[sword-devel] Arabic Translation

[Troy A. Griffitts]

Sameh,
	Great to hear you got it working!  Yes, we need to make a note of this. 
  I believe someone else had this same problem a while back.  It turns 
out that if you hit enter at the top of your locale (have at least 1 
blank line at the top) everything will work fine.  The technical problem 
is that our SWORD config object looks for lines which start with a '[' 
to determine the start of a new section.  When the MS editors add the 
BOM character to hint that the file is Unicode UTF-8, the line no longer 
starts with a '[' and the section is skipped.  We should really change 
our config class to ignore these characters.  My apologies for not 
remembering this problem!  Again, I'm glad you got things working.  I 
expect a new BibleCS release sometime near and before Jun 15.

	Excited to have your Arabic submissions!

		-Troy.




See7a wrote:
> All,
> 
> I finally got arabic working in both locales and uilocales :) I'm
> sending this mail to let you know the solution and also because I
> think there should be some easier way to do it :)
> 
> The cause of the problems I had is the BOM hidden characters added in
> the begining of the text file when I save it as utf8 in notepad. I
> also tried another text editor with the same result. SWORD doesn't
> seem to handle these charachters correctly. I just have open the file
> in some editor that displays them and delete them manually to get it
> to work.
> 
> Now it's just a matter of writing some Arabic string. I will send
> again as soon as I have something completed.
> 
> I just wanted to know when is the next realease of SWORD for Windows
> expected? I want to try to finish this translation - or at least a big
> part of it - before the coming release so that it can be added to the
> release package.
> 
> Blessings,
> Sameh
> 
> On 5/1/05, Joachim Ansorg <junkmail at joachim.ansorgs.de> wrote:
> 
>>Hi,
>>
>>>The files provided at
>>>https://crosswire.org/svn/biblecs/trunk/stage/uilocales.d/ are encoded as
>>>ascii though they have the Encoding value set ti utf8. Did anyone try
>>>saving one of these files as utf8? Do we have any
>>>working locales file that actually uses utf8 encoding?
>>
>>The de.conf file contains unicode umlaut characters.
>>Is your arabic utf8 locale file available somewhere so we can test it?
>>
>>Joachim
>>--
>><>< Re: deemed!
>>
>>
>>
> 
> 
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page