[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#5256) encoding of guide.sdf

hyc@symas.com wrote:
> hyc@symas.com wrote:
>> ghenry@suretecsystems.com wrote:
>>> <quote who="dieter@dkluenter.de">
>>>> Hi,
>>>> the guide *.sdf files are UTF-8 encoded, but the online availeable HTML
>>>> files
>>>> seem to be iso8859-1 encoded, which leeds to display errors, an example is
>>>> part
>>>> 9.2.1.
>>>> ... proxyâ??s efficiency ...
>>> Is this something I can fix, or is it part of the doc build for the main
>>> site?
>> It's in the SDF source files, therefore something you should fix. I don't know
>> what text editor you used on those files, but you should use something else,
>> or use one that you can set to just ISO8859-1.
>> I can't think of a grep regex that will detect 8-bit characters, but you need
>> to find them all and get rid of them.
> (Used a binary editor to generate a regexp for [ 0x80 - 0xff ]). There were 
> only two occurrences in the sdf files; both in backends.sdf. Both are the same 
> character, an apostrophe used instead of a single quote.
> (binary patch xx)
> X=`cat xx`
> % grep "[$X]" *.sdf
> backends.sdf:same connection. This connection pooling strategy can enhance the 
> proxy?s
> backends.sdf:maybe stored procedures can?t be considered programming, anyway ;).

I use Vim and gedit. The above would have been copy and paste from the FAQ.

I'll do a Vim trigger to clean up things like this before a commit/make.

Thanks all.

Kind Regards,

Gavin Henry.
Managing Director.

T +44 (0) 1224 279484
M +44 (0) 7930 323266
F +44 (0) 1224 824887
E ghenry@suretecsystems.com

Open Source. Open Solutions(tm).