Ben Wiley Sittler wrote:
It's a font suitcase, and IIRC the font data is actually in
the resource fork. At least under Mac OS X, fontforge seems
to be able to deal with these. If you have the file on a
non-Mac OS machine it may well be corrupt, since non-Mac
filesystems do not preserve the
I have a font for an exotic language (Javanese) that I want to
convert to UTF-8 encoding. Problem is, the font file was made on a
Macintosh using Fontographer, and it has a .suit file extension
that Fontforge doesn't know how to handle.
Anyone knows of a conversion tool under Linux that can
Brice Goglin wrote:
I have forwarded this bug on the upstream bugzilla at the URL
above. Feel free to add any comments there if you think it
could help. I know nothing about Greek accents and I don't have
a Greek polytonic keyboard, so I won't be able to help much :)
At the moment in Sid,
Marcin 'Qrczak' Kowalczyk wrote:
There is still some software I have installed here which
doesn’t work with UTF-8. I switched from ekg to gaim and from
a2ps to paps because of this. UTF-8 support in some quite
popular programs still relies on unofficial patches: mc, pine,
fmt. There is still
Larry Wall wrote:
Here's a handy program to grep out names from the unicode
database. I call it uni. [..]
This is really neat. I didn't know that perl has such extensive
utf-8 support now (including the whole unicode database). I know
perl only from the Llama book (Learning Perl, 1997 edition)
Colin Paul Adams wrote:
[..] I don't know how to type the accented character.[..]
The Compose key is very useful for occasional entry of non-ASCII
characters; see http://en.wikipedia.org/wiki/Compose_key for a
description. E.g. Compose=c becomes €, Composea becomes ä.
Hundreds of such compose
Benjamin C. Wiley Sittler wrote:
I think copying the character is correct behavior. To achieve
line-breaking control without copy-n-paste artifacts, use CSS:
style type=Text/css
.word:after {
content: '\200b';
}
/style
span class=word/foo/spanspan class=word/bar/spanspan
Again, I apologise if this has been asked on this list before.
If I make a web page of which the text includes very long words
(such words in my case often are file pathnames), often very
awkward line-breaks result. They look even worse if the text is
justified (text-align: justify; in .css).
Behdad Esfahbod wrote:
If you use the latest Firefox 1.5 with Pango text rendering
enabled (unset MOZ_DISABLE_PANGO) AND my Firefox+Pango printing
patch from here:
https://bugzilla.mozilla.org/show_bug.cgi?id=357733
You can view and print MathML in Linux.
behdad, hoping that his
Rik van Riel schreef:
Egmont was right. It was only a few minutes of sysadmin time
to apply the patch and figure out a command to regenerate the
archives.
Fantastic, thanks
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
Arne Götje (高盛華) wrote:
[..] yes, it depends totally on the font to define the
*position* of the accents (and weather or not they can be
stacked). But it depends on the rendering engine to *interpret*
the information the font gives about the accents.
BTW: there was no irony in my statement.
This subject sometimes comes up, but not nearly frequently enough
I think.
The web archives of this list at
http://mail.nl.linux.org/linux-utf8/ do not preserve utf-8
characters intact. This is absurd given the subject of this list.
Is there no way of remedying this situation? Could this list be
Arne Götje (高盛華) wrote (in another thread, replying to Rich
Felker):
In this case, *you* need to *define* which combinations you
need and *how* they should be displayed.
and (replying to Andries Brouwer):
But please, if you do so, provide the necessary information
(which combinations are
[copied to linux-utf8@nl.linux.org from a discussion which started
at [EMAIL PROTECTED]
The combining accents problem seems really complicated.
Depending on the font and the rendering engine, combining accents
are sometimes displayed/printed correctly, or sometimes not.
Here are the results of
Behdad Esfahbod schreef:
If you use the latest Firefox 1.5 with Pango text rendering enabled
(unset MOZ_DISABLE_PANGO) AND my Firefox+Pango printing patch from here:
https://bugzilla.mozilla.org/show_bug.cgi?id=357733
You can view and print MathML in Linux.
behdad, hoping that his
Did any member of this list ever manage to correctly *print* pages
containing mathml, in Linux, with any Mozilla variant?
Regards, Jan
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
Joe Schaffner wrote:
After lengthy consideration, I have come to the conclusion xkb
[..] only maps keyboard events to keysyms, which are not
characters
Many of them really are just characters.
I have these two keymaps i.e. groups on my system:
/etc/X11/xkb/symbols/el -- The one I'm using
Joe Schaffner wrote:
Hello Thomas,
It looks like we're all looking for non-standard ways to
capture polytonic Greek in Linux. This must mean no keymap
exists. Given one hundred years I'll figure out xkb and write
one.
xkb is not so difficult to figure out. At the moment you can
already
Πιστιόλης Κωνσταντίνος wrote:
In that page you propose:
...A font which includes all accent combinations for Classical Greek is,
for instance, FreeSerif. The efont bitmap fonts (for xterm) also have
them...
Which may or may not be valid depending which symbol your keymap produces
for
Imitating the difficult-to-learn Windows system for 'multiple
diacriticals' should IMHO be offered as an option, but not as the only
option. The ease with which diacriticals can be combined by means of
xkb/Compose could be a 'Linux selling point' in the academic world.
BTW I am now terribly
Joe Schaffner wrote:
[..]
With this font, I can capture the entire entry, no problems, pointing
fingers, arrows, boxes, tiny-elvises, polygreek etymology... There is
virtually nothing I cannot do with the Unicode character set alone.
And in another message:
Simos Xenitellis wrote:
You can have a look at this document,
http://planet.hellug.gr/misc/polytonic/ Although it is in Greek, it
should be feasible to discern the combinations proposed. For example,
Νεκρό πλήκτρο is Dead key in the list. If there are queries, feel
free to refer to me.
Simos Xenitellis wrote:
O/H Jan Willem Stumpel έγραψε:
This also means that when you run scim, the ogonek and horn
do not work as breathing signs even if the locale is
el_GR.UTF-8, because scim's internal copy of the Compose file
is only the common one.
In addition, when you try to type
Alexandros Diamantidis wrote:
[sorry for taking a few days to reply...]
* Jan Willem Stumpel [2006-01-18 14:41]:
This does not work in my case. Also interchanging the entries (US first,
then GR) did not work. I mean you can get the accents, but not the
breathing signs. Strangely enough, even
Alexandros Diamantidis wrote:
[sorry for taking a few days to reply...]
* Jan Willem Stumpel [2006-01-18 14:41]:
This does not work in my case. Also interchanging the entries (US
first, then GR) did not work. I mean you can get the accents, but
not the breathing signs. Strangely enough, even
Alexandros Diamantidis wrote:
* Jan Willem Stumpel [2006-01-16 21:52]:
All characters, including things like ᾦ, can be made in Greek
mode, even in en_GB.UTF-8 locale, if the dead ogonek and horn in the
symbols/pc/gr file are replaced [..]
Right, that's one way to do it. Another way would
Alexandros Diamantidis wrote:
When I made an initial try at a polytonic Greek keyboard, I couldn't
find a dead_comma_above and a dead_reversed_comma_above, so I just
(ab)used the first two keysyms that weren't otherwise meaningful on a
Greek keyboard. Subsequent updates to the Greek keyboard
Some results for classical Greek: this is with Debian Sid, en_GB.UTF-8
locale, PC104 (US) keyboard. No KDE, no Gnome. Just X with icewm.
Uim and scim do not provide methods for classical Greek. The immodule
im-classicalgreek does not seem to work anymore with the newer versions
(2.4.0) of
Abel Cheung wrote:
On 11/18/05, Behdad Esfahbod [EMAIL PROTECTED] wrote:
Because paps is quite under development right now.
But I still packaged it and uploaded to Mandriva Linux. :-)
Yes, comparing to u2ps (which halted development for some time)
paps is indeed a better solution, though
Abel Cheung wrote:
I have also tried using ooffice -p (2.0); actually it doesn't
work well with cjk characters, with characters overlapping each
other; but at least all the characters do print successfully.
Hmm.. I did not see these overlapping CJK characters. I wonder
when and why this
Thomas Wolff wrote:
With a file name, soffice does TRY to print but also it fails
to print apparently because it depends on a properly configured
Unix printer channel.
Yes, and lpr has to be able to handle PostScript through some
'input filter'.
Can it be told to just produce PostScript
Thomas Wolff wrote:
ooffice -p file
On my system OpenOffice 1.1.3 and 2.0 are installed but there
is no script ooffice anywhere. The program to start is called
soffice but it does not handle a -p option. Which script do you
refer to?
On my (Debian) system it is in /usr/bin. The comment
This may be interesting for list members: Openoffice can be used
as a command-line printer for UTF-8 text files. The command is:
ooffice -p file
The user interface does not come up, so it is reasonably fast. The
print results are very nice.
Almost always Openoffice is clever enough to
William J Poser wrote:
Well, yes, but you just have to consider the study of manual to
be a form of spiritual practice, from which eventually
enlightenment will follow.
A slightly more accessible (less kabbalistic?) introduction to
gettext may be chapter 10 of the Guide to localisation:
Bruno Haible wrote:
Is this a groff version 1.18.1 or newer??
Yes, 1.18.1.1-8 (according to dpkg -l)
In languages like Japanese or Chinese, there are line breaking
opportunities not only at spaces. And there are fewer spaces
than in European languages. I guess that groff is looking for
Bruno Haible wrote:
[..]
Sample use:
$ groff-utf8 -Tutf8 -mandoc find.vi.1 | less
$ groff-utf8 -Thtml -mandoc find.vi.1 find.html; mozilla find.html
On my system in an utf-8 enabled xterm, with either en_GB.UTF-8 or
ja_JP.UTF-8 locale:
[EMAIL PROTECTED]:~$ groff-utf8 -Thtml
Arne Gtje () wrote:
Ok, I think I need to explain this a bit. [..]
Thanks very much for this clear explanation.
But not all fonts reflect those attitudes. Fonts develped in
Mainland China *have to follow the GB1830 standard*, so there
is no other option.
So GB1830 is a standard for the actual
Simos Xenitellis :
1. [..]
Unfortunately I do not know anything about Indic languages and
scripts.
2. You mention that [IIIMF] has zero documentation. The choice of
words is not elegant.
You are quite right. It is rude. I changed it to it is rather
short on user-level documentation, which I
Edward H. Trager wrote:
You should mention the newer Un series of Korean fonts
announced by Jungshik Shin in September, 2003.
Thanks! I'll put that in shortly.
In my Mozilla browser, both of these glyphs appear as the
Chinese style, [..] Maybe you should use PNG graphics here in
addition to your
Would like to get comments criticism especially about the
input part:
http://www.jw-stumpel.nl/stestu.html#T6.3
Regards, Jan
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
xerces8 wrote:
What is the state of UTF-8 on debian ?
That is what I have been trying to find out for a while.
See http://www.jw-stumpel.nl/stestu.html
Any suggestions for improvement are appreciated.
Regards, Jan
--
Linux-UTF8: i18n of Linux on all levels
Archive:
I am trying to make sense of the newer input methods (like uim, anthy,
jmode, scim ...).
Can anybody throw more light on
-- making uim/anthy work with openoffice
-- making uim/anthy work with text-mode programs
I wrote up what I got so far in
http://www.jw-stumpel.nl/input.html
Regards, Jan
Pablo Saratxaga wrote:
On Mon, May 03, 2004 at 07:32:24PM +0200, Jan Willem Stumpel wrote:
1. Most GTK+ programs allow right-clicking in text boxes to change the
input method, but Mozilla, unfortunately, does not.
Try right-clicking on the URL input field.
Of course I tried
Vasilis Vasaitis wrote:
Programs that use the GTK+ library use GTK+'s own composition
mechanism by default, instead of the one supplied by X.
Thanks very much.. but why? Why two different methods?
You can switch that temporarily for a text box, by right clicking on
it and selecting Input
[EMAIL PROTECTED] wrote:
OK - this is well-understood, and not something that can be
improved in user space. We need a kernel change [..]
OK..
But in that case, what is the point --at this moment-- of having
unicode_start? The keyboard does not generate valid UTF-8 (apart
from pure ASCII),
[EMAIL PROTECTED] wrote:
I take it then, you're saying the problem will go away if
I drop console-tools and base-config, and install the (Debian
package) kbd?
Possibly. Either it goes away, or you report a bug and I fix
the bug if I can reproduce it in my non-Debian environment.
Turns out
[EMAIL PROTECTED] wrote:
Aha - Debian most advanced is 1.06 from May 2001.
Not 1.08 from Oct 2002. And certainly not 1.10 from Jan 2004.
Debian is not exactly known for always tracking the latest
developments...
Concerning these error messages: they are warnings only.
If they are warnings only --
[EMAIL PROTECTED] wrote:
The length of keymaps has changed between 2.4 and 2.6.
And the kbd behaviour has changed between kbd-1.08 and kbd-1.09.
So, in order to understand what happens, my first question is:
what kernel? what kbd?
uname -a
Linux spica 2.4.20 #10 Mon Dec 8 20:47:15 CET 2003
[EMAIL PROTECTED] wrote:
Oh - Debian has their own version. If that is broken it isn't
my fault.
Huh? Who *ever* said it was? The question was only 'how to make it
work'. I take it then, you're saying the problem will go away if I
drop console-tools and base-config, and install the (Debian
Edward H. Trager wrote:
This seems to imply that the stock Linux Mozilla packages
available for download are useless for Indic languages ...
Maybe that conclusion goes too far. Could be that it is only a
problem with the letter (u+092c). My guess (but I dont know any
Indic language) is that
Jungshik Shin wrote:
It's impossible to infer the document encoding from 'lang' tag.
Indeed, yes, I presented the URL inserted by jmaiorana to the W3C
HTML validator and it could not make any sense out of it. Still,
when I set Mozilla to 'autodetect Japanese' it correctly found it
to be
[EMAIL PROTECTED] wrote:
If you see html lang=ja then the page should use the font
specified by the Japanese setting by default. [..] Encoding
is fairly irrelevent to this, afaik
http://ken2403king.kir.jp/form.htm
Thats a funny one, indeed. When I opened it in Mozilla it was
displayed as
Edward H. Trager wrote:
I don't know whether the following page will answer your
question or not:
http://eyegene.ophthy.med.umich.edu/unicode/#fonts
Note: This page does not describe the set up of fontconfig and
xft.
It is an excellent page, I found it already some time ago, and
learned a lot
Jungshik Shin wrote:
You have to note that for a good quality rendering, you'd
better get fonts specifically made for a subset of Unicode
repertoire instead of pan-Unicode fonts. Google 'alan wood
unicode fonts' and you'll get Alan Wood's Unicode font site.
For Latin, you definitely need to
Does anyone have a step-by-step description of how to install
Bitstream Cyberbit in Debian Sid? And similarly for (MS) Arialuni?
I am still puzzled on when exactly what font is used for display
and for printing in the various Mozilla versions. Each time I
think 'I got it' it turns out that 'I
55 matches
Mail list logo
