Sorry, this was my first attempt ever to contact a mailing list. I thought
this was the way to do it. I have now subscribed and hope I have done it the
right way.
Ulrich Ruess <utde(a)ms13.hinet.net> さんは書きました:
> Unfortunately acroread cannot handle UTF-8. Is there a way around? Since the
> other pdf-viewers have problems rotating stuff, sometimes acroread is the
> only way out.
Can you describe in more detail please what problem occurs when
trying to use acroread in UTF-8?
>>>>>>To get Chinese working I set RC_LANG="en_US.UTF-8" and
RC_LC_TYPE="zh_TW.UTF-8" in /etc/sysconfig/language. I do not have anything
like ./xcin or similar. All the other things like fonts, input-servers etc. I
had known before and installed. What I did not know was how to start xcin.
After this, when starting acroread from the panel, the icon flashes somewhere
on the screen for some time and then stops. To find out some more I tried to
start acroread in a console. Result as below:
uli@p4:~> acroread
Warning: charset "UTF-8" not supported, using "ISO8859-1".
Aborted
When I comment RC_LC_CTYPE="zh_TW.UTF-8" out, acroread works again, but-of
course- no more xcin.
I then "googled" and found that it is a known problem with acroread not to
accept UTF-8. Unfortunately I could find no solution.
I also did the on-line update. This did not change anything>>>>>>>>
I am running in ja_JP.UTF-8 locale always and didn't notice any
problems. There are many locales where Acroread itself has problems
and doesn't work correctly. but the script used to start Acroread uses
LANG=en_US and LC_NUMERIC=POSIX:
LANG="en_US"
export LANG
LC_NUMERIC=POSIX
export LC_NUMERIC
(see /usr/X11R6/bin/acroread). Therefore one doesn't notice any
problems even when running in UTF-8 locales.
>>>>>>>>>> I do not yet understand scripting, but I checked the script and the
above mentioned lines are there.
Maybe you are not using the SuSE package for Acroread?
>>>>>>>>>I do not yet understand the process of adding software to a Linux
system well enough to even consider using something that is not from the
official distribution.
If you are not using the SuSE package, your start script probably
doesn't set LANG and LC_NUMERIC.
By the way, it may be better to use the m17n mailing list
for such questions:
http://www.suse.de/~mfabian/mailing-list.html
--
Mike Fabian <mfabian(a)suse.de> http://www.suse.de/~mfabian
睡眠不足はいい仕事の敵だ。
我 不知道 <yangrongwei(a)hotmail.com> さんは書きました:
> I am Yang_RongWei, a China user. I want to know the GB18030 standard
> supporting status of SuSE Linux. I found this doc in your company's
> site
>
> http://lists.suse.com/archive/m17n/2001-Nov/0013.html
>
> but it cannot answer my question. I found your mail address in that
> doc. So I write this mail to you. Could you help me answer these
> questions?
>
> 1. Does "SuSE Linux 7.3" support GB18030 ?
No.
> 2. Did SuSE Linux get GB18030 certification from China government ?
SuSE didn't apply for GB18030 certification yet.
> 3. If it got, which is the first version number of SuSE ?
> 4. Which is the first version number when SuSe supports GB18030 ?
UnitedLinux 1.0 and SLES8 (which is based on UnitedLinux 1.0)
support GB18030 but SuSE has not yet tried to get a certification.
SuSE Linux 8.2 didn't support GB18030 anymore because XFree86
was updated to version 4.3.0 and the GB18030 patches needed for
XFree86 were not yet ported to this new XFree86 version.
James Su from TurboLinux has ported the GB18030 patches to XFree86
4.3.0 in the meantime and we have included his patches in the current
beta version of SuSE Linux. I.e. SuSE 9.0, which will be released
sometime in autumn this year, will support GB18030 again.
> 5. Where can I find offical doc about SuSE's GB18030 supporting status?
I don't know any official document about that.
--
Mike Fabian <mfabian(a)suse.de> http://www.suse.de/~mfabian
睡眠不足はいい仕事の敵だ。
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.rpmftp://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
睡眠不足はいい仕事の敵だ。
