Avoide HTML entities in translatable tekst.

[AJenbo]

Binary package hint: ubiquity-slideshow-ubuntu

When a string contains "don’t" it makes it unnecessarily hard to read for translators. If the text is in a place where the character isn't allowed it would be better to escape it.

[Dylan McCall (dylanmccall)]

Yeah, I got another bug report about this as well :)
(Bug #749995)

It's too late to change this for Natty, unfortunately — I didn't realise this would be a problem until well past string freeze — but I'll see about fixing it for Ocelot. Ideally it will be a change that maintains the good practice of having proper quotes and apostrophes, maybe replacing them — or escaping them — in the build process. (There are a few scripts that will do that, though I'm unsure how they do for il8n).
I wonder if we can get Launchpad to present these characters better?…

[Dylan McCall (dylanmccall)]

Oh, I could add translator comments to the POT files, though. Would that help?

[AJenbo (ajenbo)]

Yeah I was also thinking having this fixed for next version.

I don't think they are visible in launchpad. They might be helpful for some one who translate using po files.

 Do you commit the text in HTML files, if that is the case then it don't think you need to encoded or escape them.

[Dylan McCall (dylanmccall)]

Yes, that was my instinctive "must support IE6" reflex kicking in. At this point, it should be using the unescaped UTF-8 characters. If that is not happening anywhere, please feel free to submit a bug report. Not sure when it happened, but I'll mark this as fix released to make it clear.