|

»

»

vtigercrm dev lists

»

vtigercrm-developers

Whole sentences for language translation?

View: New views

8 Messages — Rating Filter: Alert me

	Whole sentences for language translation? by Paproth, Stefan :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Hi there, is it possible to use only whole sentences for language translation? Actually, some sentences are build by pieces which makes it sometimes impossible to build right sentences in other languages. We use the German language-package and have problems on some places. A good example is quick-create: {foreach item=detail from=$QCMODULE} <option value="{$detail.1}">{$APP.NEW} {$detail.0}</option> {/foreach} This generates in English: New Account New Contact New Document ... The word new is stored in "NEW" But in German the word new depends on the second word: So you write Neue Firma for new Account Neuer Kontakt for new Contact Neues Dokument for new document I think other languages might have the same problem! Best regards, Stefan _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com
	Re: Whole sentences for language translation? by Eugene Babiy :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Hi Paproth. In Russian we have the same problems. But in your situation "NEW" in Russian translates as "НОВЫЙ" and I decided to shorten it and make "Нов." but it looks ugly. Best regards, Eugene Babiy tel. +380660785088 mob. +380505804768 Skype: eugene.babiy Paproth, Stefan пишет: Hi there, is it possible to use only whole sentences for language translation? Actually, some sentences are build by pieces which makes it sometimes impossible to build right sentences in other languages. We use the German language-package and have problems on some places. A good example is quick-create: {foreach item=detail from=$QCMODULE} <option value="{$detail.1}">{$APP.NEW} {$detail.0}</option> {/foreach} This generates in English: New Account New Contact New Document ... The word new is stored in "NEW" But in German the word new depends on the second word: So you write Neue Firma for new Account Neuer Kontakt for new Contact Neues Dokument for new document I think other languages might have the same problem! Best regards, Stefan _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com `[eugene_babiy.vcf]` `begin:vcard fn:Eugene Babiy n:Babiy;Eugene org:"Gorysont";Sales adr:;;vul. Korotka, 32;Lenkivtsi;Chv;60111;Ukraine email;internet:eugene.babiy@... title:Manager tel;work:+380660785088 tel;cell:+380505804768 x-mozilla-html:TRUE version:2.1 end:vcard` _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com
	Re: Whole sentences for language translation? by carlo beschi :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Hi all, the same issue is present (and not easily fixable at current state) with italian translations. A great effort has been done IMHO in 5.1 to better internationalization and internationalization support. But with the current system (single language files for all modules + general application labels in a different file) there's not that much more that you can do than adding new labels - and taking hardcoded string out of the code . I've been playing a bit with gettext (http://www.gnu.org/software/gettext/) for localizing issue on a client's project which uses wordpress as a software basis. I find it amazing to work with .mo and .po files :-D (http://codex.wordpress.org/Translating_WordPress#gettext_files) This is a enhancement suggestion for vtiger 6.0 ... carloz Eugene Babiy ha scritto: > Hi Paproth. > > In Russian we have the same problems. But in your situation "NEW" in > Russian translates as "НОВЫЙ" and I decided to shorten it and make > "Нов." but it looks ugly. > > Best regards, Eugene Babiy > > tel. +380660785088 > mob. +380505804768 > Skype: eugene.babiy > > > > Paproth, Stefan пишет: >> Hi there, >> >> is it possible to use only whole sentences for language translation? >> Actually, some sentences are build by pieces which makes it sometimes >> impossible to build right sentences in other languages. >> >> We use the German language-package and have problems on some places. >> >> A good example is quick-create: >> >> {foreach item=detail from=$QCMODULE} >> <option >> value="{$detail.1}">{$APP.NEW} {$detail.0}</option> >> {/foreach} >> >> This generates in English: >> >> New Account >> New Contact >> New Document >> ... >> >> The word new is stored in "NEW" >> >> But in German the word new depends on the second word: >> So you write >> >> Neue Firma for new Account >> Neuer Kontakt for new Contact >> Neues Dokument for new document >> >> I think other languages might have the same problem! >> >> Best regards, >> >> Stefan >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Reach hundreds of potential candidates - http://jobs.vtiger.com > _______________________________________________ > Reach hundreds of potential candidates - http://jobs.vtiger.com _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com
	Re: Whole sentences for language translation? by David V.-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Gettext would be great. We use it in other projects for french and spanish. David V. 2009/9/21 Carlo Beschi <carloz@...> Hi all, the same issue is present (and not easily fixable at current state) with italian translations. A great effort has been done IMHO in 5.1 to better internationalization and internationalization support. But with the current system (single language files for all modules + general application labels in a different file) there's not that much more that you can do than adding new labels - and taking hardcoded string out of the code . I've been playing a bit with gettext (http://www.gnu.org/software/gettext/) for localizing issue on a client's project which uses wordpress as a software basis. I find it amazing to work with .mo and .po files :-D (http://codex.wordpress.org/Translating_WordPress#gettext_files) This is a enhancement suggestion for vtiger 6.0 ... carloz Eugene Babiy ha scritto: > Hi Paproth. > > In Russian we have the same problems. But in your situation "NEW" in > Russian translates as "НОВЫЙ" and I decided to shorten it and make > "Нов." but it looks ugly. > > Best regards, Eugene Babiy > > tel. +380660785088 > mob. +380505804768 > Skype: eugene.babiy > > > > Paproth, Stefan пишет: >> Hi there, >> >> is it possible to use only whole sentences for language translation? >> Actually, some sentences are build by pieces which makes it sometimes >> impossible to build right sentences in other languages. >> >> We use the German language-package and have problems on some places. >> >> A good example is quick-create: >> >> {foreach item=detail from=$QCMODULE} >> <option >> value="{$detail.1}">{$APP.NEW} {$detail.0}</option> >> {/foreach} >> >> This generates in English: >> >> New Account >> New Contact >> New Document >> ... >> >> The word new is stored in "NEW" >> >> But in German the word new depends on the second word: >> So you write >> >> Neue Firma for new Account >> Neuer Kontakt for new Contact >> Neues Dokument for new document >> >> I think other languages might have the same problem! >> >> Best regards, >> >> Stefan >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Reach hundreds of potential candidates - http://jobs.vtiger.com > _______________________________________________ > Reach hundreds of potential candidates - http://jobs.vtiger.com _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com
	Re: Whole sentences for language translation? by Prasad-14 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. Hi Carlo/David Can you share a small write up or example app to demonstrate the use of Gettext, I'm interested to learn and understand it. Regards, Prasad vtiger Team On 9/21/09, David V. <davidv.net@gmail.com> wrote: Gettext would be great. We use it in other projects for french and spanish. David V. 2009/9/21 Carlo Beschi <carloz@...> Hi all, the same issue is present (and not easily fixable at current state) with italian translations. A great effort has been done IMHO in 5.1 to better internationalization and internationalization support. But with the current system (single language files for all modules + general application labels in a different file) there's not that much more that you can do than adding new labels - and taking hardcoded string out of the code . I've been playing a bit with gettext (http://www.gnu.org/software/gettext/) for localizing issue on a client's project which uses wordpress as a software basis. I find it amazing to work with .mo and .po files :-D (http://codex.wordpress.org/Translating_WordPress#gettext_files) This is a enhancement suggestion for vtiger 6.0 ... carloz Eugene Babiy ha scritto: > Hi Paproth. > > In Russian we have the same problems. But in your situation "NEW" in > Russian translates as "НОВЫЙ" and I decided to shorten it and make > "Нов." but it looks ugly. > > Best regards, Eugene Babiy > > tel. +380660785088 > mob. +380505804768 > Skype: eugene.babiy > > > > Paproth, Stefan пишет: >> Hi there, >> >> is it possible to use only whole sentences for language translation? >> Actually, some sentences are build by pieces which makes it sometimes >> impossible to build right sentences in other languages. >> >> We use the German language-package and have problems on some places. >> >> A good example is quick-create: >> >> {foreach item=detail from=$QCMODULE} >> <option >> value="{$detail.1}">{$APP.NEW} {$detail.0}</option> >> {/foreach} >> >> This generates in English: >> >> New Account >> New Contact >> New Document >> ... >> >> The word new is stored in "NEW" >> >> But in German the word new depends on the second word: >> So you write >> >> Neue Firma for new Account >> Neuer Kontakt for new Contact >> Neues Dokument for new document >> >> I think other languages might have the same problem! >> >> Best regards, >> >> Stefan >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Reach hundreds of potential candidates - http://jobs.vtiger.com > _______________________________________________ > Reach hundreds of potential candidates - http://jobs.vtiger.com _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com
	Re: Whole sentences for language translation? by Finjon Kiang :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Maybe check this: http://us.php.net/manual/en/function.gettext.php One more hope. If there exists any plan for vtiger 6.0, hope it could be a rewrite base on some popular PHP frameworks, like CakePHP. ;) -- Finjon Kiang 2009/9/23 Prasad <prasad@...>: > Hi Carlo/David > > Can you share a small write up or example app to demonstrate the use of > Gettext, I'm interested to learn and understand it. > > Regards, > Prasad > vtiger Team > > On 9/21/09, David V. <davidv.net@...> wrote: >> >> Gettext would be great. >> >> We use it in other projects for french and spanish. >> >> David V. >> >> >> 2009/9/21 Carlo Beschi <carloz@...> >>> >>> Hi all, >>> >>> the same issue is present (and not easily fixable at current state) with >>> italian translations. >>> >>> A great effort has been done IMHO in 5.1 to better internationalization >>> and internationalization support. >>> >>> But with the current system (single language files for all modules + >>> general application labels in a different file) there's not that much >>> more that you can do than adding new labels - and taking hardcoded >>> string out of the code . >>> >>> >>> I've been playing a bit with gettext >>> (http://www.gnu.org/software/gettext/) for localizing issue on a >>> client's project which uses wordpress as a software basis. >>> >>> I find it amazing to work with .mo and .po files :-D >>> >>> (http://codex.wordpress.org/Translating_WordPress#gettext_files) >>> >>> This is a enhancement suggestion for vtiger 6.0 ... >>> >>> carloz >>> >>> Eugene Babiy ha scritto: >>> > Hi Paproth. >>> > >>> > In Russian we have the same problems. But in your situation "NEW" in >>> > Russian translates as "НОВЫЙ" and I decided to shorten it and make >>> > "Нов." but it looks ugly. >>> > >>> > Best regards, Eugene Babiy >>> > >>> > tel. +380660785088 >>> > mob. +380505804768 >>> > Skype: eugene.babiy >>> > >>> > >>> > >>> > Paproth, Stefan пишет: >>> >> Hi there, >>> >> >>> >> is it possible to use only whole sentences for language translation? >>> >> Actually, some sentences are build by pieces which makes it sometimes >>> >> impossible to build right sentences in other languages. >>> >> >>> >> We use the German language-package and have problems on some places. >>> >> >>> >> A good example is quick-create: >>> >> >>> >> {foreach item=detail from=$QCMODULE} >>> >> <option >>> >> value="{$detail.1}">{$APP.NEW} {$detail.0}</option> >>> >> {/foreach} >>> >> >>> >> This generates in English: >>> >> >>> >> New Account >>> >> New Contact >>> >> New Document >>> >> ... >>> >> >>> >> The word new is stored in "NEW" >>> >> >>> >> But in German the word new depends on the second word: >>> >> So you write >>> >> >>> >> Neue Firma for new Account >>> >> Neuer Kontakt for new Contact >>> >> Neues Dokument for new document >>> >> >>> >> I think other languages might have the same problem! >>> >> >>> >> Best regards, >>> >> >>> >> Stefan _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com
	Re: Whole sentences for language translation? by David V.-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Hi Prasad, I currently use gettext in php-gtk2 (desktop) applications. But since most people use it for web sites I realized it would be easier for me to point you to a nice tuto instead of writing one for you (since I don't currently use it for any web site). Here is one : http://mel.melaxis.com/devblog/2005/08/06/localizing-php-web-sites-using-gettext/ And another one : http://onlamp.com/pub/a/php/2002/06/13/php.html?page=1 If the first one the autor mention the problem of plurals we have in many languages and how to solve it "automatically" with gettext. David V. 2009/9/22 Prasad <prasad@...> Hi Carlo/David Can you share a small write up or example app to demonstrate the use of Gettext, I'm interested to learn and understand it. Regards, Prasad vtiger Team On 9/21/09, David V. <davidv.net@gmail.com> wrote: Gettext would be great. We use it in other projects for french and spanish. David V. 2009/9/21 Carlo Beschi <carloz@...> Hi all, the same issue is present (and not easily fixable at current state) with italian translations. A great effort has been done IMHO in 5.1 to better internationalization and internationalization support. But with the current system (single language files for all modules + general application labels in a different file) there's not that much more that you can do than adding new labels - and taking hardcoded string out of the code . I've been playing a bit with gettext (http://www.gnu.org/software/gettext/) for localizing issue on a client's project which uses wordpress as a software basis. I find it amazing to work with .mo and .po files :-D (http://codex.wordpress.org/Translating_WordPress#gettext_files) This is a enhancement suggestion for vtiger 6.0 ... carloz Eugene Babiy ha scritto: > Hi Paproth. > > In Russian we have the same problems. But in your situation "NEW" in > Russian translates as "НОВЫЙ" and I decided to shorten it and make > "Нов." but it looks ugly. > > Best regards, Eugene Babiy > > tel. +380660785088 > mob. +380505804768 > Skype: eugene.babiy > > > > Paproth, Stefan пишет: >> Hi there, >> >> is it possible to use only whole sentences for language translation? >> Actually, some sentences are build by pieces which makes it sometimes >> impossible to build right sentences in other languages. >> >> We use the German language-package and have problems on some places. >> >> A good example is quick-create: >> >> {foreach item=detail from=$QCMODULE} >> <option >> value="{$detail.1}">{$APP.NEW} {$detail.0}</option> >> {/foreach} >> >> This generates in English: >> >> New Account >> New Contact >> New Document >> ... >> >> The word new is stored in "NEW" >> >> But in German the word new depends on the second word: >> So you write >> >> Neue Firma for new Account >> Neuer Kontakt for new Contact >> Neues Dokument for new document >> >> I think other languages might have the same problem! >> >> Best regards, >> >> Stefan >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Reach hundreds of potential candidates - http://jobs.vtiger.com > _______________________________________________ > Reach hundreds of potential candidates - http://jobs.vtiger.com _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com
	Re: Whole sentences for language translation? by Prasad-14 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. @David, @Finjon Thanks for the references. On 9/23/09, David V. <davidv.net@gmail.com> wrote: Hi Prasad, I currently use gettext in php-gtk2 (desktop) applications. But since most people use it for web sites I realized it would be easier for me to point you to a nice tuto instead of writing one for you (since I don't currently use it for any web site). Here is one : http://mel.melaxis.com/devblog/2005/08/06/localizing-php-web-sites-using-gettext/ And another one : http://onlamp.com/pub/a/php/2002/06/13/php.html?page=1 If the first one the autor mention the problem of plurals we have in many languages and how to solve it "automatically" with gettext. David V. 2009/9/22 Prasad <prasad@...> Hi Carlo/David Can you share a small write up or example app to demonstrate the use of Gettext, I'm interested to learn and understand it. Regards, Prasad vtiger Team On 9/21/09, David V. <davidv.net@gmail.com> wrote: Gettext would be great. We use it in other projects for french and spanish. David V. 2009/9/21 Carlo Beschi <carloz@...> Hi all, the same issue is present (and not easily fixable at current state) with italian translations. A great effort has been done IMHO in 5.1 to better internationalization and internationalization support. But with the current system (single language files for all modules + general application labels in a different file) there's not that much more that you can do than adding new labels - and taking hardcoded string out of the code . I've been playing a bit with gettext (http://www.gnu.org/software/gettext/) for localizing issue on a client's project which uses wordpress as a software basis. I find it amazing to work with .mo and .po files :-D (http://codex.wordpress.org/Translating_WordPress#gettext_files) This is a enhancement suggestion for vtiger 6.0 ... carloz Eugene Babiy ha scritto: > Hi Paproth. > > In Russian we have the same problems. But in your situation "NEW" in > Russian translates as "НОВЫЙ" and I decided to shorten it and make > "Нов." but it looks ugly. > > Best regards, Eugene Babiy > > tel. +380660785088 > mob. +380505804768 > Skype: eugene.babiy > > > > Paproth, Stefan пишет: >> Hi there, >> >> is it possible to use only whole sentences for language translation? >> Actually, some sentences are build by pieces which makes it sometimes >> impossible to build right sentences in other languages. >> >> We use the German language-package and have problems on some places. >> >> A good example is quick-create: >> >> {foreach item=detail from=$QCMODULE} >> <option >> value="{$detail.1}">{$APP.NEW} {$detail.0}</option> >> {/foreach} >> >> This generates in English: >> >> New Account >> New Contact >> New Document >> ... >> >> The word new is stored in "NEW" >> >> But in German the word new depends on the second word: >> So you write >> >> Neue Firma for new Account >> Neuer Kontakt for new Contact >> Neues Dokument for new document >> >> I think other languages might have the same problem! >> >> Best regards, >> >> Stefan >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Reach hundreds of potential candidates - http://jobs.vtiger.com > _______________________________________________ > Reach hundreds of potential candidates - http://jobs.vtiger.com _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com _______________________________________________ Reach hundreds of potential candidates - http://jobs.vtiger.com