openSUSE M17n September 2005

m17n@lists.opensuse.org

5 participants
12 discussions

No compose characters possible with asian language setting
by akimbo337＠gmx.de 16 Nov '09

16 Nov '09

Hello! I'm currently using SuSE 9.0 pro for both german and japanese input. This works fine so far, by setting the variables LC_CTYPE to ja_JP.UTF-8 and LANG to de_DE.UTF-8, but nevertheless I experienced a problem: With the LC_CTYPE set to japanese and an input method running (currently kinput2), I cannot type european language compose characters any more - at least the ones I used to produce with two sequent keystrokes ( ´ and e for é for example). The rest of my (german) keyboard layout works all fine, and with LC_CTYPE set to german, é's, à's, ô's, etc pose no problem, but then, of course, I cannot input japanese... This problem seems also to be existent for other language settings that use an input method, I tried it out with a friend who uses chinese input (also on SuSE 9.0 pro). We (my friend and I) are currently writing an article about asian language input with StarOffice/OOo, so we would really appreciate any help or hint concerning this problem. Thanks. Marcel Boeing

5 6

ghostscript and LyX-CJK
by hisha 19 Oct '05

19 Oct '05

Dear list, I just installed SUSE9.3, japanese version, in Unicode. Basically everything works, except two snags: 1) lyx-cjk-1.3.5-3 does not allow for kanji input in the main window. I tried this after starting kinput2 -canna& LANG=ja_JP LC_XMODIFIERS="@im=kinput2" lyx-cjk I can see japanese text, e.g. the splash.lyx file. I can input Japanese if I open the "find" dialog, or in the lower bar, the minibuffer, and even copy and paste the result into the main window, but NOT enter Japanese directly. This worked still fine with SUSE 9.1. 2) Next, ghostview. I took an example file, like http://www.suse.de/~mfabian/suse-cjk/vertical-orizontal-test.ps I verified that I can open this in my old SUSE8.2 and see all characters correctly. Next, I open it with gs as normal user in 9.3, from bash. The result are Mojibake and the messages: --- gs vertical-horizontal-test.ps ESP Ghostscript 8.15 (2004-09-22) Copyright (C) 2004 artofcode LLC, Benicia, CA. All rights reserved. This software comes with NO WARRANTY: see the file COPYING for details. Scanning /usr/X11R6/lib/X11/fonts/ for fonts... 12 files, 12 scanned, 0 new fonts. Scanning /usr/share/fonts/ for fonts... 2 files, 2 scanned, 0 new fonts. Can't find (or can't open) font file /home/hisha/Resource/Font/Ryumin-Light-UniJIS-UTF8-V. Can't find (or can't open) font file Ryumin-Light-UniJIS-UTF8-V. Querying operating system for font files... Didn't find this font on the system! Substituting font Courier for Ryumin-Light-UniJIS-UTF8-V. Loading NimbusMonL-Regu font from /usr/share/ghostscript/fonts/n022003l.pfb... 2395532 1032646 1474788 180942 1 done. Can't find (or can't open) font file /home/hisha/Resource/Font/Ryumin-Light-UniJIS-UTF8-H. Can't find (or can't open) font file Ryumin-Light-UniJIS-UTF8-H. Didn't find this font on the system! Substituting font Courier for Ryumin-Light-UniJIS-UTF8-H. >>showpage, press <return> to continue<< --- Then I switched to root (su -) and there I CAN open the file, without a hitch. The messages are in this case --- ESP Ghostscript 8.15 (2004-09-22) Copyright (C) 2004 artofcode LLC, Benicia, CA. All rights reserved. This software comes with NO WARRANTY: see the file COPYING for details. Scanning /usr/X11R6/lib/X11/fonts/ for fonts... 12 files, 12 scanned, 0 new fonts. Scanning /usr/share/fonts/ for fonts... 2 files, 2 scanned, 0 new fonts. Loading a TT font from /usr/X11R6/lib/X11/fonts/truetype/ipam.ttf to emulate a CID font Ryumin-Light ... Done. >>showpage, press <return> to continue<< --- These two things happend just afer I installed the system, so I did not change the standard configuration. Now, because I did not find any hint in the suse-cjk guide, does anybody have an idea of what might be going wrong? Hisha __________________________________ Save the earth http://pr.mail.yahoo.co.jp/ondanka/

2 10

Hebrew Type1 font problem
by hermanmeester 29 Sep '05

29 Sep '05

Hello everyone, I was wondering if there might be some font experts around. For Hebrew (working in Suse Linux 9.1), I downloaded a couple of free to use fonts via http://culmus.sourceforge.net/ That's all legal and permitted etc, and it worked for a few weeks, but suddenly the fonts didn't come out anymore in OpenOffice. I'm not sure if this is a pure "m17n" question but please don't throw me out yet ;-) I installed the fonts (which are PostScript Type1 fonts) in the /usr/X11R6/lib/X11/fonts/Type1 directory. First I just put the file, which was a tar.gz file, there as /usr/X11R6/lib/X11/fonts/Type1/culmus-0.101.tar.gz This worked for a while. So I guess when importing the fonts, those files were automatically "unzipped"? Later I installed a few Arabic Truetype fonts in the same way (except in /usr/X11R6/lib/X11/fonts/truetype of ocurse, but that didn't work. Apparently these were not unzipped ("de-compressed") automatically? So I took the compressed files out, by saving them somewhere else, and installed them all manually. Now that (still) works. The Arabic fonts all look perfect (but they're truetype). I configured all the fonts as active, but I can't find anywhere in any OpenOffice FAQ or such, what I did wrong. Can free fonts just "expire"? Even if they're designed for free use? Then I also have some directory called /usr/share/fonts/he/Type1 Here, "/he/" must stand for Hebrew. There, those fonts are also stored, I guess uncompressed. I didn't make that directory, I don't know who did ;-) Does that have anything to do with it? (Hebrew is the main Complex-Text-Layout (CTL) enabled language for OOo on my system.) I didn't want to bother you, but I thought the problem is interesting, anyway I'm getting to understand less of how fonts work everyday. Thanks and regards, Herman

2 3

RE: [m17n] AdobeReader crashes on SUSE 10.0 RC1 i386
by James Lin 20 Sep '05

20 Sep '05

Ah.. I see Ok, thank you so much for the info. -James Lin I18N Software Engineer Symantec Corporation http://www.symantec.com ------------------------- Office: 1-650-527-3429 Email: james_lin(a)symantec.com ------------------------- -----Original Message----- From: Mike FABIAN [mailto:mfabian@suse.de] Sent: Tuesday, September 20, 2005 9:36 AM To: James Lin Cc: m17n(a)suse.com Subject: Re: [m17n] AdobeReader crashes on SUSE 10.0 RC1 i386 "James Lin" <james_lin(a)symantec.com> さんは書きました: > Hi Mike > > I am sorry, I meant how to make the following bug to public: > https://bugzilla.novell.com/show_bug.cgi?id=117514 > > Is there an option? That's not so easy because this is a SLES9 bug. SuSE Linux 10.0 bugs are generally public. That #85416 was not public was an accident in my opinion, therefore I changed it. But SLES9 bugs are currently only open for SLES9 customers and partners. And I cannot change this. > -James Lin > I18N Software Engineer > Symantec Corporation > http://www.symantec.com > ----------------------------------------------- > Office: 1-650-527-3429 > Email: james_lin(a)symantec.com > ----------------------------------------------- > > > -----Original Message----- > From: Mike FABIAN [mailto:mfabian@suse.de] > Sent: Tuesday, September 20, 2005 9:14 AM > To: James Lin > Cc: m17n(a)suse.com > Subject: Re: [m17n] AdobeReader crashes on SUSE 10.0 RC1 i386 > > "James Lin" <james_lin(a)symantec.com> ªµªóªÏßöªªÞª·ª¿: > >> Hi >> How do you make the bug to public use? >> >> I couldn't find an option. > > This bug is already public. You should be able to access it now. > >> -----Original Message----- >> From: Satoru Matsumoto [mailto:helios_reds@gmx.net] >> Sent: Monday, September 19, 2005 6:41 AM >> To: m17n(a)suse.com >> Subject: Re: [m17n] AdobeReader crashes on SUSE 10.0 RC1 i386 >> >> Konnichiwa again, Mike! >> >> Mike FABIAN wrote: >>> Satoru Matsumoto <helios_reds(a)gmx.net> ªµªóªÏ*ÖþÛê¢¯: >> >>>> Sigh... I'm not a registered beta tester, so I can't access to the >>>> bug report. (Access Denied: You are not authorized to access bug >>>> #85416.) >>> >>> Please try again, I've just fixed this (I could see no reason why >>> the visibility of this bug needs to be limited to the registered >>> beta testers, therefore I made this bug public). >> >> Hmm, I can access to the Bug #85416 now. I wonder what happened... >> >>>> How can I get the SuSE acroread package for openSUSE 10.0 OSS? >>> >>> I'm not sure yet. openSUSE 10.0 OSS will contain only open source >>> software, i.e. acroread cannot be in openSUSE 10.0 OSS because it is >>> not open source. But I heard that some non-open-source packages will >>> also be made available as addons when openSUSE 10.0 will be released. >>> Probably acroread will be included in these addon packages. >> >> OK. I will wait. >> >> -- >> ¡à¡Ü¡à _/_/_/ To be Happy! _/_/_/ >> ¡à¡à¡Ü _/_/ Satoru Matsumoto _/_/ >> ¡Ü¡Ü¡Ü _/ helios_reds(a)gmx.net _/ >> >> -- >> To unsubscribe, e-mail: m17n-unsubscribe(a)suse.com For additional >> commands, e-mail: m17n-help(a)suse.com >> >> >> -- >> To unsubscribe, e-mail: m17n-unsubscribe(a)suse.com For additional >> commands, e-mail: m17n-help(a)suse.com >> > > -- > Mike FABIAN <mfabian(a)suse.de> http://www.suse.de/~mfabian > â²ØùÜôðëªÏª¤ª¤ÞÂÞÀªÎîØªÀ¡£ > > > -- > To unsubscribe, e-mail: m17n-unsubscribe(a)suse.com For additional > commands, e-mail: m17n-help(a)suse.com > > > > -- > To unsubscribe, e-mail: m17n-unsubscribe(a)suse.com For additional > commands, e-mail: m17n-help(a)suse.com > -- Mike FABIAN <mfabian(a)suse.de> http://www.suse.de/~mfabian 睡眠不足はいい仕事の敵だ。 -- To unsubscribe, e-mail: m17n-unsubscribe(a)suse.com For additional commands, e-mail: m17n-help(a)suse.com

1 0

RE: [m17n] AdobeReader crashes on SUSE 10.0 RC1 i386
by James Lin 20 Sep '05

20 Sep '05

Hi Mike I am sorry, I meant how to make the following bug to public: https://bugzilla.novell.com/show_bug.cgi?id=117514 Is there an option? Thanks -James Lin I18N Software Engineer Symantec Corporation http://www.symantec.com ----------------------------------------------- Office: 1-650-527-3429 Email: james_lin(a)symantec.com ----------------------------------------------- -----Original Message----- From: Mike FABIAN [mailto:mfabian@suse.de] Sent: Tuesday, September 20, 2005 9:14 AM To: James Lin Cc: m17n(a)suse.com Subject: Re: [m17n] AdobeReader crashes on SUSE 10.0 RC1 i386 "James Lin" <james_lin(a)symantec.com> さんは書きました: > Hi > How do you make the bug to public use? > > I couldn't find an option. This bug is already public. You should be able to access it now. > -----Original Message----- > From: Satoru Matsumoto [mailto:helios_reds@gmx.net] > Sent: Monday, September 19, 2005 6:41 AM > To: m17n(a)suse.com > Subject: Re: [m17n] AdobeReader crashes on SUSE 10.0 RC1 i386 > > Konnichiwa again, Mike! > > Mike FABIAN wrote: >> Satoru Matsumoto <helios_reds(a)gmx.net> さんは*蓼筏¿: > >>> Sigh... I'm not a registered beta tester, so I can't access to the >>> bug report. (Access Denied: You are not authorized to access bug >>> #85416.) >> >> Please try again, I've just fixed this (I could see no reason why the >> visibility of this bug needs to be limited to the registered beta >> testers, therefore I made this bug public). > > Hmm, I can access to the Bug #85416 now. I wonder what happened... > >>> How can I get the SuSE acroread package for openSUSE 10.0 OSS? >> >> I'm not sure yet. openSUSE 10.0 OSS will contain only open source >> software, i.e. acroread cannot be in openSUSE 10.0 OSS because it is >> not open source. But I heard that some non-open-source packages will >> also be made available as addons when openSUSE 10.0 will be released. >> Probably acroread will be included in these addon packages. > > OK. I will wait. > > -- > □●□ _/_/_/ To be Happy! _/_/_/ > □□● _/_/ Satoru Matsumoto _/_/ > ●●● _/ helios_reds(a)gmx.net _/ > > -- > To unsubscribe, e-mail: m17n-unsubscribe(a)suse.com For additional > commands, e-mail: m17n-help(a)suse.com > > > -- > To unsubscribe, e-mail: m17n-unsubscribe(a)suse.com For additional > commands, e-mail: m17n-help(a)suse.com > -- Mike FABIAN <mfabian(a)suse.de> http://www.suse.de/~mfabian 睡眠不足はいい仕事の敵だ。 -- To unsubscribe, e-mail: m17n-unsubscribe(a)suse.com For additional commands, e-mail: m17n-help(a)suse.com

2 1

RE: [m17n] AdobeReader crashes on SUSE 10.0 RC1 i386
by James Lin 20 Sep '05

20 Sep '05

Hi How do you make the bug to public use? I couldn't find an option. thanks -----Original Message----- From: Satoru Matsumoto [mailto:helios_reds@gmx.net] Sent: Monday, September 19, 2005 6:41 AM To: m17n(a)suse.com Subject: Re: [m17n] AdobeReader crashes on SUSE 10.0 RC1 i386 Konnichiwa again, Mike! Mike FABIAN wrote: > Satoru Matsumoto <helios_reds(a)gmx.net> ��ϕ��ޤ��: >> Sigh... I'm not a registered beta tester, so I can't access to the >> bug report. (Access Denied: You are not authorized to access bug >> #85416.) > > Please try again, I've just fixed this (I could see no reason why the > visibility of this bug needs to be limited to the registered beta > testers, therefore I made this bug public). Hmm, I can access to the Bug #85416 now. I wonder what happened... >> How can I get the SuSE acroread package for openSUSE 10.0 OSS? > > I'm not sure yet. openSUSE 10.0 OSS will contain only open source > software, i.e. acroread cannot be in openSUSE 10.0 OSS because it is > not open source. But I heard that some non-open-source packages will > also be made available as addons when openSUSE 10.0 will be released. > Probably acroread will be included in these addon packages. OK. I will wait. -- �� _/_/_/ To be Happy! _/_/_/ �� _/_/ Satoru Matsumoto _/_/ �� _/ helios_reds(a)gmx.net _/ -- To unsubscribe, e-mail: m17n-unsubscribe(a)suse.com For additional commands, e-mail: m17n-help(a)suse.com

2 1

playing windows games on suse 9.3
by Joshua Raphael Fuentes 20 Sep '05

20 Sep '05

Ey.. I'm using suse 9.3 professional and it's a really damn good software. I just have this bit of a problem. I've been trying to run Warcraft 3 using wine. I'm just using the default wine included on the package, and have not updated yet. Anyway, my problem is that when I try to run it, it asks for the cd, when in fact my cd is just in my drive. If I try to run the installation that I had on a windows partition, it still asks thesame thing . So, how do I solve this? I've read from some sites that they are sucessfull in doing that one, but how. I've already tried winex and crossover office to run it, but I still got thesame results. Any suggestions on how I could run frozen throne on linux? -- REGISTERED LINUX USER # 393260 there are 10 types of people in the world, those who understand binary and those who don't

1 0

Re: [m17n] AdobeReader crashes on SUSE 10.0 RC1 i386
by James Su 19 Sep '05

19 Sep '05

Hi, The workaround couldn't resolve the issue of firefox plugin, because it's a shared object rather than a startup script. We must force firefox to use xim, otherwise nppdf.so will crash firefox. I think maybe we should push Adobe to release a new acroread binary version which is linked against libstdc++.so.6, rather than the old one. Regards James Su Mike FABIAN wrote: > Satoru Matsumoto <helios_reds(a)gmx.net> さんは書きました: > > >> I got AdobeReader_jpn-7.0.1-1.i386.rpm from Adobe site and installed in >> my 'SUSE 10.0 RC1 i386' box. >> >> But, when I want to start acroread, it crashes by segfault. >> >> Since the strace log is too large to attach, I put it on my server. >> http://61.26.3.112:30080/~helios/error_reports/AdobeReader_strace.txt >> >> Is there anyone who can explain why AdobeReader crashes? >> > > As James Su already explained, the workaround is to use > GTK_IM_MODULE=xim. The SuSE acroread package already contains > that workaround: > > Wed Aug 17 15:03:07 CEST 2005 - mfabian(a)suse.de > > - Bugzilla #85416: add workaround to avoid crash when scim is > installed (add "export GTK_IM_MODULE=xim" to the start skript). > > See the bugzilla report for details on why this workaround is > necessary. > > >> On my 'SUSE 10.0 RC1 x86_64' box, it seems everything fine. >> > > The problem does not occur on x86_64 because acroread is a binary only > package which is available only for i386. I.e. you have to use the > i386 version also on x86_64. That happens to avoid the conflict of > libstdc++ described in bug #85416. > > >> There was no need to install additional Japanese font packages in >> order to display Japanese PDF files. >> > > That is because of my hack /usr/sbin/acroread-cidfont-config (which is > in the ghostscript-cjk package). This script will make the CID-keyed > fonts from the package "CID-keyed-fonts-Wada" available for Acroread. > It wastes a lot of disk space because real copies of these fonts have > to be made into the acroread font directory. But it makes Japanese in > acroread work out of the box. The same works for Korean using > CID-keyed-fonts-Munhwa and for traditional Chinese using > CID-keyed-fonts-MOE. Unfortunately we do not have such fonts for > simplified Chinese. > >

1 0

AdobeReader crashes on SUSE 10.0 RC1 i386
by Satoru Matsumoto 19 Sep '05

19 Sep '05

I got AdobeReader_jpn-7.0.1-1.i386.rpm from Adobe site and installed in my 'SUSE 10.0 RC1 i386' box. But, when I want to start acroread, it crashes by segfault. Since the strace log is too large to attach, I put it on my server. http://61.26.3.112:30080/~helios/error_reports/AdobeReader_strace.txt Is there anyone who can explain why AdobeReader crashes? On my 'SUSE 10.0 RC1 x86_64' box, it seems everything fine. There was no need to install additional Japanese font packages in order to display Japanese PDF files. Thanks. -- □●□ _/_/_/ To be Happy! _/_/_/ □□● _/_/ Satoru Matsumoto _/_/ ●●● _/ helios_reds(a)gmx.net _/

2 4

Re: [m17n] AdobeReader crashes on SUSE 10.0 RC1 i386
by James Su 18 Sep '05

18 Sep '05

Hi, try export GTK_IM_MODULE=xim before starting acroread. Regards James Su Satoru Matsumoto wrote: > I got AdobeReader_jpn-7.0.1-1.i386.rpm from Adobe site and installed in > my 'SUSE 10.0 RC1 i386' box. > > But, when I want to start acroread, it crashes by segfault. > > Since the strace log is too large to attach, I put it on my server. > http://61.26.3.112:30080/~helios/error_reports/AdobeReader_strace.txt > > Is there anyone who can explain why AdobeReader crashes? > > On my 'SUSE 10.0 RC1 x86_64' box, it seems everything fine. There was no > need to install additional Japanese font packages in order to display > Japanese PDF files. > > Thanks. > >

2 1

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE M17n September 2005