Alexander E. Patrakov wrote:
> DJ Lucas wrote:
>
>>
>> No..only groff CVS.
>>
>
> No, not even groff CVS, because it expects different command line
> options than those hard-coded in Man-DB.
>
I have not looked, but I wonder if he is working on that. He had
mentioned 2.5.3 in that rep
DJ Lucas wrote:
> Ken Moffat wrote:
>> On Tue, Oct 07, 2008 at 05:59:14PM -0500, Randy McMurchy wrote:
>>
>>> Hi all,
>>>
>>> I'm way on the downhill side of getting all the package
>>> updates in. Groff is sort of a bugaboo, however. The
>>> DJ book uses the Groff-UTF8 package, but I'm not sure
Ken Moffat wrote:
> On Tue, Oct 07, 2008 at 05:59:14PM -0500, Randy McMurchy wrote:
>
>> Hi all,
>>
>> I'm way on the downhill side of getting all the package
>> updates in. Groff is sort of a bugaboo, however. The
>> DJ book uses the Groff-UTF8 package, but I'm not sure it
>> does much.
>>
>> P
Randy McMurchy wrote:
> Hi all,
>
> I'm way on the downhill side of getting all the package
> updates in. Groff is sort of a bugaboo, however. The
> DJ book uses the Groff-UTF8 package, but I'm not sure it
> does much.
>
> Please give some input if you have any on this subject.
> It would be an add
On Tue, Oct 07, 2008 at 05:59:14PM -0500, Randy McMurchy wrote:
> Hi all,
>
> I'm way on the downhill side of getting all the package
> updates in. Groff is sort of a bugaboo, however. The
> DJ book uses the Groff-UTF8 package, but I'm not sure it
> does much.
>
> Please give some input if you ha
> > 1. An acute accent is not a quoting character. Anyone using an
> > acute accent for quoting is abusing this character.
>
> Agreed, Groff should be fixed. Also it probably should use Unicode
> bullets (not middle dots) for bullets.
I won't change the defaults. From the PROBLEMS file:
*
Alexander E. Patrakov wrote:
> >The ACUTE ACCENT part looks wrong.
>
> But libiconv also transliterates it to "'" :)
The correctness criteria for glibc are stronger than for libiconv, since
it's used by many more people.
It can also be a bug in libiconv, due to the fact that at the time when
I in
Bruno Haible wrote:
As for the "iconv" program from glibc, the situation is worse. I have
prepared a patch against Glibc-2.3.6 (attached) that transliterates the
offending characters produced by Groff into their ASCII equivalents if
there is no any other suitable fallback. You can try it without
Alexander E. Patrakov wrote:
> >Why should they complain? They can use GNU libiconv. It transliterates the
> >bullet to 'o', like you wish.
>
> The "iconv" program from libiconv transliterates the bullet to ".",
> which is also acceptable.
libiconv converts the MIDDLE DOT to '.' and the BULLET and
I wrote:
Is this patch a right solution?
Forgot to say: even if it is, it would be insane to require patched or
not-yet-released version of glibc just for viewing manual pages "the
right way" in locales such as pl_PL. A short-term distro-friendly
solution is also needed. Any ideas?
--
Ale
Bruno Haible wrote:
Alexander E. Patrakov wrote:
The answer "patch
glibc so that iconv transliterates the bullet to 'o'" is better (and in
fact this is doable), but I think that users of non-Glibc systems (or
old Glibc) will complain if this becomes the official answer.
Why should the
Alexander E. Patrakov wrote:
> The answer "patch
> glibc so that iconv transliterates the bullet to 'o'" is better (and in
> fact this is doable), but I think that users of non-Glibc systems (or
> old Glibc) will complain if this becomes the official answer.
Why should they complain? They can use
12 matches
Mail list logo
