[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Standalone 'info' should recode into display's encoding
|
From: |
Gavin Smith |
|
Subject: |
Re: Standalone 'info' should recode into display's encoding |
|
Date: |
Wed, 22 Jan 2014 16:43:42 +0000 |
On Tue, Jan 21, 2014 at 8:46 PM, Gavin Smith <address@hidden> wrote:
> The attached patch implements some support for changing from a UTF-8
> encoded file to an ASCII one.
Anything that replaces strings of characters in a file with strings of
unequal length potentially invalidates the tags table (lists of
offsets within the file of nodes and anchors). There will be ways to
fix this but I haven't thought of what they are yet.
- Re: Standalone 'info' should recode into display's encoding, (continued)
- Re: Standalone 'info' should recode into display's encoding, Eli Zaretskii, 2014/01/01
- Re: Standalone 'info' should recode into display's encoding, Per Bothner, 2014/01/01
- Re: Standalone 'info' should recode into display's encoding, Werner LEMBERG, 2014/01/02
- Re: Standalone 'info' should recode into display's encoding, Per Bothner, 2014/01/02
- Re: Standalone 'info' should recode into display's encoding, Werner LEMBERG, 2014/01/02
Re: Standalone 'info' should recode into display's encoding, Paul Eggert, 2014/01/01
Re: Standalone 'info' should recode into display's encoding, Patrice Dumas, 2014/01/01
Re: Standalone 'info' should recode into display's encoding, Gavin Smith, 2014/01/21
- Re: Standalone 'info' should recode into display's encoding,
Gavin Smith <=