Re: lynx-dev Re: [dev.15] fixup patch: edit TEXTAREA

[Leonid Pauzner]

29-Jan-99 19:41 Jacob Poon wrote:
> On Fri, 29 Jan 1999, Kim DeVaughn wrote:

>> On Fri, Jan 29, 1999, Jacob Poon (address@hidden) said:
>> |
>> | I am wondering, if an external editor is used to edit files in TEXTAREA,
>> | will the unprintable characters get filtered out as well?  The reason of
>> | concern is that it is possible that Lynx cannot print the text in
>> | TEXTAREA, but the external reader can (eg: text in TEXTAREA is encoded in
>> | Unicode, and Lynx cannot use the proper font, so external editor is

Lynx does not support raw Unicode 16bit (UCS-2),
it allows UTF-8 instead which is us-ascii compatible and safe,

>> | required to read/write Unicode).  If this patch sends a filtered version
>> | of data when launching external editor, Lynx will destroy the TEXTAREA
>> | contents and makes the filtered texts unreadable on any editor, which
>> | partially defeats the purpose of external editing.
>>
>> No filtering is performed in that direction (lynx --> edit file).
>>
>> The filtering is only performed in the other direction (file --> lynx),
>> and is only performed on byte values of x'00' - x'1F' (with TAB's being
>> expanded to spaces, mod 8).

> This may still represent some problems.  For example, if the encoding of
> externally edited file depends on byte values 0x00 to 0x1F (eg: UCS-2) as
> part of encoding, some text data may get lost.

>> I think that's OK, WRT Unicode, isn't it ...?

> Not when the page uses non-escaped Unicode character sets (eg: UCS-2,
> UCS-4), which uses the first 32 byte values.

Such pages not supported by lynx in any case, not only forms.