Re: [I18n]xterm to invoke luit
> > Does luit support the encodings that do not compatible with iso-2022? > > For example GB18030? > > It supports a few non-ISO-2022-compliant encodings such as Big5. > It doesn't support GB18030 so far, though Juliusz is willing to > support it. See his message at If I do # LANG=zh_TW.Big5 xterm -u8 -e luit Warning: couldn't find charset data for locale zh_TW.Big5; using ISO 8859-1. # xterm -u8 -e luit -g2 'Big 5' # LANG=zh_TW.Big5 It still cannot display any big5 encoded char. Anything I did wrong? Leon > > http://mail.nl.linux.org/linux-utf8/2001-11/msg00093.html > > for detail. -- Leon Ho, Red Hat Inc., Asia-Pacific Operations <[EMAIL PROTECTED]> Files:http://people.redhat.com/llch Legal:http://apac.redhat.com/disclaimer ___ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
Re: [I18n]xterm to invoke luit
Hi, At Thu, 31 Jan 2002 13:58:11 +0800, James Su wrote: > Does luit support the encodings that do not compatible with iso-2022? > For example GB18030? It supports a few non-ISO-2022-compliant encodings such as Big5. It doesn't support GB18030 so far, though Juliusz is willing to support it. See his message at http://mail.nl.linux.org/linux-utf8/2001-11/msg00093.html for detail. --- Tomohiro KUBOTA <[EMAIL PROTECTED]> http://www.debian.or.jp/~kubota/ "Introduction to I18N" http://www.debian.org/doc/manuals/intro-i18n/ ___ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
Re: [I18n]xterm to invoke luit
Hello, Does luit support the encodings that do not compatible with iso-2022? For example GB18030? Regards James Su Tomohiro KUBOTA wrote: >Hi, > >XFree86 4.2 has been released. Thus, I'd like to start an improvement >of xterm to invoke luit, so that xterm will obey the current LC_CTYPE >locale not only when it is one of UTF-8 locales but also when it is >one of various major locales (which luit supports). > >My idea is: > - adding "-lc" command line option and "locale" resource (boolean) > to specify whether luit will be invoked or not. > - luit will be invoked only when locale is other than "C", "POSIX", > or UTF-8. > - when luit will be invoked, xterm will be need to be UTF-8 mode. > This will be done automatically. > - "xterm -e ..." has to work well even with luit. > - A new sample resource file "XTerm-locale.ad" will be supplied. > - manual page will need explanation of this new feature. > >If nobody is working on this so far, I'd like to develop this and >to send a patch to XFree86 finally. > >Items which need further discussion: > - emulate doublewidth de-facto standard for east Asian encodings > (using http://www.cl.cam.ac.uk/~mgk25/ucs/scw-proposal.html ?) > - luit to support more encodings > (http://mail.nl.linux.org/linux-utf8/2001-11/msg00093.html) > - whether xterm or luit will support BiDi or not. Usage of fribidi > may have license problem (like Robert Brady's patch). > >However, my work above will be able to be started without waiting >for conclusions of these discussions. > >Any comments? > >--- >Tomohiro KUBOTA <[EMAIL PROTECTED]> >http://www.debian.or.jp/~kubota/ >"Introduction to I18N" http://www.debian.org/doc/manuals/intro-i18n/ >___ >I18n mailing list >[EMAIL PROTECTED] >http://XFree86.Org/mailman/listinfo/i18n > > ___ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
[I18n]xterm to invoke luit
Hi, XFree86 4.2 has been released. Thus, I'd like to start an improvement of xterm to invoke luit, so that xterm will obey the current LC_CTYPE locale not only when it is one of UTF-8 locales but also when it is one of various major locales (which luit supports). My idea is: - adding "-lc" command line option and "locale" resource (boolean) to specify whether luit will be invoked or not. - luit will be invoked only when locale is other than "C", "POSIX", or UTF-8. - when luit will be invoked, xterm will be need to be UTF-8 mode. This will be done automatically. - "xterm -e ..." has to work well even with luit. - A new sample resource file "XTerm-locale.ad" will be supplied. - manual page will need explanation of this new feature. If nobody is working on this so far, I'd like to develop this and to send a patch to XFree86 finally. Items which need further discussion: - emulate doublewidth de-facto standard for east Asian encodings (using http://www.cl.cam.ac.uk/~mgk25/ucs/scw-proposal.html ?) - luit to support more encodings (http://mail.nl.linux.org/linux-utf8/2001-11/msg00093.html) - whether xterm or luit will support BiDi or not. Usage of fribidi may have license problem (like Robert Brady's patch). However, my work above will be able to be started without waiting for conclusions of these discussions. Any comments? --- Tomohiro KUBOTA <[EMAIL PROTECTED]> http://www.debian.or.jp/~kubota/ "Introduction to I18N" http://www.debian.org/doc/manuals/intro-i18n/ ___ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
[I18n]Cedilla: a manic text printer
A first beta of Cedilla, the manic text printer, is available from http://www.pps.jussieu.fr/~jch/software/cedilla/ Regards, Juliusz -- CEDILLA ¸ A best-effort text printer Juliusz Chroboczek Cedilla is a simple text printer that uses Unicode internally. Using Unicode means that the set of characters that can appear in the input is very large, and the user may very well have no font available that contains glyphs for the characters that he wants to print. Cedilla attempts to at least partially solve this problem using a number of techniques: 1. Cedilla can use an arbitrary number of downloadable fonts; for any given print job, only the necessary fonts will be downloaded. 2. Cedilla will use its own built-in font. 3. Cedilla will retouch existing glyphs in order to e.g. remove dots or add bars. 4. Cedilla will attempt to build composite glyphs (e.g. for accented characters) on the fly. 5. Cedilla will use fallbacks for characters that are not supported by the available fonts. SOURCES OF GLYPHS Cedilla will attempt to use glyphs from all of the following sources, in decreasing order of preference: 1. Glyphs present in an available font. This is the common case, and covers all simple characters but also, depending on the used font, a number of composites. Example: Être ou ne pas être ? 2. Built-in glyphs. Cedilla has a built-in font which can be (partially) downloaded if necessary. Example: €. 3. Retouched glyphs When no suitable glyph is available, Cedilla will sometimes attempt to retouch an available glyph. The main application is to produce dotless glyphs for further composition; another use is to provide barred glyphs. Example: (Slovenian sentence containing đ.) Example: Tiuj ĉi arĥaismoj neniam estos elĵetitaj. 3. Glyphs composed based on data accompanying the font. The Adobe Font Metrics (AFM) format can include positioning information for composites, and Cedilla will be glad to use such data. However, as few fonts come with extra information in this form, this technique is seldom useful. 4. Glyphs composed out of components present in a single font. If a glyph is missing from a font, but all the components needed to construct it are present, Cedilla will build a composite glyph out of those. While the positioning of the diacritical marks is approximate, the algorithm used appears to be satisfactory with many standard fonts. Example: Czy pamiętasz jak ze mną tańczyłaś Walca ? When building such composites, Cedilla will, whenever necessary, replace dotted letters with their dotless variants or retouch the base glyphs to remove the dot (see Section 2 above). Of course, Cedilla is not limited to using glyphs that are present in Unicode in precomposed form. For example, the second letter of the third word in the sentence below is a Latin small e followed with ‘Combining Vertical Line Below.’ Example: Mo lè je̩ dígí, kò ní pa mí lára. 4. Glyphs composed out of components taken from different fonts. As this sometimes leads to esthetically unpleasant results, Cedilla tries to avoid this technique. It can be useful in some cases, however, and will in particular enable printing almost legible Greek when no decent Greek font is available: Example: Οὐχὶ ταὐτὰ παρίσταταί μοι γιγνώσκειν, ὦ ἄνδρες ᾿Αθηναῖοι, ὅταν τ᾿ εἰς τὰ πράγματα ἀποβλέψω καὶ ὅταν πρὸς τοὺς λόγους οὓς ἀκούω· Note how the diacritical marks were taken from the primary font, while all the other Greek glyphs came from the Symbol font. (Actually, Polytonic Greek is difficult, and Cedilla needs some more work before it can present it satisfactorily. Given suitable fonts — not Symbol! —, Monotonic Greek appears okay, at least to my unexercised eyes.) 5. Fallbacks. In cases when no glyph is directly available for a character, Cedilla will fall back on ever less satisfactory alternatives. For example, a closing double quotation mark will first be replaced with a sequence of two closing single quotation marks which will, in turn, be replaced by a sequence of two apostrophes. The fallbacks mechanism is a rather complex beast (it currently consists of four distinct phases), and interacts in wonderful and mysterious ways with the glyph generation mechanisms, notably composite glyph generation. Its exact mechanics are still in a state of flux, and will be described when they have stabilised. INSTALLING CEDILLA Please see the file ‘INSTALL’ for information on installing Cedilla. INVOKING CEDILLA Please see the ‘cedilla(1)’ manual page for information on invoking cedilla. CONFIGURING CEDILLA Cedilla is configured by inserting fontset definitions in a file named ‘cedilla-config.lisp’ which, by default, lives in ‘/etc/’. A fontset definition is an invocation of
