<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
My opinion is that the way BD handles localization already is the right
way to go for general release. I like to be able to switch languages on
occasion for my own idiosyncratic reasons. Thinking about Vietnamese
users, though, it would be nice to have an option during installation
to choose which language is set up initially but still have the ability
to change it later. I was not aware of the locale detection feature,
which sounds pretty cool. But like Peter said, the locale needs to be
configured for that to be effective.<br>
<br>
Daniel<br>
<br>
Keith Watson wrote:
<blockquote cite="mid:000d01c8a999$dcce09c0$0201a8c0@keith" type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">In the meantime, DM, could we create a build at next release time
which automagically starts up in Farsi as the default? Irrespective of
the tricky questions I raised above? This would be wonderful.
</pre>
</blockquote>
<pre wrap="">Yes!
</pre>
</blockquote>
<pre wrap=""><!---->
Having this setup up during install is a great idea.
Keith Watson
_______________________________________________
jsword-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
PMBX license 1502
</pre>
</body>
</html>