September 2002 - openSUSE M17n - openSUSE Mailing Lists

update: mined 2000.3 package available for SuSE Linux 8.0
by Mike Fabian 04 Aug '03

04 Aug '03

An updated package of mined is available for SuSE Linux 8.0: ftp://ftp.suse.com/pub/people/mfabian/8.0-i386/mined-2000.3-0.i386.rpm ftp://ftp.suse.com/pub/people/mfabian/8.0-src/mined-2000.3-0.src.rpm Mined is a text editor, small and easy to use, yet powerful. It is Unicode-capable, using UTF-8 encoding (also converts UTF-16 input). >From the CHANGES file: ============================================================================= Changes from mined 2000.2 -> mined 2000.3 ========================================= Documentation: -------------- The manual page was updated and thoroughly revised. Its primary source was transformed into HTML, roff/man format being generated. The mined web pages were updated and revised. The file "doc/compilation" (with compilation hints) was updated. Features: --------- HOP '/' enters an indented Javadoc comment frame. Interface: ---------- Options can be concatenated on the command line. (mined -uu instead of mined -u -u enables Unicode line separators.) Right-to-left script input support is now enabled by default. The option -b toggles it. Option -G disables (actually toggles) the display of certain control characters as block graphics characters (enabled by default). Option +G enforces use of block graphics for display of menu borders. May be used if the "alternative character set" capability is not configured in your system but your terminal does have the capability. Set output delay (-d0..-d9) to none (-d-) by default in all versions. The help command was unified on Unix and DOS versions. Not completely, however, as calling a sub-programm ("less") through the "system" call doesn't seem to work on DOS (it crashes or blocks terminal input afterwards, even with cygwin). See also next comment. A second help viewing mode is now avaible (HOP HELP, e.g. HOP F1). It displays help information within mined itself, restoring the previous editing state afterwards. This is the default on MSDOS for the reason mentioned before. Bug fixes: ---------- Fixed a screen-related pointer confusion after replacement with multiple lines (embedded newline) which could result in a display bug and page down could be blocked. (Very minor) Just deleting the trailing line-end of a file is also considered a modification (a file only modified this way would previously not have been saved automatically). (Minor) With UTF-8 auto-detection involved, the character count after reading the file could be wrong (ESC ? would have been correct). (Minor) The pop-up menu, when modified with HOP and thus becoming smaller, used to leave the frame of its previous width on the screen. (Embarassing) Although I was proud of "perfect responsiveness to window size changes" I had just forgotten to implement that for the case of a menu being open. On DOS, editing a file with Unix line-ends, the function "append to buffer" used to append the lines with MSDOS line-ends. -- Mike Fabian <mfabian(a)suse.de> http://www.suse.de/~mfabian 睡眠不足はいい仕事の敵だ。

3 10

CJK-LyX 1.2.0 package available for SuSE Linux 8.0
by Mike Fabian 20 Jan '03

20 Jan '03

An updated CJK-LyX package is available for SuSE Linux 8.0: ftp://ftp.suse.com/pub/people/mfabian/8.0-i386/cjk-lyx-1.2.0-0.i386.rpm For some screenshots and SuSE specific notes see http://www.suse.de/~mfabian/suse-cjk/cjk-lyx.html >From the /usr/share/doc/packages/cjk-lyx/NEWS file: What's new in version 1.2.0? ---------------------------- LyX 1.2.0 is the version where many of changes in the 1.1.x series really begin to pay off. It should prove to be a very solid base for further developments. As of this version, we use (yet another) new versioning scheme: next major version will be 1.3.0, and 1.2.x will be just incremental fixes (like the `fix' series used to be for 1.1.5 and 1.1.6). This version sees the introduction of the so-called `new' insets, which can contain arbitrary text. As a consequence, many new features are now possible: - Floats, footnotes and margin notes are now real insets. The positional parameters of figure, table and algorithm floats can be set float-by-float - Most problems with the new table inset of 1.1.6 have been addressed (memory consumption, file bloat, spell-checking, search and replace...). Better longtable header/footer support was implemented. - TeX mode has been superseded by the ERT inset, which is foldable, or can be shown inline - Notes inset can now contain arbitrary LyX constructs; they will not appear in the output. - New minipage inset Note that another consequence of these changes is that older LyX versions will almost certainly fail to read files produced by LyX 1.2.0. Other more traditional insets have been improved too: - New graphics inset with support for hassle-free inclusion of various image formats (GIF, JPEG, PNG and EPS by default) and a new rendering scheme that should fix the bugs we had with the older ghostscript method. - Support for natbib for bibliography citations The math editor has been mostly rewritten. This begun as a general cleanup, but it turns out that many new features happened in this process, among which: - many of the known bugs or annoyances in mathed have been fixed. - possibility to display all standard latex and amsmath symbols (and also the \mathcal, \mathbb, and \mathfrak fonts)as long as the relevant fonts have been made available to the X server - support for many amsmath features Commands: xrightarrow, xleftarrow, substack, underset, dddot over/under arrows (e.g. underleftarrow). Environments: align, alignat, xalignat, xxalignat, multline, gather split, gathered, aligned, cases, subarray, pmatrix, bmatrix, vmatrix, Vmatrix - Preliminary support for xymatrix - Support for horizontal and vertical lines in arrays. - Improvements to the parser - Improvements to math text mode - (Better) support for nested macros - Enable size changes to arrays after creation (add/delete rows/columns) - Support for changing font or displaystyle on a selection - GUI support provided for many more features -- Mike Fabian <mfabian(a)suse.de> http://www.suse.de/~mfabian 睡眠不足はいい仕事の敵だ。

3 4

Missing fonts in lyx-cjk / how to find the package for latex2html
by Shin, Jong-Hwa 27 Sep '02

27 Sep '02

Dear Folk I've got some problems for using lyx-cjk in SuSE8.0. First of all, I don't know how to generate html file in lyx/lyx-cjk. In my previous experience of using old SuSE versions with lyx1.4, it was quite easy to generate html files: latex2html and the embedded function in lyx. But, lyx1.6 and lyx-cjk 1.6 in SuSE8.0 don't seem to have the exporting function. Am I correct? Even, I cannot find the packages, like latex2html, hevea,or tth. Am I wrong? Please, let me know how to generate html files from lyx/lyx-cjk. Thank you in advance. Secondly, when I open a file in lyx-cjk and see it in xdvi, terminal problems show error messages like this: Could not get fontset. -adobe-times-medium-i-normal--14-140-75-75-p-73-iso8859-1, Cannot load fontset KSC5601.1987-0 Using 'fixed'. Could not get fontset. -adobe-times-bold-i-normal--24-240-75-75-p-128-iso8859-1, Cannot load fontset KSC5601.1987-1. Using fixed. I would like to know how to find the additionally fonts in Yast. In fact, I think that I have installed almost all fonts related to Korean. But, I don't know why this happens. Ciao Jong-Hwa

2 2

CJK on SuSE 8.1
by Friedrich Dimmling 26 Sep '02

26 Sep '02

Couriosity overriding the caveat 'Never touch a running system' I have ordered a copy of SuSE 8.1 Pro. Now my question: Can I install the 8.0 packages e.g. for xcin, cjk-latex, the unicode support for LaTeX and Gnu Emacs, Emacs unicode font and the Archic TTFs (for Chinese) on the 8.1 system or shall I wait for new packages to come? I mostly use CJK LaTeX with Gnu Emacs, OpenOffice and KMail with xcin. Friedrich -- Friedrich Dimmling, Berlin, Germany

2 1

RE:Re: [m17n] Ugly english text after chinese TTF fonts installed
by hillmanhk 25 Sep '02

25 Sep '02

Mike, thanks for your help...The layout of KDE and OpenOffice look a lot better. However, for the mozilla, there is a case that if the web site contain both chinese and english fonts and the web page default encoding is chinese big5, the english text are still using chinese fonts. Do you know how to solve it? Regards, Hillman Dai Hay Ming >"hillmanhk" <hillmanhk(a)sinaman.com> writes: > >> In order to use the OpenOffice, I have installed the chinese >> truetype fonts, bkai00mp.ttf and bsmi001p.ttf with the rpm files >> provided by Mike. The chinese fonts display so far is good. However, >> the english text display in KDE interface, mozilla and OpenOffice >> are really terrible. They are small, unclear and even hard to >> distingush between normal and bold type! > >Try to avoid using these Chinese fonts for English texts. > >KDE: > > http://www.suse.de/~mfabian/suse-cjk/kde-font-setup.html > >explains how to select a nice font for English and combine it >with a nice font for other languages like Chinese. > >OpenOffice: > >see > > http://lists.suse.com/archive/m17n/2002-Aug/0015.html > >Mozilla: > > Edit -> Preferences -> Appearance -> Fonts > > and choose different fonts for English and Chinese. > >-- >Mike Fabian <mfabian(a)suse.de> http://www.suse.de/~mfabian >$B?gL2ITB-$O$$$$;E;v$NE($@!#(B > >-- >To unsubscribe, e-mail: m17n-unsubscribe(a)suse.com >For additional commands, e-mail: m17n-help(a)suse.com > >. > Regards, Hillman Dai Hay Ming ================================================================== 至尊偶像鈴聲選舉：http://sms.sina.com.hk/ringtone/

3 3

Japanese Keyboard
by Thomas Piekenbrock 25 Sep '02

25 Sep '02

Hello, I have this wonderful Japanese keyboard with all the hiragana Symbols on it. I would like to use them in Linux. Is it possible to create a keyboard coding for this, simply by letting the Kana keys produce the respective Roman Characters (i.e. the press of "ka" syllable rendering the two Roman letters "k" and "a")? If yes, how can I do this so that it works for KDE 3.0? Best Regards, Thomas Piekenbrock -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net

2 5

Ugly english text after chinese TTF fonts installed
by hillmanhk 24 Sep '02

24 Sep '02

Hi all, In order to use the OpenOffice, I have installed the chinese truetype fonts, bkai00mp.ttf and bsmi001p.ttf with the rpm files provided by Mike. The chinese fonts display so far is good. However, the english text display in KDE interface, mozilla and OpenOffice are really terrible. They are small, unclear and even hard to distingush between normal and bold type! Could you help me to solve this problem? Regards, Hillman Dai Hay Ming Regards, Hillman Dai Hay Ming ================================================================== 至尊偶像鈴聲選舉：http://sms.sina.com.hk/ringtone/

2 1

CLE
by Stefan Friedrich 24 Sep '02

24 Sep '02

Hi everyone, I have just seen some distributions here in Taiwan with Chinese Linux Extensions (CLE). What exactly is this? Is it something that can be achieved with the SuSE 8.0 distro and a chinese setup or does it go much deeper such as recompiling the kernel to suit big5? With everything going unicode will this stuff not become obsolete? PS: I am looking forward to the release of SuSE 8.1 in October with Gnome 2.0! Stefan

2 1

Probelm with TrueType and UTF-8
by Isam Bayazidi 24 Sep '02

24 Sep '02

Hi all I am using SuSE 7.3, KDE 3.0.3, XFree86 4.1.0 .. I use the Arabic language in KDE3 so I wanted to get the TrueType fonts that comes with MS-Windows to use for Arabic .. I refered to a HOWTO that explains how to impoert TTFs to SuSE .. it worked BUT it did not define the fonts for the Encoding UTF-8 ( ISO-10646-1) .. it is essensial to define it for UTF-8 as it is the encoding used in KDE3 and GNOME2 .. for example the font TAHOMA that I use for Arabic is defined for : ( this is from /use/X11/lib/X11/fonts/truetype/fonts.dir ) tahoma.ttf -microsoft-Tahoma-medium-r-normal--0-0-0-0-p-0-ascii-0 tahoma.ttf -microsoft-Tahoma-medium-r-normal--0-0-0-0-p-0-fcd8859-15 tahoma.ttf -microsoft-Tahoma-medium-r-normal--0-0-0-0-p-0-iso8859-15 tahoma.ttf -microsoft-Tahoma-medium-r-normal--0-0-0-0-p-0-iso8859-10 tahoma.ttf -microsoft-Tahoma-medium-r-normal--0-0-0-0-p-0-iso8859-9 tahoma.ttf -microsoft-Tahoma-medium-r-normal--0-0-0-0-p-0-iso8859-8 tahoma.ttf -microsoft-Tahoma-medium-r-normal--0-0-0-0-p-0-iso8859-7 tahoma.ttf -microsoft-Tahoma-medium-r-normal--0-0-0-0-p-0-iso8859-6 tahoma.ttf -microsoft-Tahoma-medium-r-normal--0-0-0-0-p-0-iso8859-5 tahoma.ttf -microsoft-Tahoma-medium-r-normal--0-0-0-0-p-0-iso8859-4 tahoma.ttf -microsoft-Tahoma-medium-r-normal--0-0-0-0-p-0-iso8859-3 tahoma.ttf -microsoft-Tahoma-medium-r-normal--0-0-0-0-p-0-iso8859-2 tahoma.ttf -microsoft-Tahoma-medium-r-normal--0-0-0-0-p-0-iso8859-1 while I want it to be defined for ISO10646-1 as well .. how can I do so ? knowing that in Mandrake the fontdrake tool import the Windows TTFs properly and define it for ISO10646-1 as well .. Thanks for your help .. Yours Isam Bayazidi

2 1

The dead '~' is evil!
by Steven T. Hatton 24 Sep '02

24 Sep '02

I just learned what dead keys really are. The file /usr/X11R6/lib/X11/locale/en_US.UTF-8/Compose defines the key combinations necessary to type 'special'characters using the en_US.UTF-8 locale. 'Why?', you may ask is the dead '~' especially evil? in a word `rm -r ~/.junk`. If you are in the habbit of typing <dead_tilde> <space> and switch to a mapping without dead keys `rm -r ~/.junk' becomes `rm -r ~ /.junk' which has a whole different meaning. In preparing this message I did a `grep "~" /usr/X11R6/lib/X11/locale/en_US.UTF-8/Compose' and found there is also a "<dead_tilde> <dead_tilde> : "~" asciitilde" mapping. This is much better. It could still make working with '~' escapes in ssh rather confusing, but I see that as a far less likely problem. In general, now that I understand what ḋead keý means, I donṫ like them. Thereś got to be a better way! I have many uses for special characters. They range from transscribing the Nibelungenlied into electronic text, to building databases representing, for example, Old Norse words and their inflections, or proto-Germanic and its relationship to its daughter languages. I also would like to be able to express mathematical concepts such as ∃,∄, ⋂, ⋃, ⋀, ∩, ∪, ∬. In a semi-natural way. And then we hit the obvious problem of which of ⋂ and ∩ is the correct symbol for the instance in question. Is ∑ the same as Σ? I used `ucm` to pick these characters out. This is an unusably slow process for any kind of work which involves extensive use of characters not available in the current key mapping. The first '∑' is from 'U+2200' and the second 'Σ' is from U+0300. These appear identical on my SuSE 8.0 box in kmail. I copied these from kmail to and Emacs buffer and found the first of these characters is not rendered, and the second is rendered as expected. Hexlifying the buffer holding `∑ Σ' resulted in the following character codes: e288 9120 cea3. This could be anoying when it comes to human to human comunication. It is potentially devistating when it comes to human to computer communication. For example, imagine a database of words from different languages and data entered by different users who donṫ fully understand the idosynchracies of UTF encoding. To the users, everything may appear correct, but what were intended to be equivalent strings entered by different users may actually be two distinct representations of the same human readable representation. I'm sure much of what I'm saying is not news to people on this list. I do have one proposal for a tool which may help alleviate some of these problems. It would be nice to have a speciall key sequence to switch quickly between key mappings (I believe the KDE actually does support this.), and have a visual representation of the current mapping displayed to the user at will. It might even be helpfull to be able to browse the available mappings with the corresponding visual representations displayed to the user before selecting that particular option. As it stands, I don't even know if I have a 104 or a 105 keyboard. I don't know the difference. Things have gotten better regarding selecting keyboards and such with the KDE. I still find them confusing. A user sould not have to learn the underlying details of xmodemappings and the ~/.kde/share/config/kxkbrc. Any thoughts on this? -- STH

2 7