Re: Non-Latin Characters Disply in the VIM for Win32

2008-11-20 Fir de Conversatie Szabolcs


Most Windows programs, like Notepad, will use different fonts for
different types of characters.

Even if Notepad is set to use Courier New, it will use a different
font to display e.g. Chinese characters.  Windows Vim does not do
this.  It only uses the font that is specified in the options.
Courier New does not include any Chinese characters, so if you need
Chinese characters, you'll need to use a different font, e.g. MS
Mincho.

For some reason Windows does not use anti-aliasing for any of the
fonts that includes CJK characters, so with these fonts, even Latin
letters will be ugly ...

I wish Windows Vim could automatically select the proper font for
different types of characters, like most other Windows programs do ...
The Gnome version of Vim can already do this.

Will we ever get this feature in Windows Vim?

--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---



Re: Opening files with Unicode names under Windows?

2008-09-13 Fir de Conversatie Szabolcs Horvát
On Sat, Sep 13, 2008 at 16:09, Bram Moolenaar wrote:

 I wonder why this has not been a problem before.


It is not surprising that this does not come up often.  Those people
who use localized versions of Windows are less likely to run into such
problems (for example on a Hungarian Windows system the default
encoding does include ő and ű).  The rest of us learn quickly that it
is best to avoid file names with characters that are not present in
the system encoding.  Even today there are many programs that don't
understand Unicode, and these file names can cause all kinds of weird
problems (like a picture viewer skipping them in a slide show, or even
worse: a CD burner program silently omitting them from the CD ...)

Also the names of those files that are most commonly edited with Vim
(like source code) are unlikely to contain non-ascii characters.

--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---



Re: Opening files with Unicode names under Windows?

2008-09-11 Fir de Conversatie Szabolcs



On Sep 11, 1:08 am, Tony Mechelynck [EMAIL PROTECTED]
wrote:
 On 10/09/08 22:59, Szabolcs Horvát wrote:

  2008/9/10 Szabolcs[EMAIL PROTECTED]:
  It turns out that I was wrong.  Vim *can* open these files if I use
  the :e command, or I browse to the file with Vim as you suggested, or
  I just drag it onto the Vim window.  The problem is only present when
  I use the Edit with Vim entry of the right click menu.  So I suppose
  that the gvimext shell extension is the culprit.

  It seems that gvimext does not support Unicode file names, so I
  attempted to fix it ...  However, I am not a programmer, and I know
  absolutely nothing about Windows programming (I just Googled for
  documentation) ...  I would appreciate it very much if someone could
  take a look at my primitive effort to add Unicode support, and tell me
  if I did something stupid.  (It does appear to work when tested with
  the őű.txt file.)

 Well, I don't know anything about programming Windows for Unicode but
 you might test the following names (I'm adding quotes because some of
 them have spaces)

         Э-эй ухнем.txt
         Ĉu.ĉi-tie.ĉiuaŭtune.ŝiriĝas.folioj.htlm
         爲無爲、則無不治。.txt
         أَلسَّلامُ عَلَيْكَمْ.txt

 Paste them, don't hand-copy them ;-). I don't think the content of the
 files matters. I expect the last two to be particularly difficult
 because of the high CJK codepoints and the RTL Arabic words with
 composing characters in them. I don't guarantee that all values are
 permitted as filenames but they are meaningful text (well, more or
 less; let's say they're linguistically OK) and I intentionally didn't
 use question marks and asterisks (which I think are

Yes, all of these names are working.
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---



Re: Opening files with Unicode names under Windows?

2008-09-10 Fir de Conversatie Szabolcs



On Sep 10, 9:22 pm, Tony Mechelynck [EMAIL PROTECTED]
wrote:
 On 10/09/08 21:00, Szabolcs wrote:



  I do have

  set enc=utf-8

  in my vimrc, but Windows gVim (on English WinXP) still cannot open
  files with non-latin1 characters in the name.  For example, opening
  őű.txt will try to open ou.txt.  I use version 7.2 downloaded from
 www.vim.org.  What might be the difference between my and Vadim
  Zeitlin's setup?

 I don't know. Vadim is using Cyrillic characters in his filenames and
 you're using accented Latin, but should that make a difference?

 Can you browse a directory containing that kind of files, and are the
 filenames displayed correctly?

 Let's say you try

         :cd magyar
         :view ./

 (or similar) how are the filenames displayed? If you put the cursor on a
 Hungarian double-acute-accented vowel and hit ga -- what does Vim answer?


Hello Tony,

It turns out that I was wrong.  Vim *can* open these files if I use
the :e command, or I browse to the file with Vim as you suggested, or
I just drag it onto the Vim window.  The problem is only present when
I use the Edit with Vim entry of the right click menu.  So I suppose
that the gvimext shell extension is the culprit.

There are easy workarounds, so this is not a serious problem.  I just
got so used to using the right-click menu for opening files with Vim
that I didn't even try other methods ...

Szabolcs
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---



Re: Opening files with Unicode names under Windows?

2008-09-10 Fir de Conversatie Szabolcs Horvát
2008/9/10 Szabolcs [EMAIL PROTECTED]:

 It turns out that I was wrong.  Vim *can* open these files if I use
 the :e command, or I browse to the file with Vim as you suggested, or
 I just drag it onto the Vim window.  The problem is only present when
 I use the Edit with Vim entry of the right click menu.  So I suppose
 that the gvimext shell extension is the culprit.


It seems that gvimext does not support Unicode file names, so I
attempted to fix it ...  However, I am not a programmer, and I know
absolutely nothing about Windows programming (I just Googled for
documentation) ...  I would appreciate it very much if someone could
take a look at my primitive effort to add Unicode support, and tell me
if I did something stupid.  (It does appear to work when tested with
the őű.txt file.)

--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---



gvimext.patch
Description: Binary data


Fortran plugin and vimrc_example

2008-05-25 Fir de Conversatie Szabolcs

The Fortran plugin's documentation gives instructions on how to enable
automatic selection of source format (fixed or free form) based on the
file extension (see :help fortran).  It also mentions that this will
only work if the filetype plugin indent on line precedes the syntax
on one in vimrc.  This is not true for the included vimrc_example.

Unless there is a reason not to, it would be nice to swap the order of
these two lines in the 'official' vimrc_example to make sure that it
is compatible with the Fortran plugin.
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---



Re: .nb files are Mathematica notebooks

2008-01-17 Fir de Conversatie Szabolcs



On Jan 17, 8:35 pm, Bram Moolenaar [EMAIL PROTECTED] wrote:
 I also see *.nb files listed as Nota Bene text files.  I don't know what
 Nota Bene is, but perhaps the file contents can be checked to be
 something that looks like Mathematica?


According to http://filext.com/file-extension/nb, Nota Bene is a
word processor and bibliographic manager.

Mathematica notebooks always begin with a comment, i.e. (* (without
the quotes).  I am not sure whether there may be any whitespace before
the (*, but none of the notebooks I checked (created by versions 3.0,
5.2 and 6.0) had any.  So perhaps any *.nb file whose first two
characters are (* could be linked to the mma file type?

Szabolcs
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---



.nb files are Mathematica notebooks

2008-01-16 Fir de Conversatie Szabolcs

Currently only *.m files are recognized as mma filetype
(Mathematica).  *.nb files can also be safely linked to the mma file
type, as Mathematica notebooks just contain one big Mathematica
expression.

Of course one does not normally edit raw notebook files with a text
editor, but syntax colouring is useful for reading them.
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---