Package: groff-base
Version: 1.18.1.1-20
Severity: normal

There are manpages that use \' (the escaped version of the apostroph) to get
"pretty" quotes around words. However \' maps to the acute accent which is
not present in ISO-8859-15 (and some other LatinX variants). Thus the next
command in the pipeline 'iconv -c -f ISO-8859-1 -t ISO-8859-15' happily
strips out those characters.

Which gives some interesting results when this happens to be in a piece of
text that must be rendered bold. On the terminal this is accomplished by
using overstriking meaning every character is printed twice with a backspace
in between. However when some characters are stripped out by iconv there are
stray backspaces left that eat away the remaining text!

Example:

   env LC_ALL=en_US.ISO-8859-15 man smartd.conf

and see the explanation for the -l option. Notice how

   ...by using the '-t short' and '-t long' options...

gets truncated to

   ...by using the-t shor and-t lon options...

Clearly not a very desirable result. Maybe a new mdoc.local rule can be
added like so:

   .  if '\*[.T]'latin1' \
   .    char \' \N'39'

to always map the \' (escaped apostroph) back to the single ' (apostroph)
for the latin1 output device. For UTF8 locales the "pretty" quotes remain
intact. For the ascii output device the escaped apostrophs already get
mapped back to the single ones.


Arjan

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.23.14 (PREEMPT)
Locale: LANG=C, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages groff-base depends on:
ii  libc6                         2.7-12     GNU C Library: Shared libraries
ii  libgcc1                       1:4.3.1-2  GCC support library
ii  libstdc++6                    4.3.1-2    The GNU Standard C++ Library v3

groff-base recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to