[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev [PATCH] minor doc update

From: Thomas Dickey
Subject: Re: lynx-dev [PATCH] minor doc update
Date: Fri, 22 Sep 2000 20:56:32 -0400
User-agent: Mutt/1.2.5i

On Fri, Sep 22, 2000 at 05:03:11PM -0600, address@hidden wrote:
> In a recent note, Thomas Dickey said:
> > Date: Fri, 22 Sep 2000 05:25:20 -0400
> > 
> > but there's nothing that I see that forces archiving as text.
> > 
> To my understanding, archiving as text means setting a flag in
> the archive directory.  Zip makes this decision on a statictical
> analysis of (the beginning of) each file.  One of the .po files
> contains enough non-Roman characters that this flag says "binary"
> rather than "text".  -aa works fine on OS/390.  On ASCII UNIX
> it doesn't matter.  The file(s), BTW, are:
>     address@hidden:185$ unzip -a ../ | more
>         [ ... ]
>     inflating: lynx2-8-4/docs/README.TRST  [text]
>     inflating: lynx2-8-4/docs/  [binary]
>     inflating: lynx2-8-4/  [text]
>         [ ... ]
>     inflating: lynx2-8-4/po/readme     [text]
>     inflating: lynx2-8-4/po/ru.po      [binary]

I don't see that the ru.po is worse than the next file - several characters
in the 0xa0-0xff range.  Perhaps zip uses some threshold (or are you using
the large unbundled ru.po - I'm only reading the 1293-character stub)?

>     inflating: lynx2-8-4/po/pt_BR.po   [text]

Thomas E. Dickey <address@hidden>

; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]