683RE: UTF8_STRING patch
- Aug 10, 2002Jason Maiorana wrote:
> >For the conversion, look in mbyte.c. The functions convert_setup() andI dunno. You could try looking in the GTK documentation (but you
> >string_convert() should be able to do it.
> one quick question: how do you determine which is the appropriate
> encoding to pass to "clip_yank_selection".
> It looks like the GDK functions all assume that the data is in the
> format of the current locale: this is incorrect i think. I set
> encoding=utf8 which does not match my en_US locale. I dont have
> really working locales for utf8, if there was an "allLangs_USkbd.utf8"
> locale i would use it.
probably end up looking in the source code...).
> Converting COMPOUND_TEXT to my current locale would only corrupt it,The value of 'encoding' defines the encoding used internally in Vim for
> which probably explains why that never worked for me. Doesnt vim
> have some notion of internal representation encoding? If vim were
> to always use utf-8 internally in all situations, that would make
> UTF8_STRING conversion a non-issue...
all text in buffers, registers, etc.
"Hit any key to continue" it said, but nothing happened after F sharp.
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
/// Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim \\\
\\\ Project leader for A-A-P -- http://www.a-a-p.org ///
\\\ Lord Of The Rings helps Uganda - http://iccf-holland.org/lotr.html ///
- << Previous post in topic Next post in topic >>