String.ini

laulau · Post by **laulau** » Mon 19 Jan 2015 6:12 pm

Hi,
I have accented characters in string.ini, i've converted the file to UTF-8.
In dashboard forecast is ok now.
In internet index.htm it isn't but it's ok in gauges.htm !
Is there an issue or am i doing something wrong ?

CaptCMX.JPG

CaptCMX1.JPG

CaptCMX2.JPG

Post by **steve** » Mon 19 Jan 2015 6:29 pm

I'm not sure why it isn't working on the index.htm page, but the realtimegauges file uses <#forecastenc>, so the character gets 'web encoded' as ô which is why it works OK in the gauges ticker.

mcrossley · Post by **mcrossley** » Mon 19 Jan 2015 7:13 pm

Laurent, do you have a link to your MX pages?

mcrossley · Post by **mcrossley** » Mon 19 Jan 2015 7:25 pm

It's OK I found your MX site.

Did you save index.html as UTF-8 when you edited it?

laulau · Post by **laulau** » Mon 19 Jan 2015 7:27 pm

http://ialsacem4.chez.com/index.htm

laulau · Post by **laulau** » Mon 19 Jan 2015 7:33 pm

mcrossley wrote:It's OK I found your MX site.

Did you save index.html as UTF-8 when you edited it?

Yes but it look's like the processed file is no longer !

laulau · Post by **laulau** » Sat 24 Jan 2015 11:19 pm

It seems that all the standard files are not UTF-8 encoded after being processed !

Post by **steve** » Sun 25 Jan 2015 9:08 am

Mine are - if I look at trends.htm in notepad++, it shows as UTF-8 w/o BOM. Some/all of the others show as ANSI in notepad++ but that's because mine don't have any 'special' characters in them so they look like ANSI. I'm not sure what it is about trends.htm that makes it detectable as UTF-8.

Note that there was a bug with extra files where the utf-8 setting was being saved.

Could you zip up your strings.ini and your amended indexT.htm file, and I'll take a look.

laulau · Post by **laulau** » Sun 25 Jan 2015 9:17 am

Hi,
I also add the processed index.htm file, you can see that the accented characters are not 'well' encoded.

Post by **steve** » Sun 25 Jan 2015 9:23 am

They're all UTF-8, so that isn't the problem. Perhaps I need to do something similar to what I did for the all-time records problem. I'll experiment...

Post by **steve** » Sun 25 Jan 2015 1:08 pm

I'm having real problems fixing this without breaking the encoding on other things. I think you will have to use <#forecastenc> instead of <#forecast>, for now at least.

laulau · Post by **laulau** » Sun 25 Jan 2015 2:46 pm

No problem.
I'm running CMX for beta testing purpose.

Post by **steve** » Sun 25 Jan 2015 3:20 pm

I have a solution now which just fixes the forecast without breaking anything else. But I think I now have to apply the same thing to some other web tags. At the moment I'm not sure which ones. It's very confusing. Perhaps just the ones from strings.ini...

laulau · Post by **laulau** » Sun 25 Jan 2015 10:24 pm

I've installed last CMX build (3014).
I'm not able to confirm

Accented characters in forecast strings don't display properly on web page - should be fixed in 3014

because no accented characters in forecast at the time i'm writing.
I noticed something else : my pressure trend tag "$presstrend = ""; "is empty but "$presstrendenglish = "Falling"" isn't!
(OK for the temptrendtext)

laulau · Post by **laulau** » Mon 26 Jan 2015 7:45 am

This morning i can confirm that forecast with accented characters from string.ini is fixed.

Cumulus Support

String.ini

String.ini

Re: String.ini

Re: String.ini

Re: String.ini

Re: String.ini

Re: String.ini

Re: String.ini

Re: String.ini

Re: String.ini

Re: String.ini

Re: String.ini

Re: String.ini

Re: String.ini

Re: String.ini

Re: String.ini