<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">Il 28/05/2019 15:43, David Haslam ha
scritto:<br>
</div>
<blockquote type="cite"
cite="mid:-ud9s_kTJnypOHw_0BuP-qvXV3kv_g7RHCkdkSmCcmyzDElBxgKeIAwXjXOMI2CbBFRc2VjmueyOkc1XOujpmxBMOoYMhp6OFZ6RIB78-ms=@protonmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div>Further along this thread the thorny issue of localised
punctuation arose. </div>
<div><br>
</div>
<div>This prompts a further question about localising
front-end apps. </div>
<div><br>
</div>
<div>To what extent (if ever) do we envisage providing support for
non-Western digits in references and in how the chapter
numbers and verse tags are displayed in each front-end?</div>
<div><br>
</div>
</blockquote>
<span class="tlid-translation translation" lang="en"><span title="">David,
you're getting ahead of me... I left this question on stand-by
but it was coming after our work on the bible in Burmese.</span>
<span title="">I think it would be perfectly legitimate to do
this.</span> <span title="" class="">Or in the case of the
digits would it be possible to simply translate them, it seems
less difficult if it is a language file that is read no?</span></span>
<blockquote type="cite"
cite="mid:-ud9s_kTJnypOHw_0BuP-qvXV3kv_g7RHCkdkSmCcmyzDElBxgKeIAwXjXOMI2CbBFRc2VjmueyOkc1XOujpmxBMOoYMhp6OFZ6RIB78-ms=@protonmail.com">
<div>For example, would we ever contemplate supporting Thai
digits?</div>
<div><br>
</div>
<div>Or is our systemic bias toward Western digits too far gone?</div>
<div><br>
</div>
<div>Best regards,</div>
<div><br>
</div>
<div>David</div>
<div><br>
</div>
<div id="protonmail_mobile_signature_block">
<div>Sent from ProtonMail Mobile</div>
</div>
<div><br>
</div>
<div><br>
</div>
On Sun, May 26, 2019 at 20:46, Troy A. Griffitts <<a
href="mailto:scribe@crosswire.org" class=""
moz-do-not-send="true">scribe@crosswire.org</a>> wrote:
<blockquote class="protonmail_quote" type="cite"> As I mentioned
in my previous email. This past weekend I have spent<br>
some time internationalizing one of our Android and iOS apps:<br>
<br>
<a class="moz-txt-link-freetext" href="https://play.google.com/store/apps/details?id=org.crosswire.bishop">https://play.google.com/store/apps/details?id=org.crosswire.bishop</a><br>
<br>
I have created a "gibberish" translation file for testing, but
now am to<br>
the point that I believe it is mostly complete. If you might be
willing<br>
to translate this gibberish file into a language with which you
are<br>
natively familiar, I am sure that people group would be very
grateful<br>
for your work, and so would I. Here is the file for
translation.<br>
<br>
<a class="moz-txt-link-freetext" href="https://git.crosswire.org/main/bishop/blob/master/www/bundledResources/uilocales.d/de-utf8.conf">https://git.crosswire.org/main/bishop/blob/master/www/bundledResources/uilocales.d/de-utf8.conf</a><br>
<br>
The format should be straighforward to understand. Generally it
is:<br>
<br>
English Text=Translated Text<br>
<br>
There are a few occasions where buttons are split into 2 lines,
e.g.,<br>
<br>
Variant Study L1=Variant<br>
<br>
Variant Study L2=Study<br>
<br>
This should be generally intuitive to figure out while
translating.<br>
<br>
Finally, there are some very long strings in the "About" screen
and<br>
Install Manager Warning screens which can be seen as the last 10
lines<br>
or so in the file. I decided to use shorter keys than the
entire<br>
English text so these have keys like:<br>
<br>
App About Header=<br>
<br>
App About L1=<br>
<br>
App About L2=<br>
<br>
I hope you can figure out from my gibberish here what the
original<br>
english actually is. My giggerish dialect is generally a
conversion of<br>
non-initial vowels to zero (0). You may need to find these long
strings<br>
in the app if you can't figure out my gibberish.<br>
<br>
I will post development bundles with translations included as
they come<br>
in, so you can see how your work looks in the app before we
publish the<br>
next version. If you'd like to try your work out as you
translate, on<br>
Android, the app will look on your SD card for locales at:<br>
/sword/uilocales.d/, so if you place your locale file there, it
should<br>
be recognized and available to choose under settings.<br>
<br>
A developer preview of 1.2.0 which includes locale support is
available<br>
at: <a class="moz-txt-link-freetext" href="http://crosswire.org/~scribe/bishop.apk">http://crosswire.org/~scribe/bishop.apk</a><br>
<br>
Thank you for any help. Blessings,<br>
<br>
Troy<br>
<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page</blockquote>
<div><br>
</div>
<div><br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page</pre>
</blockquote>
<br>
</body>
</html>