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.
** Change
** No longer affects: ubiquity-slideshow-ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750367
Title:
Avoide HTML entities in translatable tekst.
To manage notifications about this bug go to:
** Branch linked: lp:~dylanmccall/ubiquity-slideshow-ubuntu/bug-750367
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750367
Title:
Avoide HTML entities in translatable tekst.
To manage notification
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.
--
You re
Oh, I could add translator comments to the POT files, though. Would that
help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750367
Title:
Avoide HTML entities in translatable tekst.
--
ubuntu-bug
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 practic