Ticket #222 (closed defect: invalid)

Opened 8 years ago

Last modified 8 years ago

Overhall of rest of lang files for plugins - alot of comments

Reported by: anonymous Owned by: gogo
Priority: normal Milestone:
Component: Plugin_Fullscreen Version:
Severity: normal Keywords:
Cc:

Description

Linker de.js and fr.js are missing the strings to translate, delete theese until someone accually translates them.

InsertAnchor Wrong encoding, delete or correct : fr.js de.js

ImageManager Wrong encoding, delete or correct : fr.js

Possible safe to convert : de.js

HtmlTidy Wrong encoding, delete or correct : de.js

Possible safe to convert : nl.js fr.js

FullScreen? Wrong encoding, delete or correct : fr.js

Possible safe to convert : no.js de.js

FullPage? Possible safe to convert : nl.js de.js

DynamicCSS Possible safe to convert : de.js nl.js no.js

ContextMenu Possible safe to convert : nl.js

CharacterMap Wrong encoding, delete or correct : de.js

Possible safe to convert : no.js nl.js it.js

Change History

Changed 8 years ago by kim@…

Forgot to sign my email there, in case someone has any comments. I might be wrong here but from what I can see from the latest CVS this should be correct.

Changed 8 years ago by niko

hmmm... i don't get the problem, why do you think these files are wrong encoded, how do you detect this?

when i open these files in my editor (quanta) as utf-8 encoded everything works!

Changed 8 years ago by kim@…

  • status changed from new to closed
  • resolution set to invalid

Im opening them with textpad, and if they were detected as ANSI I tried opening them in Homesite without any luck. The one thing that boggled me however was that some of the files was opened as UTF-8 and still the characters was messed up, and even Textpad gave me a warning for missing characters... So I might begin to wonder if there is something missing in my Textpad or so.

Whatever it is - I shouldnt be looking at the other lang files, I should focus on the NO files instead, so I close all theese tickets.

Changed 8 years ago by niko

Imho some kind of a magic charset-auto-dedection won't work well without BOM. can't you tell your editor that all JS-files are UTF-8?

...as you closed the ticket, it would be fine for me too when somebody has problems with the encoding of the other languages he should report the errors and we try to fix them then.

Note: See TracTickets for help on using tickets.