Colin Watson wrote:
> > I don't much like any of the switch ideas, since they would probably
> > not be able to express all possible collections of man pages (given
> > debhelper's current command line parser). The manpage:encoding idea
> > could work, but might have ambiguity issues with man pages
On Fri, Oct 12, 2007 at 01:41:49PM +0300, Antti-Juhani Kaijanaho wrote:
> On Thu, Oct 11, 2007 at 12:42:49PM -0400, Joey Hess wrote:
> > The manpage:encoding idea could work, but might have ambiguity issues
> > with man pages with colons in their name
>
> I think that's solvable by taking the las
On Thu, Oct 11, 2007 at 12:22:18PM +0100, Colin Watson wrote:
> I have uploaded man-db 2.5.0-1, which includes the following changes of
> note:
[...]
>
> groff does not yet support UTF-8 input, so at the moment this is
> implemented by recoding in man. For the time being, the implementation
> req
On Fri, Oct 12, 2007 at 12:03:56PM +0100, Colin Watson wrote:
> On Fri, Oct 12, 2007 at 08:51:31AM +0900, Junichi Uekawa wrote:
> > I assume UTF-8 / local-encoding detection can fail sometimes; which
> > encoding has precedence?
>
> You're right, it can. It's much more likely that a random non-UTF
set but not the country, and so a full
> > locale name is inconvenient.
> >
> > o There is a new "manconv" program which can try multiple possible
> > encodings for a file, thus allowing UTF-8 manual pages to be
> >
On Thu, Oct 11, 2007 at 12:42:49PM -0400, Joey Hess wrote:
> The manpage:encoding idea could work, but might have ambiguity issues
> with man pages with colons in their name
I think that's solvable by taking the last colon. I don't think
encodings have colons in them.
--
Antti-Juhani Kaijanaho
On Thu, Oct 11, 2007 at 12:42:49PM -0400, Joey Hess wrote:
> I don't much like any of the switch ideas, since they would probably
> not be able to express all possible collections of man pages (given
> debhelper's current command line parser). The manpage:encoding idea
> could work, but might have
On Fri, Oct 12, 2007 at 10:00:21AM +0200, Josselin Mouette wrote:
> Le jeudi 11 octobre 2007 à 12:22 +0100, Colin Watson a écrit :
> > My original plan was that UTF-8 manual pages should be installed in
> > /usr/share/man/.UTF-8/ (unless your language is Chinese or
> > Por
Le jeudi 11 octobre 2007 à 12:22 +0100, Colin Watson a écrit :
> My original plan was that UTF-8 manual pages should be installed in
> /usr/share/man/.UTF-8/ (unless your language is Chinese or
> Portuguese, just use the language code, not the country code, so for
> example French
gt;
> o There is a new "manconv" program which can try multiple possible
> encodings for a file, thus allowing UTF-8 manual pages to be
> installed in any directory even without an explicit encoding
> declaration.
This is cool.
A grea
Colin Watson wrote:
> Once we have a consensus on install locations, dh_installman should IMO
> be changed to do the recoding automatically; to do this, it needs to be
> told the source encoding. Joey, what do you think is the best way to do
> this? Options that come to mind are:
>
> * --languag
, and so a full
locale name is inconvenient.
o There is a new "manconv" program which can try multiple possible
encodings for a file, thus allowing UTF-8 manual pages to be
installed in any directory even without an explicit encoding
declarati
12 matches
Mail list logo
