[jsword-devel] Problems getting started / Translation of UI

[Benny Wasty]

Hi,
now I found the time to get my JSword development environment running 
again (I reinstalled my computer a while ago).
I don't have the font problem anymore now but I had a few different 
problems which could be solved by deleting the contents of the 
.jsword-folder under "Documents and Settings". Might it be a problem 
that my installed version 1.0.7 and the development version use the same 
directory there?. And would it be possible to take a different folder 
for the development version? Or how could I ensure that there are no 
conflicts?

Concerning the translation: The umlauts (characters with diacretics) 
look fine as far as I saw it. The question marks were probably in the 
files I edited before I knew JInto. I think one changed file got lost 
(in the "path editor" under "Sword Books Properties" in the options), 
but I think I'll send another patch for that in a few days as I want to 
improve the translation a little more anyway (I'm not quite happy with 
some formulations and the ftp-site-editor is still not translated).
Do you know already when exactly you will release the new version? I'm a 
little busy right now but I'd hurry a bit to get the translation done if 
you want to release very soon...

Benny


DM Smith schrieb:
> Benny,
> 	I'm sorry I didn't apply your patch right away. I typically try to  
> get on it as soon as possible. I had a few problems applying the  
> patch. I saw that there were some question marks rather than  
> characters with diacritics. I took my best guess as to what the  
> characters should have been (I studied a little bit of German in  
> college, and that was almost 30 years ago. So please verify my work).  
> Also, the property files can be ascii only with unicode characters  
> being escaped. I did this by opening each file with the JInto Eclipse  
> plugin and saving it with that.
>
> I think I fixed the problem of being unable to switch to English. The  
> problem was that I did not set the default locale if the user choose  
> English. I'm not happy with how I did it as we have about 30  
> translations of Bible book names and this change hides all of them.
>
> Did you ever figure out the font problem? I have never seen that  
> problem. (Has anyone else seen it?)
>
> Many, many thanks for your effort. It is greatly appreciated.
>
> We serve better when we serve Christ together,
> 	DM
>
>
> On Sep 22, 2007, at 5:52 PM, Benny Wasty wrote:
>
>   
>> Hi,
>> this is my first mail to the list, so a short introduction: I'm from  
>> Germany and I'm currently studying Software Engineering. I know the  
>> Sword Project for quite some time and have also followed the mailing  
>> lists for a few months. Now I've found the time to really get  
>> involved and start programming etc.
>>
>> The first problem I have is a warning that shows up (when I compile  
>> and run BibleDesktop in eclipse):
>> -----
>> 21.09.2007 00:43:57 org.crosswire.common.swing.FontStore load
>> WARNUNG: Unable to load the font store: file:/C:/Dokumente%20und 
>> %20Einstellungen/Benny%20Wasty/.jsword%5CBookFonts.properties
>> -----
>> The result is that the font of the bible text is different  
>> (something with serifs, and smaller, too small) compared to my  
>> installed version (1.07). Anyone knows what could be the reason?
>>
>> I started improving the German translation of the UI because it's  
>> quite bad and incomplete. The attached patch contains the changes  
>> (only .properties-files). It's not perfect and also not totally  
>> complete, but */much /*better than the current translation...
>>
>> The language-property-files are a bit problematic in my opinion.  
>> Weren't too easy to find in the first place, there are many and  
>> they're spread among quite a few directories. Would be really  
>> helpful to keep the translations in one place, maybe even in one  
>> file. Adding new languages would also be easier then.
>>
>> And there's a bug with the selection of the translation:
>> I always see the German version, no matter if German or English is  
>> selected in the options menu. Switching to Turkish or Persian is  
>> possible though. I looked into the code and debugged a little, but  
>> couldn't find anything yet. Maybe it has something do to with my  
>> operating system's language being German...
>>
>> Enough for the first mail...
>>
>> Benny Wasty
>>
>> < 
>> jsword_german_translation 
>> .zip>_______________________________________________
>> jsword-devel mailing list
>> jsword-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/jsword-devel
>>     
>
>
> _______________________________________________
> jsword-devel mailing list
> jsword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/jsword-devel
>
>