Die TYPO3 Mailingliste - nicht fragen: lesen!
This is a discussion on [TYPO3] Special localization need within the typo3-english@lists.netfielders.de forums, part of the TYPO3-Mailinglists: ENGLISH category; Hello, Question as summary ------------------- How can I change the master language for part of my website? Full description of the ...
|
|||||||
| Registrieren | Hilfe | Benutzerliste | Kalender | Suchen | Heutige Beiträge | Alle Foren als gelesen markieren |
|
#1
|
|||
|
|||
|
Hello,
Question as summary ------------------- How can I change the master language for part of my website? Full description of the problem ------------------------------- The website I design is kind of a multi-domain site where multiple editors will edit page only for their "domain" (editor A will edit http://domain.tld/domainA pages, editor B will edit http://domain.tld/domainB pages, and so on). The problem I'm facing is that I need to have the whole website with all these "domains" multilingual as generic content will have their labels translated automatically. For instance a plugin for events will have "date, time, subject, ..." labels translated. The content itself will not be translated in all cases. I would bet that actually it won't often be translated. This is the reason why I'll implement the fallback mode of localization with TYPO3. The problem I'm facing is to know whether it is possible to setup a "default" or master language that is domain-dependant. For instance domain A might be "French-based" while domain-B is "German-based". With TYPO3 and its localization mechanism, AFAIK, you need to first type text in the master language before being able to translate it. That is, if I understand well and I'll have this scenario (I assume master language is English ![]() - Editor A types French content into master language. No problem, this is the only available localized content and browsing the website in English, French or German always shows French content with localized labels as explained above - After a few months, he decides to translate content into English. He cannot create an English translation. He has to: - create a French translation - copy the content from the master language (actually it's copied automatically), remove "Copy from" prefix (I know I could deactivate this feature with TS) - modify "master" text with the English translation - go back to French content and save content again to remove the fact that the master content changed and that the translation might need to be adapt to reflect change This was a "simple" case but if he first chooses to translate content in German and later translate it the the master language, then this will be a bit trickier. -- Xavier Perseguers http://xavier.perseguers.ch/en _______________________________________________ TYPO3-english mailing list TYPO3-english (AT) lists (DOT) netfielders.de http://lists.netfielders.de/cgi-bin/.../typo3-english |
|
#2
|
|||
|
|||
|
on Mon, 23 Jun 2008 22:47:32 +0200, Xavier Perseguers wrote:
> Hello, > > Question as summary > ------------------- > > How can I change the master language for part of my website? > > > > Full description of the problem > ------------------------------- > > The website I design is kind of a multi-domain site where multiple > editors will edit page only for their "domain" (editor A will edit > http://domain.tld/domainA pages, editor B will edit > http://domain.tld/domainB pages, and so on). > > The problem I'm facing is that I need to have the whole website with all > these "domains" multilingual as generic content will have their labels > translated automatically. For instance a plugin for events will have > "date, time, subject, ..." labels translated. The content itself will > not be translated in all cases. I would bet that actually it won't often > be translated. This is the reason why I'll implement the fallback mode > of localization with TYPO3. > > The problem I'm facing is to know whether it is possible to setup a > "default" or master language that is domain-dependant. For instance > domain A might be "French-based" while domain-B is "German-based". With > TYPO3 and its localization mechanism, AFAIK, you need to first type text > in the master language before being able to translate it. > > That is, if I understand well and I'll have this scenario (I assume > master language is English ![]() > > - Editor A types French content into master language. No problem, this > is the only available localized content and browsing the website in > English, French or German always shows French content with localized > labels as explained above > > - After a few months, he decides to translate content into English. He > cannot create an English translation. He has to: > > - create a French translation > - copy the content from the master language (actually it's copied > automatically), remove "Copy from" prefix (I know I could deactivate > this feature with TS) > - modify "master" text with the English translation - go back to > French content and save content again to remove the fact > that the master content changed and that the translation might need to > be adapt to reflect change > > This was a "simple" case but if he first chooses to translate content in > German and later translate it the the master language, then this will be > a bit trickier. you may use the content in 'default'-language in any language you want. important is the definition of default-language in your typoscript- template. This may vary from domain/ tree to domain/ tree if you want to translate, you have to insert those languages in the root- page. if you want to use these languages you also have to insert them in your typoscript-templates. example: #default-Konfiguration config.sys_language_uid = 0 config.language = en config.locale_all = en_EN config.htmlTag_langKey = en [globalVar = GP:L = 0] # Configuration if &L=0 config.sys_language_uid = 0 config.language = en config.locale_all = en_EN config.htmlTag_langKey = en [global] [globalVar = GP:L = 1] # Configuration if &L=1 config.sys_language_uid = 1 config.language = de config.locale_all = de_DE config.htmlTag_langKey = de [global] bernd -- http://www.pi-phi.de/t3v4/cheatsheet.html _______________________________________________ TYPO3-english mailing list TYPO3-english (AT) lists (DOT) netfielders.de http://lists.netfielders.de/cgi-bin/.../typo3-english |
|
#3
|
|||
|
|||
|
Hello,
>> Question as summary >> ------------------- >> >> How can I change the master language for part of my website? >> >> >> >> Full description of the problem >> ------------------------------- >> >> The website I design is kind of a multi-domain site where multiple >> editors will edit page only for their "domain" (editor A will edit >> http://domain.tld/domainA pages, editor B will edit >> http://domain.tld/domainB pages, and so on). >> >> [snip] >> >> The problem I'm facing is to know whether it is possible to setup a >> "default" or master language that is domain-dependant. For instance >> domain A might be "French-based" while domain-B is "German-based". With >> TYPO3 and its localization mechanism, AFAIK, you need to first type text >> in the master language before being able to translate it. >> >> [snip] > > you may use the content in 'default'-language in any language you want. > important is the definition of default-language in your typoscript- > template. This may vary from domain/ tree to domain/ tree > > if you want to translate, you have to insert those languages in the root- > page. if you want to use these languages you also have to insert them in > your typoscript-templates. > > example: > > #default-Konfiguration > config.sys_language_uid = 0 > config.language = en > config.locale_all = en_EN > config.htmlTag_langKey = en > > [globalVar = GP:L = 0] > # Configuration if &L=0 > config.sys_language_uid = 0 > config.language = en > config.locale_all = en_EN > config.htmlTag_langKey = en > [global] > > [globalVar = GP:L = 1] > # Configuration if &L=1 > config.sys_language_uid = 1 > config.language = de > config.locale_all = de_DE > config.htmlTag_langKey = de > [global] Thanks bernd. An extract from my realurl_conf.php file looks like this: 'preVars' => array( , array( 'GETvar' => 'L', 'valueMap' => array( 'de' => '1', 'fr' => '2', 'it' => '3', ), 'noMatch' => 'bypass', ), ), This means that I should in fact define English as L=0 and this will lead to having url of the form http://mydomain.tld/some/page in default language whatever it is http://mydomain.tld/en/some/page in English http://mydomain.tld/fr/some/page in French .... and pages will be indexed twice, once for the "default" language and one when it is well defined. This is OK but I think I would prefer telling RealURL to always redirect to the default language and get the default language prepended to the URL whenever I access my website without a language parameter. I do not know whether it is possible? -- Xavier Perseguers http://xavier.perseguers.ch/en _______________________________________________ TYPO3-english mailing list TYPO3-english (AT) lists (DOT) netfielders.de http://lists.netfielders.de/cgi-bin/.../typo3-english |
|
#4
|
|||
|
|||
|
Hello again,
I was a bit still asleep and missed an important point... ![]() The solution you give is OK to change the default language in a frontend view. But the problem remains for backend editing/localizing. I defined default language as English, that is I needed to add language records to my root, namely French, German and Italian with sys_language_uid 1, 2 and 3, 0 being English. When I create a content element it is defined as "default language" which I remain with a pageTS to read "English" and get the Britain flag also. Thus playing with config.language and so on I may choose another default language for the frontend and with realurl, if I define a preVar for English (=0), I get my website in the default language without prefix or in one of the 4 languages with prefix. OK. But the user still has to first create content in English to be able to translate it later. I think, in order to go to the end with this problem, I should create a fourth language record in my root for English, user would then have this when he chooses to translate his page: (default) French German Italian English That is, he may type his master content in whatever language he likes and then translate it to one of this other language. Depending on the default language, I could then say that the English version for instance is either the sys_language_uid = 0 or the sys_language_uid = 4. I think it will work. But what would be really great would be to hide the language record which is already "present" as default language. Thus hiding the sys_language_uid = 4 when default language is English and hiding sys_language_uid = 1 when default language is French. Is this possible? I would then have all cards in hand to achieve my goal! -- Xavier _______________________________________________ TYPO3-english mailing list TYPO3-english (AT) lists (DOT) netfielders.de http://lists.netfielders.de/cgi-bin/.../typo3-english |
|
#5
|
|||
|
|||
|
Hi,
> But what would be really great would be to hide the language record > which is already "present" as default language. Thus hiding the > sys_language_uid = 4 when default language is English and hiding > sys_language_uid = 1 when default language is French. The languages available in a given page for translating records depend on the languages in which the page was translated. So if a page is not translated to English (4), this language will not be available for content elements, news or whatever. Of course, there remains the problem of English (4) being available for translation of the page. If you have different users across your different domains, you could use the BE users or BE groups to restrict access to languages, this hiding English (4). HTH -- Francois Suter Cobweb Development Sarl - http://www.cobweb.ch _______________________________________________ TYPO3-english mailing list TYPO3-english (AT) lists (DOT) netfielders.de http://lists.netfielders.de/cgi-bin/.../typo3-english |
|
#6
|
|||
|
|||
|
Hi Francois,
>> But what would be really great would be to hide the language record >> which is already "present" as default language. Thus hiding the >> sys_language_uid = 4 when default language is English and hiding >> sys_language_uid = 1 when default language is French. > > The languages available in a given page for translating records depend > on the languages in which the page was translated. So if a page is not > translated to English (4), this language will not be available for > content elements, news or whatever. > > Of course, there remains the problem of English (4) being available for > translation of the page. If you have different users across your > different domains, you could use the BE users or BE groups to restrict > access to languages, this hiding English (4). Yes, this is another option. Thanks -- Xavier Perseguers http://xavier.perseguers.ch/en/tutorials/typo3.html _______________________________________________ TYPO3-english mailing list TYPO3-english (AT) lists (DOT) netfielders.de http://lists.netfielders.de/cgi-bin/.../typo3-english |
|
#7
|
|||
|
|||
|
Xavier Perseguers wrote:
> Hi Francois, > >>> But what would be really great would be to hide the language record >>> which is already "present" as default language. Thus hiding the >>> sys_language_uid = 4 when default language is English and hiding >>> sys_language_uid = 1 when default language is French. >> >> The languages available in a given page for translating records depend >> on the languages in which the page was translated. So if a page is not >> translated to English (4), this language will not be available for >> content elements, news or whatever. >> >> Of course, there remains the problem of English (4) being available >> for translation of the page. If you have different users across your >> different domains, you could use the BE users or BE groups to restrict >> access to languages, this hiding English (4). > > Yes, this is another option. Thanks I'll still try to remove it using pageTS instead as I already know there will be users that will be able to edit content in multiple sections (in a few months). -- Xavier Perseguers http://xavier.perseguers.ch/en/tutorials/typo3.html _______________________________________________ TYPO3-english mailing list TYPO3-english (AT) lists (DOT) netfielders.de http://lists.netfielders.de/cgi-bin/.../typo3-english |
|
#8
|
|||
|
|||
|
Hello,
I come back to this question and now I have my answer, I definitively need to create a fourth language, "Special English" that will be used whenever default language (master language) is not English but something else. Now the blocking point is to know what should I do to remove a language from the list of available languages when localizing a page *based on a page subtree*, not on user groups. The question was already asked a year ago I think (I found something with Google) but seems to have been left somehow floating. It seems there is no pageTS available for this, so is there a way with an extension? -- Xavier Perseguers http://xavier.perseguers.ch/en _______________________________________________ TYPO3-english mailing list TYPO3-english (AT) lists (DOT) netfielders.de http://lists.netfielders.de/cgi-bin/.../typo3-english |
|
#9
|
|||
|
|||
|
Hi,
> Now the blocking point is to know what should I do to remove a language > from the list of available languages when localizing a page *based on a > page subtree*, not on user groups. > > The question was already asked a year ago I think (I found something > with Google) but seems to have been left somehow floating. It seems > there is no pageTS available for this, so is there a way with an extension? Well, it is possible to disable items from a select-type field using PageTS. The question is whether it will apply in this case, since this drop-down doesn't have a fixed list of values, but relies on querying the sys_language table. It may still be worth a try... Cheers -- Francois Suter Cobweb Development Sarl - http://www.cobweb.ch _______________________________________________ TYPO3-english mailing list TYPO3-english (AT) lists (DOT) netfielders.de http://lists.netfielders.de/cgi-bin/.../typo3-english |
| Themen-Optionen | Thema durchsuchen |
| Ansicht | Thema bewerten |
|
|
|
||||
| Thema | Autor | Forum | Antworten | Letzter Beitrag |
| [TYPO3-templavoila] Localization of a FCE | lee perry | typo3-project-templavoila@lists.netfielders.de | 8 | 22.07.2008 09:37 |
| [TYPO3-german] css localization | Achim Gerber | typo3-german@lists.netfielders.de | 4 | 03.10.2007 16:18 |
| [TYPO3] Localization problem | Jeppe Donslund | typo3-english@lists.netfielders.de | 9 | 07.06.2007 12:04 |
| [TYPO3] EXT Localization | rocky Ou | typo3-english@lists.netfielders.de | 5 | 18.12.2006 16:11 |
| [TYPO3] Localization problem | Jigal van Hemert | typo3-english@lists.netfielders.de | 3 | 04.12.2006 08:37 |