Re: RichView Package 1.8

From: Sergey Tkachenko (svt_at_trichview.com)
Date: 10/30/03


Date: Thu, 30 Oct 2003 19:21:42 +0300


> The unicode support has to be enabled in the File menu under Options.
> It is disabled by standard.

Works ok for me (under WinXP)

>
> The right-to-left support this demo is set to 'dumb' - it will turn
> the complete text except for number, not only the hebrew or arabic
> charsets which would be the automatic mode. It is just a demo.

Look ma, I got a mirror :) But this is not what I can call a support for
bidirected text.
Does your automatic mode rely only on a charset? I think it is an
oversimplification of the problem:
- Unicode characters do not have charsets (well, it depends on what do you
call "charset");
- Arabic and Hebrew charsets include LTR characters (and they are not only
digits);
- LTR/RTL attribute of some characters depends on properties of adjacent
characters, as well as on a global LTR/RTL mode.

> >Your site states that WPtools Unicode support requires WinNT. Hmm....
> >Does it mean that Unicode documents will contain ???? when editing under
> >Win95-98-ME?
> WPTools uses the standard TextOutW function here - So I expect it
> depens on the character.

TextOutW must work under Win9x. So if it's the only function that you use
for processing Unicode text, you are too modest in specifying limitations :)

> A big amount of time went into the handling of the cursor movement,
> selection and shortcuts - since I don't think Words word selection is
> 'smart' it is not supported (I hate Word for it).

It can be turned off in TRichView (TRVStyle.SelectionMode property).
But I do not think that it's a completely harmful feature: characters can be
selected when moving mouse in a backward direction.

But doubleclick to
> select word + space works (I don't see this in your demo :-)

I can see that dblclick selects a word without space (and who needs this
space?), just like in TRichView editor.

> Well - I did not state that these are all unique features and it is
> also not necessary that they are. It is good for you that your
> customers support you so well. Congratulations!

Thanks :)



Relevant Pages

  • Re: Unicode-based FreeBSD
    ... displaying specialised characters on the screen/tty. ... There are special Input Methods for the rest of Unicode. ... Unicode support and the FreeBSD developers see little reason to ...
    (freebsd-current)
  • Re: Unicode Support
    ... > compiler/assembler is unicode support. ... > but the fact that most assemblers, ... Most popular *editing* tools support this data format. ... Is there really a need to put unicode characters into identifiers? ...
    (alt.lang.asm)
  • Re: Unicode Support
    ... >> compiler/assembler is unicode support. ... >> but the fact that most assemblers, ... Most popular *editing* tools support this data ... > Is there really a need to put unicode characters into identifiers? ...
    (alt.lang.asm)
  • Re: Daily Mail: Rumours Swell that the Government Staged 7/7
    ... correctly and support current charsets. ... ASCII chars to represent them if a newsclient doesn't support the ... If I added some more Latin chars to my header, ... happen to 8-bit bytes rather than to Unicode characters. ...
    (uk.politics.misc)
  • Re: =?ISO-8859-1?Q?Soup=E7on_of_cedilles_and_aper=E7us?=
    ... Note that most of these support only ASCII ... plus a few accented characters, ... Unicode supports, in principle, the characters of every written ... The catch is that not all newsreaders are new enough to ...
    (alt.usage.english)