I prefer to use English everywhere (OS, telephone etc). I18N is fine for end-user interfaces but I consider the AS an "expert tool" so in 95% of cases, people who don't understand English probably aren't qualified to fiddle around with it ;-) Most languages have sucky translations for technical terms (and only people from the National Language Institute or whoever invented them use them)<br>
<br><div class="gmail_quote">On Tue, Jan 10, 2012 at 11:34 AM, Heiko Braun <span dir="ltr"><<a href="mailto:hbraun@redhat.com">hbraun@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><br></div><div><br></div><div>I am currently going through the console, preparing it for i18n.</div><div>Basically making sure everything is properly placed into bundles that can be translated.</div>
<div><br></div><div>There is one thing I need your feedback on: </div><div>How are we going to treat strings that reflect technical terms? </div><div><br></div><div>I.e. a log handler has an editable field name (speaking of the UI here) called "Auto Flush".</div>
<div>To me this represent a technical term that corresponds with other places like the XML schema, the CLI and the actual XML configuration files. As such, I objecting to translate those. "Log Level" is another good example. </div>
<div><br></div><div>Now, to many native english speaking people, this might not be obvious, but once you start translating those things get pretty awkward. IMO technical terms should stay untouched and I expect people to incorporate those easily into their own language. As a result the web management interface would keep english terms for elements that derive from the XML schema or other API and provide localized description and help texts for anything else.</div>
<div><br></div><div><br></div><div>What are you thoughts on this?</div><span class="HOEnZb"><font color="#888888"><div><br></div><br><div>
<span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><div style="word-wrap:break-word">
<span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><div style="word-wrap:break-word">
<div>--</div><div><br></div><div>Heiko Braun</div><div>Senior Software Engineer</div><div>JBoss by Red Hat</div><div><a href="http://about.me/hbraun" target="_blank">http://about.me/hbraun</a></div><div><br></div></div></span><br>
</div></span><br></span><br>
</div>
<br></font></span></div><br>_______________________________________________<br>
jboss-as7-dev mailing list<br>
<a href="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>---<br>Nik<br>