I quite agree! Their way of working seems odd to say the least.
Everytime they do a format shift in this way, we find another few codepoints they forgot to cater for in their complicated (and almost unreadable) SED-based scripts. IMHO, there is nothing to be gained by shifting from Unicode to hexadecimal codes and back again. It is an error prone operation. They seem to be wedded to the SED tool, even though there are much more suitable utilities and programs available in the open-source community. -- David Peter von Kaehne wrote: > > David Haslam wrote: >> There are lots of undecoded codepoints in the text! Here are some >> examples >> from Matthew ch 1. >> http://www.nabble.com/file/p21209279/vlx3_codepoints.png >> >> -- David > > It is a lot better to go directly from the Wiki to OSIS. I can not see > any good reason to use Xephania as a intermediate format. > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > -- View this message in context: http://www.nabble.com/Open-source-German-Volxbibel-tp21183192p21209744.html Sent from the SWORD Dev mailing list archive at Nabble.com. _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page