Thanks for your replies guys. I had managed to track down the guidelines at gnu.org but the other ones were new to me.
/Martin On Aug 15, 1:23 pm, "Dardo Sordi Bogado" <[EMAIL PROTECTED]> wrote: > > But how much real text should I put in each string? I could just as > > easily translate: > > "Your data" "was saved" or > > "Your" "data" "was" "saved" > > > Should I try to keep these strings short to avoid duplication, i.e. > > keep things DRY, or make them long to give copy writing the ability to > > use specific phrasing for specific tasks? > > Use complete readable strings, DRY don't apply in translation because > it makes things really difficult (if not impossible) for translators. > > References: > > http://www.gnu.org/software/gettext/manual/gettext.html#Preparing-Str...http://www.w3.org/International/articles/composite-messages/ > > - Dardo Sordi > > > So, what happens when you want to alter the phrasing of your default > > language? Possibly radically alter it. > > An alternative that can be preferable in some cases is to have the > > msgids actually be unique ids. > > "app_flash_data_save" or > > "upload_save_ok_flash" > > might be what is translated into > > "Your data was saved" > > > Using ids here would have some similar benefits and problems to the > > ids used in SQL databases. I said some, not all. They contain no real > > text so you can totally alter the copywriting of your application at > > any point. The down side is that you will definitely have more and > > longer string in your .po files, and more duplication of words (if > > that is even a problem). > > > I have been playing around with different approaches and can honestly > > not say I have found the one true way of organizing my strings. I > > quite like using ids since they give indicate in the translation file > > how and where the string will be used. It also helps me not think > > about an applications "tone of voice" while I am in the middle of > > coding a new feature. I can focus on that when I put on my copywriter > > hat (or preferably sit down with a real pro). > > > I also like the speed and simplicity of just enclosing normal text in > > the translation function and move on... I can worry about German > > translations when I get my first customer from Germany. My application > > will not even need a .po file untill I do my first translation. But > > being from a non-English-speaking country I usually have two languages > > even from the start unless I am lazy:) > > > Well, those are my current thought on this subject. I think it is a > > subject that we could all think about a bit more. Come to think about > > it. There will probably be thousands of insightful blog-posts about > > this if I jusr google for it :)... oh well. > > > /Martin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
