<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
I wouldn't call it "racist," but it is a difficulty for languages that
have hyphenated biblical names (Vietnamese is included in this). In
Vietnamese the hyphens can be dropped and the book names can still be
understood. I can see how the presence of hypens within names would
pose a coding challenge since ranges are marked with a hyphen. Is there
no way to change it?<br>
<br>
Using only ascii presents a challenge because diacritics are lost, and
non-latin languages cannot be displayed. If
the Sword Project is to become truly international (especially adding
Asian-language modules), strings like
biblical names need to be able to be rendered in unicode. <br>
<br>
I was working
on a Vietnamese genbook last night, and the difficulty I ran into in
BibleCS (and to a lesser extent BibleTime) is that the navigation panes
do not display unicode properly. I either drop diacritics entirely (and
lose them in BibleDesktop and Gnome Sword which do display unicode) or
I leave them and let the
chapter titles, etc. appear as jumbled nonsense in the BibleCS and
BibleTime navigation panes (thankfully BibleTime's navigation combo
boxes do display unicode, but most Vietnamese users will be using
Windows). If I leave the unicode, it
looks great in Bible Desktop and Gnome Sword. However, that still
leaves one limitation with the *.conf files. Book titles can only be
displayed in
ascii. This is acceptable in Vietnamese but not very professional. I
know there was discussion on the developer's forum recently about rtf
in the conf files. If there is any way to change conf files to unicode,
I would plead for such a change for the sake of making The Sword
Project a viable option internationally.<br>
<br>
To summarize, for the sake of continuing internationalization of the
Sword Project, I recommend two things (I wish I were a developer so I
could help out, so please take my recommendations as a wish list--I
don't mean to be
ungrateful for the quality work developers have already put into the
Sword engine and its various front-ends):<br>
1. Make it possible for the "Description" field of the conf files to
use unicode, if not make the whole conf file unicode.<br>
2. For BibleCS and BibleTime, make it possible for the navigation panes
to display unicode. This item is more urgent for BibleCS because
BibleTime's combo boxes make up for the navigation pane's limitations.<br>
<br>
Daniel<br>
<br>
Eeli Kaikkonen wrote:
<blockquote cite="midPine.GSO.4.58.0710211717440.15152@paju.oulu.fi"
type="cite">
<pre wrap="">On Sun, 21 Oct 2007, Hariyanto Handoko wrote:
</pre>
<blockquote type="cite">
<pre wrap="">And there is bug in Judge (Hakim - hakim) , I only can see Hakim-hakim 1. .
Sword doesn't support sign -
And I change in file id.conf in line 13 become : Judge = Hakim.
</pre>
</blockquote>
<pre wrap=""><!---->
It's quite natural because '-' is used as a sign of a range, for example
Genesis-Deuteronomy is the same as Genesis 1:1 - Deuteronomy 34:12 and
Genesis-Genesis1 is the same as Genesis 1:1 - Genesis 1, which is the
same as Genesis 1:1 - Genesis 1:31 or just Genesis 1.
This is a difficult situation. The simple solution is to disallow the
'-' character (as well as ':', ',', '.', ';' etc.) in book names. But it
may be as "racist" as using ascii only.
Yours,
Eeli Kaikkonen (Mr.), Oulu, Finland
e-mail: <a class="moz-txt-link-abbreviated"
href="mailto:eekaikko@mailx.studentx.oulux.fix">eekaikko@mailx.studentx.oulux.fix</a> (with no x)
_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated"
href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext"
href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page
</pre>
</blockquote>
</body>
</html>