WordPerfect can save text as Unicode -- have you tried writing your
document in WordPerfect and saving it that way? Otherwise, according to
the documentation, it may not automatically recognize a text as being in
Unicode (though when you import it, WP should give you a message to confirm
file format, at which point you can select Unicode).
If that doesn't do the trick, then your best bet is to bring the question
to the WordPerfect SGML newsgroup, at
news://cnews.corel.com/corel.wpoffice.sgml. This is a peer group, and
volunteers from CNET provide the main source of advice and can notify Corel
when they find a true bug -- Corel itself doesn't monitor the newsgroup.
Hope that helps.
At 07:49 PM 2/19/01 +0100, you wrote:
>On 11 Jan 2001 Tobin Nellhaus wrote:
>> Since WordPerfect has dictionaries for many languages (select the ones
>> you want when you install), it should work fairly well. Its XML/SGML
>> system has a couple of problems (in particular, you have to compile
>> the DTD into a template, and it uses its own style system rather than
>> XSL), but otherwise it's reasonably good.
>I have tried WordPerfect 9 with teixlite.dtd v1.3 and it compiled
>without problems... when I removed the NOTATIONs block. I guess
>there should be the obligatory SYSTEM identifiers - perhaps just ""?
>I have also (re?)discovered a potentially serious problem with
>WordPerfect support for Unicode. When a text is typed in a true
>Unicode editor (eg. UniPad or MSWord) and then opened in or imported
>into WordPerfect, the unsupported characters are *silently* replaced
>with a space! Using cut-and-paste is much worse, as it modifies also
>the supported characters - but at least one can see it at a glance.
>I noticed this behaviour while working with a German text using
>the "long-s" (ſ) which was also easy to notice - but with
>a long text containing just a few unsupported characters here
>and there this may lead to serious errors in the text itself.
>Is there a list of which Unicode characters (code points)
>have their WordPerfect equivalents? The solution is to have
>the unsupported ones converted to &entities; before loading
>Otherwise, it is indeed quite good and nice to use.
Librarian for Drama, Film and Theater Studies
[log in to unmask]