Hi Kristof,<br><br>This issues has been brought up earlier as well. To make the translation clean up all-over the product it could<br>take more effort both in terms of development and validation. Currently we are focusing on getting in new features<br>
as we go along we can better plan for language cleanup's as well. This give us more focused work items.<br><br>We would appreciate community help in identifying such language or translation issues.<br><br>Regards,<br>
Prasad<br><br><div><span class="gmail_quote">On 11/24/08, <b class="gmail_sendername">Kristóf KOVÁCS</b> <<a href="mailto:kristof.kovacs@onlineprojects.hu">kristof.kovacs@onlineprojects.hu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello Tigers,<div><br></div><div>I was talking with Dávid of CafeOpen about vTiger translations, and there is one issue which my team often faces with, and this is word order. Let me illustrate it with an example (using German instead of Hungarian to make it more clear, but the concept is the same).</div>
<div><br></div><div>For example, in ActivityEditView.tpl there is the following code:</div><div><br></div><div><div><input title="{$APP.LBL_ADD_NEW} {$APP.Contact}" .....</div><div><br></div><div>And this shows a button called "Add Contact". It seems all well since "$APP.LBL_ADD_NEW" is "Add" and "$APP.Contact" is "Contact". </div>
<div><br></div><div>But "Add Contact" in German is "Kontakt hinzufügen" (notice that the words are in a different order). Now we have a problem since "{$APP.LBL_ADD_NEW} {$APP.Contact}" can not be forced to display this, and saying "hinzufügen Kontakt" does not sound quite right (it sounds very bad indeed).</div>
<div><br></div><div>Translation quirks can circumvent some of such problems (one could write "Neue Contact"), but often these strings are reused at other parts of the code, and fixing it in one place often destroys grammar at other places.</div>
<div><br></div><div>One idea would be to use printf()-like format strings to correct such issues, even if it may require an introduction of a now Smarty function. I'm thinking along the lines of something like this:</div>
<div><br></div><div><div>{a_smarty_printf_function $APP.ADD_NEW_SOMETHING_FORMATSTRING, $APP.LBL_ADD_NEW, $APP.Contact}</div><div><br></div><div>Then, in english, the .lang file would read:</div><div>[...]</div><div>'LBL_ADD_NEW' = 'Add',</div>
<div>'Contact' => 'Contact',</div><div>'ADD_NEW_SOMETHING_FORMATSTRING' => "'%s %s", // Very simple format string, no surprise here</div><div>[...]</div><div><br></div><div>And in german, it would be:</div>
<div><div>[...]</div>
<div>'LBL_ADD_NEW' = 'Hinzufügen',</div><div>'Contact' => 'Kontakt',</div><div>'ADD_NEW_SOMETHING_FORMATSTRING' => "'%2$s %1$s", // Notice how I used "1$" and "2$" to access arguments in different order</div>
<div>[...]</div><div><br></div><div>I don't feel it elegant enough (but more elegant than the original), so comments, suggestions, ideas, better solutions are very much welcome. Please all brainstorm this ever the next coffee. :o) </div>
<div><br></div><span class="sg"><div>Kristóf</div>
</span></div></div></div>
<br>_______________________________________________<br>
Reach hundreds of potential candidates - <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://jobs.vtiger.com" target="_blank">http://jobs.vtiger.com</a> <br></blockquote></div><br>