Hi Marcin,<div><br></div><div>Many thanks.</div><div><br></div><div>1. If a translation is missing it will fall back to the default text so e.g. if the version string is missing the default English text will be used so nothing will be break.</div>
<div>2. I may not always be consistent but try.</div><div>3. I think this is correct.</div><div>4. Somebody else asked this. And Bible tends to target people who are not hard core Sword users and felt that document would be a simpler and more meaningful word that module. I realise many will disagree.</div>
<div><br></div><div>The strings and arrays xml documents seem great Marcin but the properties file does not seem to be a translation of the one I sent although it does seem to be a valid translation of another document so I am not sure what happened. It should have Bible section names for translation in it e.g. Gospels, History, Letters, etc.</div>
<div><br></div><div>Best wishes</div><div>Martin<br><br><div class="gmail_quote">On 27 December 2010 22:37, Marcin Sanecki <span dir="ltr"><<a href="mailto:marcin.sanecki@gmail.com">marcin.sanecki@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi Martin,<br>
<br>
I have attached translated files (UTF-8 encoded).<br>
I have tested it on my eclipse with android emulator - looks good.<br>
<br>
Here are my questions:<br>
<br>
1. I notice that e.g. in German translation there is no string for<br>
version_text. What in such case? Is the default (english) localization<br>
used for it ?<br>
2. Sometime there is dot at the and of a sentence (indexing_wait_msg)<br>
sometimes not (index_not_available_for_download). Should it gets<br>
improved?<br>
3. For key "search_all_bible" there is a translation: "Whole bible"<br>
- shouldn't be "whole Bible" ?<br>
4. <string name="download">Download Documents</string> - why<br>
Document, why not module ?<br>
<br>
Take care,<br>
Marcin<br>
<br>
2010/12/27 Martin Denham <<a href="mailto:mjdenham@gmail.com">mjdenham@gmail.com</a>>:<br>
<div><div></div><div class="h5">> Hi Marcin,<br>
> Thanks for offering to do a Polish translation of the user interface. You<br>
> can see the current translations under this folder in the dirs named<br>
> values-?? and there is currently no Polish translation of And Bible ui but<br>
> the Polish users would appreciate a localised ui. To create a Polish<br>
> translation you can download strings.xml and translate the text inside the<br>
> xml tags and e-mail the resulting file to this mailing list or direct to me.<br>
> If you wish to there are also a couple of other files which could also<br>
> usefully be translated the contents of which often appear in the ui<br>
> i) arrays.xml contains the 3 currently supported module types and ii) the<br>
> section names are in UserMsg.properties which are from JSword. You will<br>
> notice that UserMsg.properties is a properties file and the others are xml<br>
> files. The portion of UserMsg.properties to the left of ' = ' should not be<br>
> translated.<br>
> I have attached current versions of the 3 files for your convenience.<br>
> This is well timed as I am planning to do a build of And Bible soon for<br>
> checking and then a further build a few days later with some minor changes<br>
> and fixes for release on wider channels. It would be great to include a<br>
> Polish localisation.<br>
> Best regards<br>
> Martin<br>
><br>
> On 26 December 2010 22:07, Marcin Sanecki <<a href="mailto:marcin.sanecki@gmail.com">marcin.sanecki@gmail.com</a>> wrote:<br>
>><br>
>> Hi all,<br>
>> what about Polish translation ? If there is not there I'd like to do the<br>
>> job.<br>
>> Could any of you explain me how to integrate it and who can commit it ?<br>
>><br>
>> Regards<br>
>> Marcin<br>
>><br>
>> 2010/12/26 Dominique Corbex <<a href="mailto:domcox@users.sourceforge.net">domcox@users.sourceforge.net</a>>:<br>
>> > Hi all,<br>
>> ><br>
>> > Please find an updated French translation for and-bible.<br>
>> ><br>
>> > domcox<br>
>> ><br>
>> > _______________________________________________<br>
>> > mobile-devel mailing list<br>
>> > <a href="mailto:mobile-devel@crosswire.org">mobile-devel@crosswire.org</a><br>
>> > <a href="http://www.crosswire.org/mailman/listinfo/mobile-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/mobile-devel</a><br>
>> ><br>
>> ><br>
>><br>
>> _______________________________________________<br>
>> mobile-devel mailing list<br>
>> <a href="mailto:mobile-devel@crosswire.org">mobile-devel@crosswire.org</a><br>
>> <a href="http://www.crosswire.org/mailman/listinfo/mobile-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/mobile-devel</a><br>
><br>
><br>
> _______________________________________________<br>
> mobile-devel mailing list<br>
> <a href="mailto:mobile-devel@crosswire.org">mobile-devel@crosswire.org</a><br>
> <a href="http://www.crosswire.org/mailman/listinfo/mobile-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/mobile-devel</a><br>
><br>
><br>
</div></div><br>_______________________________________________<br>
mobile-devel mailing list<br>
<a href="mailto:mobile-devel@crosswire.org">mobile-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/mobile-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/mobile-devel</a><br>
<br></blockquote></div><br></div>