Hi,
I'm having problems with the new ubuntu hoary and groff. Hoary works
with utf-8 by default, and groff isn't working well about thar,
special characters aren't reconized. I was thinking about it's a
problem about ubuntu, but I wanted to be sure if groff is supossed to
support utf-8 input. Jus
> Readin info groff I found how to do utf-8 output, but nothing about
> input :(
This is correct, unfortunately. groff doesn't yet support UTF8 input.
You have to convert your file first to something groff can understand.
Below is a small perl script which does that. Note that it doesn't
`fake
> This is correct, unfortunately. groff doesn't yet support UTF8 input.
Ought! :(
But, it's something impossible to implement, or just it isn't interesting?
I say it because if the different distros take the same way as
ubuntu... It wont be cool for groff
> > This is correct, unfortunately. groff doesn't yet support UTF8
> > input.
>
> But, it's something impossible to implement, or just it isn't
> interesting?
I want to do this since years, but there are always more important
things to do :-( Reason is that I'm involved in more than a single
pro
Dear Werner,
you wrote
Below is a small perl script which does that. Note that it doesn't
`fake' glyphs, this is, it doesn't construct, say, `Amacron' from an
`A' and a `macron' glyph. Any volunteer for this?
May I volunteer
SADAHIRO Tomoyuki <[EMAIL PROTECTED]>
http://homepage1.nifty.com/nomenc
Dear Werner,
you wrote:
This is correct, unfortunately. groff doesn't yet support UTF8 input.
You have to convert your file first to something groff can understand.
Below is a small perl script which does that. Note that it doesn't
`fake' glyphs, this is, it doesn't construct, say, `Amacron' from
> It seems there is a problem with this script.
> If there is an `Amacron' in the data, the script produces `u0100'.
> But glyphs in groff are named in decomposed form,
> glyph name for `Amacron' is `u0041_0304'.
> You can see this from unicode_decomposed hash in afmtodit
> and uniglyph.cpp & glyp
Dear Werner,
It do not think many fonts have that Math Symbols, while `la' and
`ra' are often used in roff files in non-math context
Really? Can you give an example?
.URL from www.tmac uses la and ra
.URL is often used in the groff man pages.
Sincerely, Mic
> .URL from www.tmac uses la and ra
> .URL is often used in the groff man pages.
Aah, I see. Can you do a survey which characters for la and ra could
be used also, this is, what popular UTF8 console fonts actually have?
It should be straightforward to add a fallback character with `.fchar'
to tt
On Wed, Mar 09, 2005 at 09:45:44AM +0100, Werner LEMBERG wrote:
> Aah, I see. Can you do a survey which characters for la and ra could
> be used also, this is, what popular UTF8 console fonts actually have?
> It should be straightforward to add a fallback character with `.fchar'
> to tty.tmac:
>
> > .fchar \[la] <
> > .fchar \[ra] >
>
> Could we do that for \[hy] and \[mi] too?
Of course! Which entities do you suggest?
Werner
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
> > Below is a small perl script which does that. Note that it
> > doesn't `fake' glyphs, this is, it doesn't construct, say,
> > `Amacron' from an `A' and a `macron' glyph. Any volunteer for
> > this?
>
> It seems the following function is what you are looking for:
>
> $NFC_string = NFC($strin
> This is correct, unfortunately. groff doesn't yet support UTF8 input.
> You have to convert your file first to something groff can understand.
>
> Below is a small perl script which does that.
This does not work (Mdk 10.2rc1, groff 1.19 with some mdk patches but they are
unlikely be the cause)
Dear Werner,
you wrote:
No, this is a misunderstanding. I want a library of artificial
characters which combines base characters and accents to composite
characters, e.g.
.fchar \[u0041_0304] \Z''A
.fchar \[-A] \[u0041_0304]
Those macros should work for all platforms and -- if possible -- for
al
> > Below is a small perl script which does that.
>
> This does not work (Mdk 10.2rc1, groff 1.19 with some mdk patches
> but they are unlikely be the cause). Manuals on mdk are in koi8-r,
> my locale ru_RU.UTF-8.
Actually, it does work. See below.
> :3: warning: can't find special character `
> > I want a library of artificial
> > characters which combines base characters and accents to composite
> > characters, [...]
>
> Such substuitution, if done properly, has to be font-dependent and
> resorted to only if the font lacks precomposed characters.
Right. This is what the `.fchar' req
Werner LEMBERG wrote:
> Michail Vidiassov wrote
AFAIK, opentype fonts have tables of relative positions of accented
characters and accents, AFM files can have a section describing the
construction of composites. Can groff use that information?
No. It shouldn't be too difficult to write a scr
Dear Alejandro and All:
as far as I understand, the situation with character composition
in groff is as follows
1) General case
Opentype fonts may have character composition information,
but it is hard to get out of the font.
PS fonts used to have composition information, but it
is of no u
Dear Werner,
On Mon, 14 Mar 2005, you wrote:
> > > I want a library of artificial
> > > characters which combines base characters and accents to composite
> > > characters, [...]
> >
> > Such substuitution, if done properly, has to be font-dependent and
> > resorted to only if the font lacks prec
> as far as I understand, the situation with character composition
> in groff is as follows [...]
Thanks for your analysis, to which I agree.
> 3) Metrics for some decent PostScript or TrueType fonts are to
> be included in groff distribution.
I think this will eventually come. The main ques
On Wed, Mar 09, 2005 at 06:55:48PM +0100, Werner LEMBERG wrote:
> > > .fchar \[la] <
> > > .fchar \[ra] >
> >
> > Could we do that for \[hy] and \[mi] too?
>
> Of course! Which entities do you suggest?
I was going to suggest simply Unicode HYPHEN-MINUS; I know you don't
like it typographica
Dear Werner,
some time ago you wrote:
... groff doesn't yet support UTF8 input.
You have to convert your file first to something groff can understand.
Below is a small perl script which does that.
Attached is a small C program that does that.
Why not to put something like that code into groff
> > ... groff doesn't yet support UTF8 input.
>
> Attached is a small C program that does that.
Michail,
sorry for not answering such a long time. Currently, I don't have
time to look into your stuff since the deadline of the next TeXLive is
near, but I will check it in a few weeks.
We
23 matches
Mail list logo
