From: Alexej Kryukov (firstname.lastname@example.org)
Date: Tue May 02 2006 - 12:47:04 CST
On Monday 01 May 2006 23:11, Philippe Verdy wrote:
> No it does not work for me: I can't match spans of text that cover
> several lines. the \n just matches the final \n at end of line but
> not anything else after it.
What exactly you are doing to search for a newline character? For me
:/\n<enter> highlights all ends of lines in the current buffer, while
:%s/\n//<enter> removes all newline characters at all (or replaces
them with whatever I want). If this is not that you need, please
describe the problem more precisely.
> This is where there are some tricks with international text. The
> supports works inthe GUI provided that it works in the console based
> version. There are serious issues with clusters.
This is just a prejudice. In fact Vim can handle texts in almost
any known encoding internally, while the console environment just
implies some limitations (i. e. requires the text to be converted
into a specific encoding before it can be rendered). For this
reason the GUI versions of Vim (for any system, including win32) are
much more powerful and more suitable for editing multilingual texts.
> Also the windows version of Vim has some problems created only by the
> ported GUI that isnot required for Unix/Linux as it works fine with
> just the console version in a X11 window. This all depends on the
> capabilities of the console terminal on X11 (and so from the X
> terminal used which dependson the X11 font rendering) and so the
> Unix/Linux system must have support for UTF-8 text consoles and so
> the X terminal must support this encoding and be able to use OpenType
> fonts instead of just the common legacy bitmap fonts found in many
> X11 distribs.
Where the hell you have red such things? Well, of course, any
modern Linux distribution does include Unicode-enabled console
terminals, but, AFAIK, none of those terminal applications
depends from some special OpenType fonts. For example the -misc-fixed
font I have mentioned is a "legacy bitmap font"; nevertheless is a
Unicode font and actually has more complete character coverage than any
other Unicode font I know.
> Vim assumes the capabilities of the terminal using the TERM
> environment and support libraries that implement the terminal
> capabilities. This setting ishard to emulate on Windows, so it's
> necessarily imperfect.
Forgot about terminal versions. I have used the GUI version of
Vim (first under Windows and then under Linux) for a quite long
time for editing multilingual (Latin + Cyrillic + Polytonic
Greek) texts for a long time, and I am perfectly satisfied
with the multilingual support. If you have any specific problems,
please describe them.
-- Regards, Alexej Kryukov <akrioukov at newmail dot ru> Moscow State University Historical Faculty
This archive was generated by hypermail 2.1.5 : Tue May 02 2006 - 13:08:09 CST