[FM Discuss] Fwd: About http://translate.flossmanuals.net encoding

[Aleksandar Erkalovic]

hi,

this is strange... but it seems i found a way how to fix it. soo.. if
you go to arrange toc:

http://translate.flossmanuals.net/bin/arrange/ActivitiesGuideSugar_es

it is suppose to use utf-8  but i see my browser has autodetected it
is iso8859-1 page. if it is iso8859-1, it will show those characters
ok. if i select utf-8 again, it will show silly characters.

if i go to view page:

http://translate.flossmanuals.net/bin/view/ActivitiesGuideSugar_es

i get the same story.... utf-8 shows funny characters and iso8859-1
(autodetected as correct encoding) shows funny characters.

is this chapter titles something that has been copy+pasted from
somewhere else or was it entered from the keyboard? what probably
happened is... someone had wrong encoding inside the browser, and was
pasting or entering utf8 characters.

anyhoo... this is what i did to fix it. so i went to:
http://translate.flossmanuals.net/bin/arrange/ActivitiesGuideSugar_es
i selected utf-8 encoding in my browser for this page. i edited
chapter name and i entered this "Ó" character. i saved it. seems to
work for the first chapter. somebody who has some idea about spanish
should change the rest of the chapter names like this. i am not so
sure about that upside down ? character.

aco


On Mon, Dec 13, 2010 at 4:31 PM, James Simmons <nicestep at gmail.com> wrote:
> Aleksander,
>
> I assume we're talking about the Spanish version of "Make Your Own
> Sugar Activities!" here.  I used Babel Fish to create a rough
> translation of the chapter titles and the contents because I don't
> speak the language.  Native speakers have been polishing it, as has a
> retired teacher who does speak the language.  When you edit the TOC
> entries they look OK, as I remember, but when the text is displayed it
> looks funny.
>
> As an American my knowledge of non-ascii encodings is rudimentary at best.
>
> James Simmons
>
>
>
> On Mon, Dec 13, 2010 at 6:46 AM, Aleksandar Erkalovic
> <aerkalov at gmail.com> wrote:
>> when adam said "flat files" he wanted to say it is twiki platform.
>> twiki platform is using flat files to save data (with utf8 encoding).
>> there is no sqlite or postgres here.
>>
>> now, this is not the first book with non ascii characters in latin. so
>> it is not general problem with encodings. encodings in chapters seems
>> fine.
>> encodings in TOC seems to have problems. normaly it does not have
>> problems.... but this time it has. so this is isolated problem and i
>> will have a look at this. might be that someone was manualy editing
>> toc on the disk.. that would make a problem... or maybe it is
>> this silly character that makes problem. english is not my native
>> language, so i am familiar with this non ascii problem. i have tested
>> it
>> with many silly croatian characters and it worked fine. it worked for
>> farsi that is also RTL :) will check this problem after work.
> _______________________________________________
> Discuss mailing list
> Discuss at lists.flossmanuals.net
> http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net
>



-- 
 http://www.binarni.net/