Results 1 to 5 of 5

Thread: CNV5 Fonts Not Working in Word List Manager Creation

  1. #1
    Join Date
    May 2004
    Posts
    123

    Default CNV5 Fonts Not Working in Word List Manager Creation

    I'm unable to get the correct fonts to display in the word list manager. Anyone know why that might be?
    I am running BW8 on a Windows 7 machine.

  2. #2
    Join Date
    Apr 2004
    Posts
    916

    Default

    The Chinese fonts (and some others, e.g. Thai) are double byte-versions, which means (as I understand it) that each character requires two (or more?) key strokes to create it. The words are not divided from one another, so the BW programmers have no way of knowing which groups of characters make a word. They just make sure that these versions display as in printed editions. But searching on them has to be done by individual characters or by strings. And copying them into the WLM appears to use the underlying code (two underlying characters for each Chinese character), rather than displaying them in the Chinese fonts. I think that they display in Unicode in the browse window, and they certainly copy into the editor in Unicode, but BW does not use Unicode internally, and apparently the WLM does not display Unicode at all. You can make a request to display Unicode in WLM, and there has been talk about converting to Unicode in many ways, but that would be a massive undertaking, and I suspect that it would slow down many aspects of the program.
    Christ's,
    Mark Eddy

  3. #3
    Join Date
    Jul 2008
    Posts
    20

    Default

    Quote Originally Posted by Mark Eddy View Post
    The Chinese fonts (and some others, e.g. Thai) are double byte-versions, which means (as I understand it) that each character requires two (or more?) key strokes to create it. The words are not divided from one another, so the BW programmers have no way of knowing which groups of characters make a word. They just make sure that these versions display as in printed editions. But searching on them has to be done by individual characters or by strings. And copying them into the WLM appears to use the underlying code (two underlying characters for each Chinese character), rather than displaying them in the Chinese fonts. I think that they display in Unicode in the browse window, and they certainly copy into the editor in Unicode, but BW does not use Unicode internally, and apparently the WLM does not display Unicode at all. You can make a request to display Unicode in WLM, and there has been talk about converting to Unicode in many ways, but that would be a massive undertaking, and I suspect that it would slow down many aspects of the program.
    Christ's,
    Mark Eddy
    Will it help if the source CNV text is supplied in/converted to unicode rather than double-byte fonts before making the module?

  4. #4
    Join Date
    Apr 2004
    Posts
    916

    Default

    Quote Originally Posted by acheung View Post
    Will it help if the source CNV text is supplied in/converted to unicode rather than double-byte fonts before making the module?
    No. If I remember correctly, a number of years ago someone made a digital copy of CUV available in a Unicode font, but for BibleWorks to use CUV, a different database had to be used. I am speaking at the limit of my knowledge at this point (perhaps I have gone over my limit). But the way BibleWorks does searches is different from the way most programs "Search" function works. That is why BibleWorks searches can use wildcards (e.g. ? and *) in all European languages as well as Hebrew and Greek. These wildcards have to be built into the font and not be confused with a character. The speed of BW seems to come because it apparently does not search for every individual letter, but has come up with a way of searching words. Since Unicode fonts treat every variation of every letter as a different character (e.g. in European languages an accented letter is considered a totally different letter from the unaccented letter in the Unicode fonts), the way Unicode is searched appears not to be compatible with BibleWorks search system, at least at the present time. But I have no knowledge of what the BibleWorks programmers may be doing behind the scenes to accept Unicode databases as input.
    Mark Eddy

  5. #5
    Join Date
    Aug 2011
    Posts
    2

    Default

    Sorry ,I don't know,anyway,thanks for sharing!!By the way,Do you want to keep your iPhone 4 always safe and shinning by covering it with smooth iPhone 4 cases or iPhone 4 bumpers?Espow offers you multiple iPhone 4 cases and iPhone 4 bumpers from full body protector silicon cases to a combination of rubber and molded plastic bumpers.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •