Thread: unusual keymappings in Cream 0.21
Cream is a free, easy-to-use configuration of the Vim text editor
Brought to you by:
digitect
From: Christian G. <go...@ya...> - 2003-04-14 12:21:00
|
Hello, I use Cream on a Win2000. Since I installed (manually) the latest release of Cream 0.21 I have the following problem (unconvenient behaviour): To get a "á" I have to type ´and then 3 times the a to get a "é" I have to type ´ and then 3 times the e to get an "ó" I have to type ´ and then 4 times the o to get an "ú" I have to type ´ and then 5 times the u The same thing holds when I use these accents: ^ ´ ` When I copy/paste text with accents into vim I get the following (in the display): "allocations de ch<f4>mage d<e9>pend de votre derni<e8>re r<e8>mun<e9>ration" instead of : "allocations de chômage dépend de votre dernière rémunération" However when I copy/paste the text back to another program I have my accents back. In the elder versions of Cream I never had a problem like this. Thanks Christian __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com |
From: Milan K. <ko...@vo...> - 2003-04-14 13:00:04
|
Hi, JFYI on my PC there are no problems with accented characters in Cream 0.21 and W2k (and in Czech thtere is a lot of accented characters :)). Best regards, Milan -----Original Message----- Monday, April 14, 2003, 2:20:48 PM : CG> Hello, CG> I use Cream on a Win2000. CG> Since I installed (manually) the latest release of=20 CG> Cream 0.21 I have the following problem (unconvenient CG> behaviour): CG> To get a "=E1" I have to type =B4and then 3 times the a CG> to get a "=E9" I have to type =B4 and then 3 times the e CG> to get an "=F3" I have to type =B4 and then 4 times the o CG> to get an "=FA" I have to type =B4 and then 5 times the u CG> The same thing holds when I use these accents: CG> ^ =B4 ` CG> When I copy/paste text with accents into vim I get the CG> following (in the display): CG> "allocations de ch<f4>mage d<e9>pend de votre CG> derni<e8>re r<e8>mun<e9>ration" CG> instead of : CG> "allocations de ch=F4mage d=E9pend de votre derni=E8re CG> r=E9mun=E9ration" CG> However when I copy/paste the text back to another CG> program I have my accents back. CG> In the elder versions of Cream I never had a problem CG> like this. CG> Thanks CG> Christian CG> __________________________________________________ CG> Do you Yahoo!? CG> Yahoo! Tax Center - File online, calculators, forms, and more CG> http://tax.yahoo.com CG> ------------------------------------------------------- CG> This sf.net email is sponsored by:ThinkGeek CG> Welcome to geek heaven. CG> http://thinkgeek.com/sf CG> _______________________________________________ CG> cream-general mailing list CG> cre...@li... CG> https://lists.sourceforge.net/lists/listinfo/cream-general -------------------------------- |
From: Steve H. <dig...@mi...> - 2003-04-16 02:20:18
|
Christian Goebel wrote: > Hello, > > I use Cream on a Win2000. > Since I installed (manually) the latest release of > Cream 0.21 I have the following problem (unconvenient > behaviour): > > To get a "á" I have to type ´and then 3 times the a > to get a "é" I have to type ´ and then 3 times the e > to get an "ó" I have to type ´ and then 4 times the o > to get an "ú" I have to type ´ and then 5 times the u > > The same thing holds when I use these accents: > ^ ´ ` > > When I copy/paste text with accents into vim I get the following (in > the display): > "allocations de ch<f4>mage d<e9>pend de votre > derni<e8>re r<e8>mun<e9>ration" > instead of : > "allocations de chômage dépend de votre dernière > rémunération" > > However when I copy/paste the text back to another program I have my > accents back. > > In the elder versions of Cream I never had a problem like this. Sounds like an encoding problem. What do :echo &encoding :echo &fileencoding produce? Do you have any other scripts running or any specific customizations you've added? Somewhere around line 90 in cream.vim, you'll find a line that forces &encoding = utf-8, conditioned upon the developer var being set. Uncomment that single line and restart to force this and let me know if that solves the problem. You might also force the file encoding for any specific file giving you problems, too, especially if it was created in some other app. UTF-8 encoding may become official next release. I wanted to wait to test this for a while myself before making it official. The next alpha already indicates &fileencoding in the status line and has the beginnings of a menu for over-ride, too. UTF-8 will someday solve a lot of problems, but many apps, fonts and docs use other standards now so this may shock some people. ;) (Similar to what I believe you are now experiencing! For example, the "prettier" invisible characters will regress to "$" and ">". :( ) -- Steve Hall [ dig...@mi... ] Cream... a familiar feel for the famous Vim text editor! http://cream.sourceforge.net |