Subject: Possibly RTF import bug: spaces disappear in non-Latin texts
sam@stl.ru
Date: Sat Jun 03 2000 - 21:13:31 CDT
Hi folks!
Last two weeks I've worked much with texts in Russian usuing Abi. I find
it handy and useful, but there's one strange thing in its behavior.
I use Abi 0.7.9 on Linux.
When I import some .rtf file, Abi keeps spaces in texts, containing only
Latin chars, but "eats up" all spaces in non-Latin texts, e.g. Russian.
Exploring the problem I found that Abi separates words in .rtf files by
double-space (0x20 0x20), while some other editors use single-space
(0x20). So, Russian texts typed in Abi and converted into RTF were
imported back without any damage, but texts typed in Ted were damaged
when I try to open them by Abi.
Next, as I replaced all spaces with double spaces in Ted-generated
document, it was opened by Abi without any damage.
I'm not sure if this an Abi bug, a Ted bug or something else.
I just can state that, unless it doesn't matter in English texts (or
anything else based on Latin characters), there's a significant
difference in RTF import of non-Latin texts, separating words by
single-space or double-space, making first of them unreadable.
So, the questions are:
1. Is it necessary to use double-space (e.g. because of RTF standard)?
If it's not so, why Abi does that?
2. If it's so, is it necessary to require double-spaces in *IMPORT*
rather then just write them in export?
(Here also some sample files, including Abi-generated, Ted original and
patched ones. Each of them contains a short comment and six sample
"words": three "words" containing Latin capital letters A,B,C, and three
"words", containing first three letters of Russian alphabet.
The spaces between "Latin" words are kept everywhere, but in "Russian"
text only in original Abi document and patched Ted document. In
original Ted .rtf all three "non-Latin" words are joined into a single
word.)
SY, Serge Musorin.
This archive was generated by hypermail 2b25 : Sat Jun 03 2000 - 21:19:12 CDT