Quote: Here's a snip from site's source - ,,charset=iso-8859-1'' That should be changed to utf-8.Can we possibly get a fix? Thanks!
Please fix unicode in journals/titles!
I am unable to use unicode characters in my journal or it's title and I am hoping this can be correctly easily. A friend of mine looked into it and found the following:
You could fix the 'broken' characters using &x????;-style code (probably writing a program to do this for you; it's a 2 minute job), but unfortunately even then if you go back to edit your post it substitutes in the character so resubmitting breaks the text once again.
I'd welcome a fix!
I'd welcome a fix!
I vouch for that. Changing charset will likely take at most 10 seconds and removing ''ch > 0x7F'' cropping from site's string routines would probably take at most two minutes.
For those that are unknowledgeable in this matter - utf-8 is fully compatible with currently used here iso-1. Sticking with iso-1 means either that person who refuses to fix it is either ignorant or incompetent.
For those that are unknowledgeable in this matter - utf-8 is fully compatible with currently used here iso-1. Sticking with iso-1 means either that person who refuses to fix it is either ignorant or incompetent.
Quote:Original post by Kiput
I vouch for that. Changing charset will likely take at most 10 seconds and removing ''ch > 0x7F'' cropping from site's string routines would probably take at most two minutes.
For those that are unknowledgeable in this matter - utf-8 is fully compatible with currently used here iso-1. Sticking with iso-1 means either that person who refuses to fix it is either ignorant or incompetent.
He is neither ignorant, nor incompetant. He spend loads of time on the site to fix different issues that might be more important than this one, and he constantly try to improve your surfing experience here. He really does this for you.
I recommand you to be more tolerant about issues for which you don't have any clue.
Now, from a bug fix point of view, I don't know any bug that takes only two minutes to fix - unless you don't test the fix and put it directly in production. But that would be a very bad idea, wouldn't it?
Regards,
Quote:Original post by Emmanuel Deloget
He is neither ignorant, nor incompetant. He spend loads of time on the site to fix different issues that might be more important than this one, and he constantly try to improve your surfing experience here. He really does this for you.
I recommand you to be more tolerant about issues for which you don't have any clue.
Now, from a bug fix point of view, I don't know any bug that takes only two minutes to fix - unless you don't test the fix and put it directly in production. But that would be a very bad idea, wouldn't it?
Regards,
Excuse me, but I have a clue about what I'm talking about. I've developed a few sites myself. Obviously you don't seem to notice how simple is the fix. He doesn't have to rewrite the site's engine, he just has to change meta tag in the output HTML and modify site's cropping routines so that they don't remove valid utf-8 literals. That is two minutes of work if one knows what he's doing. (read: knows which routines do the cropping) While this is not the most important issue, it's so simple that having a lot of work isn't any reason to do not fix it.
I hope you understand.
You can "test the fix" by forcing the page to be displayed with the UTF-8 charset. In Firefox 2.0, click View -> Character Encoding -> Unicode (UTF-8).
I'm not sure if there might be glitches here and there, but kiput claimed that the current charset is compatible with the UTF-8 charset. If that's true, then there won't be any glitches here nor there.
I'm not sure if there might be glitches here and there, but kiput claimed that the current charset is compatible with the UTF-8 charset. If that's true, then there won't be any glitches here nor there.
Quote:Original post by KiputAnd yet you know pretty much nothing about our codebase, so trying to estimate how long the changes will take is a pretty foolish thing to do.
Excuse me, but I have a clue about what I'm talking about.
Quote:He doesn't have to rewrite the site's engine, he just has to change meta tag in the output HTML and modify site's cropping routines so that they don't remove valid utf-8 literals.And have you tested such changes using the full unicode charset, and on every browser?
Here's the problem with your proposed fix: Certain browsers (e.g. IE) use the characters present in the page to determine what language the page is in, and may adjust the font accordingly. So, if someone dumps some particular chinese letters into a post, IE can end up thinking that the page is in chinese, so it switches over to using the chinese language pack font - which looks absolutely horrible for the rest of the non-chinese text.
What we'll need to do instead is to convert all unicode characters to HTML escape codes. This is a pretty simple task as well - until you discover that input handling in our codebase is pretty heavily decentralised.
So, this change is possible. However, it's really very, very low on my list of priorities right now. Site stability is a much bigger priority, and then finishing off 4E5. Once those are sorted - which will happen no earlier than next year - then I might be able to sort out something like this.
Well could the fix be a oh... FF Extension?
I'm not trying to be a smartass; I'm be quite serious.
I'm not trying to be a smartass; I'm be quite serious.
If you want to write a firefox extension that converts unicode characters into their HTML escape-code equivalents before submitting the post form, I'm sure people would be quite happy with it.
Even if it does tie them to a particular browser. Why not write a userscript to do this instead?
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement