[TYPO3-english] Translation use case
Vahan Amirbekyan
vamirbekyan at dgfoundation.org
Sun Oct 12 18:54:49 CEST 2008
Xavier,
thank you for your reply.
Your solution is very close to a simple hardcoding of strings into project
specific code which take away all typo3 localization solution features.
I would not like to end up using this solution frenkly.
I am though very optimistic since I beleive that when Global extensions
solution was proposed typo3 folks could not miss the localization aspect of
it for default language.
"Xavier Perseguers" <typo3 at perseguers.ch> wrote in message
news:mailman.1.1223721074.22187.typo3-english at lists.netfielders.de...
> Hi Vahan,
>
>> I have many projects that use the well known sr_feusers_register ext.
>> English the the defualt language for all projects.
>> Registration confirmation email sent by the ext has name of the project
>> in it.
>> As you all know the email text is in locallang.xml
>> It makes sense to move the ext to Global location to let all projects to
>> share its funcitnality.
>> How to hangle the locallang.xml is the question.
>> l10n location does not help with default language to my understanding and
>> to my best knowledge based on my quick experiments.
>> So, how I have a global ext and have local locallangs?
>
> Install it globally if you wish and then change the locallang locally with
> TypoScript (I made a quick search on Google and first hit was in German
> but TypoScript itself is understandable):
>
> plugin.tx_EXTENSIONKEY_pi1 {
> _LOCAL_LANG {
> de {
> labelname_ein = Das ist mein neues Label eins
> labelname_zwei = Das ist mein neues Label zwei
> }
> }
> }
>
> --
> Xavier Perseguers
> http://xavier.perseguers.ch/en
More information about the TYPO3-english
mailing list