Localization in tx_news extension TYPO3 6 - localization

I'm using News System Extension 2.1 for my website. My TYPO3 version is 6.1.
The language key taken by tx_news is default, I would like to change the key to dk or nl or something. I changed the local language of TYPO3 using this:
config.locale_all = nl_NL
This solves the problem while displaying List of news, but when I try to display a Date Menu, it takes the default to English.
Maybe because the ViewHelpers I used for displaying List is default FLUID and the ViewHelpers used for displaying Date Menu are something else(They use translate key. Default View which comes with tx_news)
How do I change the language of tx_news to the language I desired to?

config.locale_all is basically used to change format of dates (more info on http://docs.typo3.org/typo3cms/TyposcriptReference/Setup/Config/Index.html)
In order to get localized labels, you need:
To download localization packages in Backend using the Language module
To set up your website with the language you want, using config.language (and possibly config.sys_language_uid if your website is going to be multilingual, then you would have to create sys_language records at root as well)
Please have a look at the frontend localization guide:
http://docs.typo3.org/typo3cms/FrontendLocalizationGuide/

Related

Ektron 9 - Changing default site language

Ektron 9 SP2 - 9.0.0.249
We are trying to change the default language to en-GB site-wide. This is what we tried:
Set English (UK) en-GB as enabled language in Settings-L10n-Lanugages and Regions
Set en-GB as default language in Settings-Setup-Default Application Language
Edited web.config <add key="ek_DefaultContentLanguage" value="1033" /> to 2057
We did this and it did not work, so rolled the changes back to find that all items allocated to taxonomies has disappeared. Luckily we had a database backup that we deployed.
Has anyone else tried this? What is the correct way?
Cheers
The default language is set using the key in the web.config file as you say. This only changes what the default is, i.e. the language you get without explicitly selecting one. Any existing content you have is not automatically translated.
The process should be this:
1) Enable English UK in Settings > Localization > Languages and Regions. Important to leave English US enabled for now.
2) Create English UK versions of your content. You can do this either by using the XLIFF feature or by doing it one content item at a time (go to the content item in the workarea, select the target language in the Add drop down list.
3) You will also need to ensure you have English UK versions of Taxonomies, Metadata, Menus, etc.
4) Change the default language value to "2057" in web.config using the ek_DefaultContentLanguage key.
5) Check your content appears.
6) Disable English US (if necessary).
Regarding the items that disappeared, I wonder if you had disabled English US when you enabled English UK? That might have caused this to happen.

TYPO3 alternative page language configuration

I'm trying to join a bunch of pages that are in different languages to a single page whith multiple alternative page languages.
This way, instead of having 3 Home pages, each one with its own language, I have 1 with several alternative page languages. So I'll have one page but the content is in different languages, depending on the language record it uses.
The issue is that TYPO3 extensions should behave differently depending on the language, i.e: form fields should be translated.
For that I was thinking on having a local storage folder for each page language record in order to hold the extension configurations. Chinese language would have a separated storage folder from the english version and the extension running for the chinese version would use the correct storage folder.
But how can I specify which storage folder the extension in the chinese language record should use if I don't use a new page?
Because if I use a language record to differentiate chinese from english I can't have different typoscript configurations. The language record properties page doesn't have a ts config field and as such I can't tell that the extension should use a different storage folder (different pid) for this language.
For each language you can add a cObj plugin and thus edit the plugin configuration. You can also use a condition and getText to assign a new pid to the plugin. For example plugin.test_pi1.sysfolder < 666.
The first option is when you look in the mysql table language overlay you have a separate record ctype plugin of your plugin and thus you can edit the plugin configuration.

How to translate Virtue Mart 2.0 (Joomla e-comerce plugin)?

I'm using Virtue Mart on joomla for catalogue features.And as I'm using joomla 1.7, I'm forced to use VirtueMart 2.0 that's still in RC state. I need to translate it to Ukrainian language because it's so new, that nobody have done it already.
Does anybody know where I should start? Because I've spent a lot of time looking for something like: "VirtueMart 2.0 translation guide" but I had no luck.
Uh… I've figured it out already. Her's what you should do:
Get the english files called en-GB.com_virtuemart.ini from /language/en-GB and /administrator/language/en-GB. First is for front-end "what the visitors see" and the second is for the back-end "admin panel".
Edit the file in any text editor. Just replace the words in quotes with what you need.
Change the beginning of the file to your language key and put it in the corresponding language directory in /language and /administrator/language. As for Ukrainian, the files will be renamed to uk-UA.com_virtuemart.ini and put in /language/uk-UA and /administrator/language/uk-UA.
I can also suggest using some version control to support translation, so you will see, what have you replaced with what.
If you want to make a package that could be installed with extension manager, you should read Creating language packs for extensions in Joomla_1.6

Dynamic localization files blackberry

Here's the scenario I have. I'm working on a multi-lang application but the available languages are dynamic and returned by an API from the server. After selecting a language I should download the localization file that contains the key/value pairs to use it in my application.
My question is, does the BlackBerry localization system allow such behavior? I mean can the key/value localization files be added to the application dynamically or they have to be bundled in my COD?
If that scenario doesn't work, I would appreciate suggestions on how to do this.
The default resource files used to localize an application must be bundled with the application.
Instead you could use Locale.getDefaultForSystem() to return the current locale in use and based on that load the correct language from your remote source.

Does someone has the cxLocalizer values for French and Spanish?

Dev.Express has changed quit some units in its last update (DevExpressVCLProducts-11.1.3).
So I decided to stop using my own translation components for on the fly translation of resource strings in the dev.express components (based on the Free DevExpress Addons code and translations).
In stead I now will use there cxLocalizer component.
So at the moment I am looking for ini-files with their resource texts translated into Frech, Spanish and German.
I already found the Dutch and German translations in the answer to one of their knowledge base articles.
Can anyone help ? Maybe we can compile a list to translations in this question.

Resources