On Thursday 21 August 2003 4:55, Kent Karlsson wrote: > Frank Murphy wrote: > > Absolutely on Mac OS. In the US (where therre are no deadkeys), > > Yes there are (see below). > > > in order to type ç on Mac OS (9 & X), press alt/option+c, > > then press c again. alt+u is for umlaut, etc. > > alt/option+c is a "dead key" (the MacOS X UI shows a yellow background > and an indication of which "dead key" you have typed, this disappears > when you type the base character, it being replaced by the combination). > Similarly, alt+u is "dead key" for umlaut. (I don't like the term "dead > key", but that is the common term for it.)
So what's the difference between alt+c on Mac OS and Multi_key+, on X11? Is it just the display of the greyed-out character? I had thought that a dead key was a real key on the keyboard (that had the accent engraved on it) that would not cause a character to be displayed until the next character was typed. > > > > are, then Xkb could be configured with se+dvorak and avoid all the > > > > > > That will not work since the default Swedish map is qwerty-ish one, > > > and åäö are not in the same place as in Dvorak as in qwerty (some > > > punctuation is consequently moved too). > > > > Why won't it work? Whatever is added afterwards should > > override any done > > before (or can be written to do so). > > Apart from differenced in row E between en-US and sv keyboards, > åäö have their unique position in "svorak" (and as a consequence > some punctuation is moved too). That is not expressed by se+dvorak. Sorry. I get it. Just had a brain fade on your explaination. > > I don't know why. Because they are identical for so many > > countries and > > languages. Plus, the main interaction people have with the > > two-letter codes > > is with internet domainnames. > > Yes. > > > And on the internet, .fr is France, not French. > > Eh, no. That is context dependent. In XML (very intenetty) > "xml:lang='fr'" means French, not France... "xml:lang='fr-FR'" > tag French French, "xml:lang='fr-CA'" tags Canadian French, etc. > (Similarly for HTMLs older "lang" attribute.) True, but end users aren't authoring raw XML, but they are typing URLs into their browsers (and seeing ads on TV and billboards) that end in these 2-letter country codes. > > How is this for an idea? I will start with my conservative proposal, > > separating language maps from country maps, and you can start > > with the > > script-based proposal, starting with the Latin and Gujarati > > scripts. As the > > Latin-script work progresses, we can start changing the > > language/country maps > > to include the script maps, making sure that people currently > > using the > > country/language maps still get their expected behavior. > > > > In parallel, we can start to build Brand specific additional > > maps (for Apple, > > Sun, SGI, etc). > > > > What do you think? > > I can start off by sending you the files I've done (with sv bias, > since that is where I started). Then we have something concrete, > and then we can discuss from there. (And maybe change our minds > entirely...) Well, that depends. Are your files script-based or language-based? If they're language-based, then they would be parallel to my concrete proposal, and could just be added (though with the 3-letter code, swe). Frank _______________________________________________ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
