Problem with encoding
Thread poster: Joanna Borowska
Joanna Borowska  Identity Verified
Poland
Local time: 16:57
English to Polish
Aug 26, 2005

When I switch from the Beta to V3 design, the encoding goes crazy (changing from ISO-8859-2 to ISO-8859-1). Even if try switching the design back to the Beta version, the encoding stays changed. The problem disappears only when I go to the list of KudoZ questions and open the question again.

Also, when I entered a response to a peer comment, the encoding was ok, but when I then decided to change my response, the encoding went mad and my new response appeared as a complete mess (only in the new design, though- in the old one everything looks ok).

Now I'm wondering if it's a general problem or just me and my stupid computer. Any ideas?

[Edited at 2005-08-26 16:16]


Direct link Reply with quote
 

Robert Tucker
United Kingdom
Local time: 15:57
German to English
+ ...
Browser settings? Aug 26, 2005

But you are always able to select the correct encoding from View > (Character) Encoding ?

Maybe also check your browser's default encoding is set to the one you most generally use.

Any response you enter will take the encoding to which your browser is set at the time. If you view it with a different browser encoding setting then, of course, (much of) it will appear a mess.

Have a look at:

http://www.proz.com/topic/34280


Direct link Reply with quote
 
Joanna Borowska  Identity Verified
Poland
Local time: 16:57
English to Polish
TOPIC STARTER
not necessarily Aug 26, 2005

Up till now my browser settings were fine, the encoding started switching after the launch of the new design. I remember that some time ago there were similar problems (http://www.proz.com/topic/31706?start=0) but then everything went back to normal (thanks to Jason). It's probably due to all the changes the site has recently been undergoing.




[Edited at 2005-08-27 10:33]


Direct link Reply with quote
 
Joanna Borowska  Identity Verified
Poland
Local time: 16:57
English to Polish
TOPIC STARTER
Beta design is to blame? Aug 27, 2005

Maybe the problem is not with encoding after all. Try looking at my question in the old and then the new design: http://www.proz.com/kudoz/1120970?kd=standard. Although the encoding stays the same (ISO-8859-2), in the new design the quotation marks change into strings of numbers and stuff like #@*&!?# (the same for Polish diacritics). With the old design, everything works fine. Help?

[Edited at 2005-08-27 20:43]


Direct link Reply with quote
 

Robert Tucker
United Kingdom
Local time: 15:57
German to English
+ ...
Reading HTML as text? Aug 27, 2005

ryfka wrote:

Try looking at my question in the old and then the new design: http://www.proz.com/kudoz/1120970?kd=standard. Although the encoding stays the same (ISO-8859-2), in the new design the question marks change into strings of numbers and stuff like #@*&!?# (the same for Polish diacritics). With the old design, everything works fine. Help?


The display is, as far as I can see, the same with my browser set to ISO-8859-1 or ISO-8859-2. The only difference I find is that in the beta version ' , “ and ” are represented by the html encodings for these characters.

The beta version is somehow reading html code as text, it seems to me. But if that's the case, why doesn't it have trouble with the ampersand?


[Edited at 2005-08-27 20:40]


Direct link Reply with quote
 
Joanna Borowska  Identity Verified
Poland
Local time: 16:57
English to Polish
TOPIC STARTER
Thanks, Robert Aug 27, 2005

Now I at least know what the problem is.
And of course I meant QUOTATION marks, not QUESTION marks- sorry for the typo.


Direct link Reply with quote
 

Robert Tucker
United Kingdom
Local time: 15:57
German to English
+ ...
Apostrophes, plain quotes and left and right quotes Aug 27, 2005

Looking into it a bit more, you are using a right single quotation mark rather than an apostrophe and, of course, left and right quotation marks rather than plain vertical ones.

http://www.ascii.cl/htmlcodes.htm

According to:

http://www.pemberley.com/janeinfo/latin1.html#unicode

these are not in the ISO 8859-1 character set.

So maybe it will be the case that if you just use apostrophes and plain quotes you won't have the problem.

Why the non- ISO 8859-1 characters work with the earlier KudoZ versions and not the beta, I still don't know.


Direct link Reply with quote
 
Joanna Borowska  Identity Verified
Poland
Local time: 16:57
English to Polish
TOPIC STARTER
You're right Aug 28, 2005

I usually use "regular" apostrophes (I've checked my other questions and they look ok in both designs). But for this particular question I copied the text from some other source and probably they used the "wrong" quotation marks.

Thanks a lot for all the trouble you took to help me solve the mystery
Cheers!


Direct link Reply with quote
 


To report site rules violations or get help, contact a site moderator:


You can also contact site staff by submitting a support request »

Problem with encoding

Advanced search






memoQ translator pro
Kilgray's memoQ is the world's fastest developing integrated localization & translation environment rendering you more productive and efficient.

With our advanced file filters, unlimited language and advanced file support, memoQ translator pro has been designed for translators and reviewers who work on their own, with other translators or in team-based translation projects.

More info »
Across v6.3
Translation Toolkit and Sales Potential under One Roof

Apart from features that enable you to translate more efficiently, the new Across Translator Edition v6.3 comprises your crossMarket membership. The new online network for Across users assists you in exploring new sales potential and generating revenue.

More info »



All of ProZ.com
  • All of ProZ.com
  • Term search
  • Jobs