--
Markus Kuhn, Computer Lab, Univ of Cambridge, GB
http://www.cl.cam.ac.uk/~mgk25/ | __oo_O..O_oo__
___
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/i18n
that you need?
Markus
--
Markus Kuhn, Computer Lab, Univ of Cambridge, GB
http://www.cl.cam.ac.uk/~mgk25/ | __oo_O..O_oo__
___
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/i18n
Alan Coopersmith wrote on 2004-08-16 16:35 UTC:
Markus Kuhn wrote:
I have substantially revised and updated the long neglected KEYSYM
Encoding specification in Appendix A of the X11 Protocol Standard. The
result, which I propose for inclusion into the next X.Org release,
is on
http
://freedesktop.org/bugzilla/show_bug.cgi?id=246
There is also a wiki page on the subject on
http://freedesktop.org/XOrg/KeySyms
Markus
--
Markus Kuhn, Computer Lab, Univ of Cambridge, GB
http://www.cl.cam.ac.uk/~mgk25/ | __oo_O..O_oo__
___
I18n
minor editorial fixes for better consistency, comments
added that clarify the Unicode mapping rule.
Unless someone shouts with an objection, I will submit these for inclusion
into the X.Org and XFree86 trees soon.
Proposed update to the X11 standard will follow shortly.
Markus
--
Markus Kuhn
, and not the old MS-Windows one. (Or implement both
together, if you really need MS-Windows compatibility here. They don't
interfere with each other, because the ISO 14755 technique uses
Ctrl-Shift to activate the hex-entry mode, while MS-Windows uses Alt.)
Markus
--
Markus Kuhn, Computer Lab, Univ
major X.Org release.
http://www.cl.cam.ac.uk/~mgk25/unicode.html#x11
Markus
--
Markus Kuhn, Computer Lab, Univ of Cambridge, GB
http://www.cl.cam.ac.uk/~mgk25/ | __oo_O..O_oo__
___
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo
.
Opinions?
Markus
--
Markus Kuhn, Computer Lab, Univ of Cambridge, GB
http://www.cl.cam.ac.uk/~mgk25/ | __oo_O..O_oo__
___
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/i18n
.
Markus
--
Markus Kuhn, Computer Lab, Univ of Cambridge, GB
http://www.cl.cam.ac.uk/~mgk25/ | __oo_O..O_oo__
___
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/i18n
/sophocles/show_mail.tpl?source=Llistname=xorg_archid=16
Keysyms probably will be next. More on the xorg_arch mailing list:
http://www.x.org/XOrg_Foundation_Join_OpenLists.html
Markus
--
Markus Kuhn, Computer Laboratory, University of Cambridge
http://www.cl.cam.ac.uk/~mgk25/ || CB3 0FD, Great Britain
to represent the Unicode character U+abcd.
Also read:
http://www.cl.cam.ac.uk/~mgk25/unicode.html#x11
Instead of xmodmap, also consider to use xkbcomp.
Markus
--
Markus Kuhn, Computer Lab, Univ of Cambridge, GB
http://www.cl.cam.ac.uk/~mgk25/ | __oo_O..O_oo__
Andreas Tobler wrote on 2003-01-03 12:36 UTC:
e.g. key TLDE {[0x0100+0x2030]}
0x01002030
Markus
--
Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK
Email: mkuhn at acm.org, WWW: http://www.cl.cam.ac.uk/~mgk25/
___
I18n mailing
Dr Andrew C Aitchison wrote on 2002-12-13 10:13 UTC:
Looking at the unicode charts (especially the character name index
http://www.unicode.org/charts/charindex.html
) I see that ASCII dot 0x2E has become Unicode 0x002E Decimal Point
and ASCII comma 0x2C has become 0x002C decimal
Thanks for the fast bug fix. I hope, RedHat/Suse/etc. will fix this in
their RPMs *very soon*, otherwise the UTF-8 locales remain completely
unuseable for everyone on an X server without XKBD (e.g., Solaris).
Ivan Pascal wrote on 2002-11-29 12:46 UTC:
But under the UTF-8 locale XLookupString
Juliusz Chroboczek wrote on 2002-11-28 11:36 UTC:
'A knot!' said Alice. 'Oh, do let me help to undo it!'
Could you please put an xscope dump on the web somewhere ?
Thanks! I didn't know about xscope.
The requested dump is now on
http://www.cl.cam.ac.uk/~mgk25/ucs/xev-adiaeresis-utf8.txt
In order to hunt down a very odd problem with the XmbLookupString and
Xutf8LookupString functions, I have extended the good old xev command to
print the output of these two functions as well, in addition to that of
XLookupString.
In order to use XmbLookupString or Xutf8LookupString, one needs to
I think I have run into a serious bug with XFree86's Xutf8LookupString
implementation. It occurs when the client runs under XFree86 4.[12], but
the X server is for example Solaris 5.8
vendor string:Sun Microsystems, Inc.
vendor release number:6410
(also occurs on Solaris 5.7). It
Is the X (4.x) supporting Unicode/16 Bit encoding ? How ?
Yes, to some degree. To get started, try:
http://www.cl.cam.ac.uk/~mgk25/unicode.html
Markus
--
Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK
Email: mkuhn at acm.org, WWW: http://www.cl.cam.ac.uk/~mgk25/
Emil Soleyman-Zomalan wrote on 2002-11-14 16:00 UTC:
Just for my own knowledge, what would be the disadvantage of creating a
new set of keysyms for Syriac as already has been done for several other
languages?
There is nothing wrong in principle with adding new keysyms, however the
integer
Juliusz Chroboczek wrote on 2002-11-12 16:49 UTC:
Use nl_langinfo(3), but it's an SUSv2 interface (i.e. it's not in POSIX)
POSIX.{1,2}:2001 and SUSv4 are the same thing now.
So nl_langinfo(CODESET) is now actually officially part of the holy
dogma of the church of POSIX. Halleluhia.
I had originally argued strongly in favour of a BACKSPACE display
semantics that removes the character left of the cursor (let's call this
character L), and then moves the cursor wcwidth(L) character cells
to the left. This is by far the most sensible solution, because this
way, if you echo the
Oscar A. Valdez wrote on 2002-10-01 22:37 UTC:
How do I configure XFree86 v. 4.1.0 to get ñ,Ñ,á,é,í,ó and ú on a
US-layout keyboard?
If it is only for personal single-user use, then .Xmodmap is still
the simplest solution.
I routinely type German and English text on a UK keyboard with the
Viveka Nathan K wrote on 2002-09-30 10:56 UTC:
I wish to use the unicode encoding.
How can I know, which applications are supporting the unicode.
What should I need to do, to make an application to support unicode ?
Read
http://www.cl.cam.ac.uk/~mgk25/unicode.html
to get started.
Tomohiro KUBOTA wrote on 2002-08-26 08:48 UTC:
The first is that simply using *-iso10646-1 fonts as defaults.
This could already be achieved by changing in /usr/lib/X11/fonts/misc/fonts.alias
the line
fixed-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1
to
fixed
Jungshik Shin wrote on 2002-08-06 15:05 UTC:
You can use one of 18pixel iso10646-1 bitmap fonts included in XF86
4.x with more CJK characters than 13pixel font:
-misc-fixed-medium-r-normal-ko-18-120-100-100-c-180-iso10646-1
-misc-fixed-medium-r-normal-ja-18-120-100-100-c-180-iso10646-1
Attached is an old email that represents the most authoritative
information that I have on the diacritic characters used in dictionaries
of the Welsh language. Hope this helped ...
Markus
--
Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK
Email: mkuhn at acm.org, WWW:
Keith Packard wrote on 2002-07-10 01:09 UTC:
AFAIK, SUS and POSIX say
that it's implementation-dependent.
Too bad the POSIX spec is closed so I can't check.
For all of you who haven't heard yet, SUS3 and POSIX:2001 are now the
same thing and are freely available online on
Keith Packard wrote on 2002-07-06 10:34 UTC:
I got the European coverage information from
http://www.evertype.com/alphabets/
I don't know why all of the latin languages include @ and ', it's
probably just a mistake; they're easily removed.
Actually, thanks to URLs and email
As we are talking about en_US.UTF-8:
General warning: Please do not use the locale name en_US.UTF-8 anywhere
outside North America. Some older Solaris documentation suggested that
this is the only UTF-8 locale you'll ever need, as locales don't change
much sensible beyond the encoding anyway.
Nadim Shaikli wrote on 2002-02-28 23:48 UTC:
What are your comments on mlterm, patch27, biditext (have you used 'em) ?
Can you send me a compact exact specification of the exact bidi
semantics of these implementations? I haven't seen one yet and I don't
have the time to reverse engineer these.
Mark Leisher wrote on 2002-02-13 00:29 UTC:
I respect Markus too much to think this was anything more than a subconscious
plea for simplicity and symmetry, born of irritation with messy reality. Sort
of absentmindedly muttering out loud when someone is nearby.
What I primarily wanted to
Tzafrir Cohen wrote on 2002-02-12 18:46 UTC:
I think it might be a good idea to really keep bidi completely out of
xterm. If people want to play around with bidi terminal semantics, then
I would suggest that they build a filter that can be plugged in between
the LTR terminal and the
Moe Elzubeir wrote on 2002-01-22 17:08 UTC:
The subsetting system is in place already, so now what?
I still have not fully understood, what exactly is in place
and how well does it work in X11R6. For example
xfd -fn '-Misc-Fixed-Medium-R-SemiCondensed--13-*-75-75-C-*-ISO10646-1[0_0xff]'
Alexander Gelfenbain wrote on 2002-01-17 19:59 UTC:
I can confirm that the license ST will be released with is BSD+ which is
standard BSD with the following clause:
* You acknowledge that this software is not designed, licensed or indended
* for use in the design, construction, operation
Tomohiro KUBOTA wrote on 2002-01-10 10:58 UTC:
At Wed, 09 Jan 2002 18:07:03 +,
Markus Kuhn wrote:
.. unless an explicit subrange specification is present, such that
people have to write
*-iso10646-1[0_0x]
if they are sure that they want to have the full font
Moe Elzubeir wrote on 2002-01-08 00:12 UTC:
I have been looking into the U+3000 limit and how the 10x20 font is
being truncated to save memory space.
This 'truncation' of the 10x20 for 'optimization' is seriously hampering
our efforts to bring Arabic support on platforms where XFree86 runs.
Juliusz Chroboczek wrote on 2002-01-08 14:16 UTC:
Font subsetting is fully implemented in the BDF, PCF, Type 1, Speedo
and freetype backends. I haven't checked the SNF or X-TT backends.
Try
xfd -fn '-misc-fixed-medium-r-semicondensed--13-*-75-75-c-*-iso8859-1[65_90]'
Very nice, I
Keith Packard wrote on 2001-12-28 19:54 UTC:
I should have monochrome text running in a week or so to give people a
chance to experiment with performance over links of various sorts. When
I've done this in other environments, I've found performance to be
acceptable down to 2B ISDN speeds;
Roozbeh Pournader wrote on 2001-12-27 22:58 UTC:
I remember the discussion here about the font naming and structure issues
for non-BMP characters. But I cannot remember the outcome (and if there
were oppositions). Since we are thinking about doing some work on Pango to
support non-BMP
On Wed, 24 Oct 2001, Jungshik Shin wrote:
JC If you desire a different behaviour, you should either try to get your
JC applications to work with `-p-' fonts, or push for a ``biwidth'' `-b-'
JC spacing type to be included in a future versions of the XLFD.
If the answer to my two questions
On Wed, 12 Sep 2001, Steve Swales wrote:
XIM is working very well with the CSI (code-set independent) version of xterm
provided by Li18nux.org (patches from IBM). It works equally well in our UTF-8
locales and our non-UTF-8 locales. Because of this (CSI), Sun will be adopting
this version
41 matches
Mail list logo
