24 replies to this topic

[SeongHeon Jeon]

Hi 

With you guys' help I managed to solve the problem i had before  

http://www.biblesupp...op-of-document/

Thanks to you, I was able to make my own Korean version of Bible and Commentaries.

 

However, when I tried to make a Dictionary module

I found that all the title words written in Korean is shown to be question marks as the screen shot attached

 

I've tried this on 2 different computers that yielded the same results

 

So again I'm looking for a help

 

I've attached the sample text file that I used and a screen shot

Please help

 

Thank you.

Attached Files

•  sample.txt   4.21K   2 downloads
•  스크린샷 2013-10-03 오후 3.07.54.png   41.51K   24 downloads

[BH.]

This is not a T4 issue.  The top word title is generated by e-Sword.  

[Tim Butterfield]

It could be a font issue.  What do you have set for the Korean font?

[BH.]

It is not a font issue.  It is a unicode conversion issue in the tools used to build e-Sword PC. 

[Josh Bond]

It is not a font issue.  It is a unicode conversion issue in the tools used to build e-Sword PC. 

 

Brent is right. You see the same issue if you try to put Greek or Hebrew words as a dictionary entry title. e-Sword doesn't support unicode in this area.

[BH.]

Convert the same file to e-Sword HD, and it appears correct.  

 

This issue does not lessen the utility of e-Sword.  The word in question is in the list at the right.  The definitions appear correct.  e-Sword is still a most useful and user accessible Bible program.  

[SeongHeon Jeon]

Convert the same file to e-Sword HD, and it appears correct.  

 

This issue does not lessen the utility of e-Sword.  The word in question is in the list at the right.  The definitions appear correct.  e-Sword is still a most useful and user accessible Bible program.  

Thank you for your replies 

But my iPad doesn't show any words

I mean I can't search on my dictionary section

 

You said it's working OK on iPad

Cold you tell me what was wrong with my setting?

I used DCTI on mudulesHD variables to call the definition

and used Gulim for the font

and clicked 'save DCTI module'

 

Link under is a trial.dcti that I generated

https://dl.dropboxus...7122/trial.dcti

[BH.]

You are right, the search text is not working 100%.  My point was that the text and the title word at the top DOES convert and display correctly.  

 

 IMG_0218.PNG   120.3K   8 downloads

 

 

[BH.]

Here is the result if you first create a DCTX file, then using the e-Sword converter.  The words now are correct.  (BTW - I have fixed T4 - T4 was saving the words as HTML instead of UTF-8 - oops)

 

 IMG_0219.PNG   77.84K   16 downloads

[SeongHeon Jeon]

Here is the result if you first create a DCTX file, then using the e-Sword converter.  The words now are correct.  (BTW - I have fixed T4 - T4 was saving the words as HTML instead of UTF-8 - oops)

 

IMG_0219.PNG

Do you mean e-Sword PC to iOS User Module Conversion Utility v1.2.0

on http://www.e-sword.net/extras.html  ?

 

It doesn't support *.dctx

Could you tell me what  is the e-Sword converter you said?