Mario has translated BibleNames_fr.properties, JSMsg_fr.properties, and JSOtherMsg_fr.properties using Amanuens. Because of an unexpected issue I pointed Amanuens to a dummy location for this first language and manually copied the files over, but now Amanuens is pointing directly at the JSword repo.<br>
<br>Could somebody clarify the difference between the contents of JSMsg.properties and JSOtherMsg.properties? Are they both equally important?<br><br>Kind regards<br>Martin<br><br><div class="gmail_quote">On 23 April 2011 20:46, Martin Denham <span dir="ltr"><<a href="mailto:mjdenham@gmail.com">mjdenham@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Would you be happy to do a trial translation of BibleNames.properties into 1 or 2 languages?<br>
<br>And Bible has been translated into some new languages recently using Amanuens and the easiest way for the same translators to translate JSword files, which still require translating, would be by using the same tool. Welsh and Ukrainian translations of And Bible strings were recently completed, Malagasy and Kazakh are pending.<br>
<br>The way Mario and I have configured Amanuens<->AndBibleSvn integration was to create a dummy user account called <a href="mailto:translate.andbible@gmail.com" target="_blank">translate.andbible@gmail.com</a> which I set up as a developer in And Bible svn. Then I loaded <a href="mailto:translate.andbible@gmail.com" target="_blank">translate.andbible@gmail.com</a> svn repo access information into Amanuens, to allow Amanuens to upload translations to the And Bible svn directly. Would you be happy to do something similar for JSword on a trial basis. Using a specified dummy account has the advantage that it is easier to monitor Amanuens actions.<br>
<br>I am still not an expert in Amanuens but my current understanding (Mario may confirm) is that using Amanuens to translate files would not preclude the use of other translation tools because there appears to be 2-way synchronisation. I should add that I have not been very active in the Amanuens
integration but that Mario made the initial suggestion and has been
coordinating it.<br>
<br>Best regards<br><font color="#888888">Martin</font><div><div></div><div class="h5"><br><br><br><div class="gmail_quote">On 7 April 2011 19:02, Martin Denham <span dir="ltr"><<a href="mailto:mjdenham@gmail.com" target="_blank">mjdenham@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi,<br><br>And Bible has started using <a href="http://amanuens.com/" target="_blank">Amanuens </a>to simplify the translation of its text strings and I wondered if there would be any interest in using Amanuens to manage the translation of JSword resource files.<br>
<br>Mario (copied) has been driving this forward for And Bible. We have been trialling it for a few weeks and it does seem to work pretty well although we had a few hiccups. <br><br>Best regards<br><font color="#888888">Martin<br>
</font></blockquote></div><br>
</div></div></blockquote></div><br>