[Live-demo] Converting docs to UTF encoding

[Zhengfan Lin]

Thanks for the dos2unix suggestion.

I decided not to do anything for now. We are very close to 6.0 and I can't
confirm DOS/Win EOL is actually causing any problem. (At least the HTMLs
are fine.) It should be a good idea to keep things as they are as long as
they are not broken so we can save some possible trouble fixing new issues
in a hurry. I'll try to convert the EOLs after 6.0 release.

Best,

Zhengfan Lin
 On Aug 6, 2012 12:46 PM, "Jorge Gaspar Sanz Salinas" <jsanz at osgeo.org>
wrote:

> On 6 August 2012 07:34, Zhengfan Lin <public.t.lin at gmail.com> wrote:
> > Translating to Chinese under Ubuntu using GEdit with system locality set
> as
> > En_US.UTF-8. No encoding problem found.
> >
> > One thing that does worry me is line encoding. Most En docs I found use
> MS
> > Win style EOL (0x0D0A). HTML conversion seems to work fine with that, but
> > Unix style (0x0A) could be more secure. Should we convert EOL ? Besides,
> is
> > absence of last line EOL a problem ?
> >
> > -
> > Zheng-Fan LIN
> >
> >
> > PS: Sorry for replying only to Jorge one hour ago. Wrong button...
> >
> >
>
> If HTML docs are being rendered well it's not a huge problem, dos2unix
> should solve tho problem. You can concatenate the find command I sent
> with dos2unix to exectue it in all files with windows EOL.
>
> If you want me to do it and commit the files I can do it also.
>
> Best regards
>
> --
> Jorge Sanz
> http://es.osgeo.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/live-demo/attachments/20120809/6ca31751/attachment.html>