36 replies to this topic

[Jogegore]

Hello everyone!

 

I need your help please.

I do not understand why, when I open a ".bblx" file from Modules>Bible>Read Bible File book chap:verse in e-Sword ToolTip Tool NT v2.37 not appear the accents or ñ letter correctly.

Consider the following paragraph as an example (my Bible translation is in Spanish):

 

÷G‚n 1:1 En [el] principio*^a Dios*^b creó^c los cielos y la tierra.^d 

G‚n 1:2 Ahora bien, resultaba que la tierra se hallaba sin forma y desierta y había oscuridad sobre la superficie de [la] profundidad acuosa;*^e y la fuerza activa* de Dios se movía de un lado a otro^f sobre la superficie de las aguas.^g

G‚n 1:3 Y Dios procedió a decir:*^h “Llegue a haber luz”. Entonces llegó a haber luz.ⁱ

G‚n 1:4 Después de eso Dios vio que la luz era buena, y efectuó Dios una división entre la luz y la oscuridad.^j

G‚n 1:5 Y Dios empezó a llamar a la luz Día,^k pero a la oscuridad llamó Noche.^l Y llegó a haber tarde y llegó a haber mañana, un día primero. 

 

Why is this happening? How I can fix this problem? Is it because of the ANSI or UTF-8 encoding?

Also, when I try to save the ".bblx" file from Modules>Bible>Save Bible File book chap:verse (because I have made some corrections), I get error the following legend: "Bad Reference".

What is really happening?

 

Greetings and thanks in advance for any help you can give me.

Attached Files

•  Not appear the accents or ñ letter correctly.png   708.05K   18 downloads
•  Bad Reference.png   546.08K   19 downloads

[Katoog]

It is because the Spanish Bible module maker did not use Unicode but RTF code or another method.

Search for the  à (every broken letter use an à followed by another symbol)

 

G‚n=Gen

Stop with the bad edits.

 

for example  ó =ó

Click on edit menu and replace

copy  ó to the first field and copy ó to the second field

"Match case" must on

Replace All

 

G‚n

Gen

Replace All

Search again for an à with Ctrl+F or edit menu and Find

 

If you save it then save it with Unicode!

Edited by Katoog, 12 October 2014 - 05:50 AM.

[BH.]

I would like to the original BBLX file as this does not make sense to me, can you post the file or say exactly where to download it? The verse designations are added by T4 when reading the file and they are corrupted.  So something else is going on.  

[Jogegore]

Thanks "Katoog" and "BH" for your answers.
 
Although to make replacements is a good idea, I would not do it.
Adjunct the original file ".bblx".

 

http://www.mediafire..._de_Jehova).exe

 

Will there be any other solution?

[Katoog]

Thanks "Katoog" and "BH" for your answers.
 
Although to make replacements is a good idea, I would not do it.
Adjunct the original file ".bblx".

 

Will there be any other solution?

Then what is the point except improving a corrupt Bible translation for your collection? (It is the Spanish version of the "New World translation")

I don't waste my time with this doctrine edited translation and JW Bibles are here forbidden to upload.

[Jogegore]

Exact Katoog!

 

 

If you want to see it that way "improving a corrupt Bible translation for your collection", YES.

 

Regardless of the Biblical translation, I would like that we focus on the problema that I present:

Why not Appear the letter ñ accents or when you 'open the file ".bblx" in e-Sword ToolTip Tool NT v2.37?

 

Actually, this problem can occur regardless of the translation that is.

 

So how I can solve this problem regardless of the translation?

 

Greetings.

[BH.]

A brief look at the issue is that the RTF code is also encoded as UTF-8, so that high ASCII values are in UTF-8 instead of RTF encoded unicode, \uXXX? format.  There is not a simple solution for this at this time using T4.   

[BH.]

I have a solution.  It does require a reworking of my code and some testing.  You can see the results in the attached screen shot.  I'm not sure when I will have a new version of T4 ready with this as it will require me going through all my code and looking at this issue in all module types.

 

 T4 Test1.jpg   90.92K   16 downloads

 

 

[APsit190]

I have a solution.  It does require a reworking of my code and some testing.  You can see the results in the attached screen shot.  I'm not sure when I will have a new version of T4 ready with this as it will require me going through all my code and looking at this issue in all module types.

 

T4 Test1.jpg

Brent,

I'm currently working on getting the rtf code for (what I call) the extended Latin (or it you prefer, Roman) characters. I'll try to get it all done in about two days at best, or three days at the latest. Then upload it as a pdf file (in the similar way I've done the Hebrew and Greek characters).

 

Blessings,

[BH.]

I have posted an update to T4, v2.38 which assumes data is encoded in UTF-8 when reading BBLX files.