Closed Bug 309733 Opened 19 years ago Closed 19 years ago

clear unicode sequence for non-breakeable space (\u00a0) in the account's "server parameter" > "advanced" dialog

Categories

(Mozilla Localizations :: fr / French, defect)

x86
Windows 2000
defect
Not set
trivial

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: pov, Assigned: jerome)

Details

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.7.12) Gecko/20050919 Firefox/1.0.7
Build Identifier: Thunderbird 1.4 (Windows/20050922)

Going inside "Outils" -> "Paramètres des comptes..." -> "Paramètres serveur" ->
"Avancés..." (in lower right corner) shows this sentence :
Lors du téléchargement des messages POP pour ce serveur, utiliser le dossier
suivant pour le nouveau courrier\u00a0:

notice the unicode character sequence at the end of the sentence

Reproducible: Always
Thunderbird => Jérôme :)
Assignee: filip → jerome
Status: UNCONFIRMED → NEW
Ever confirmed: true
Attached patch The fix.Splinter Review
The fix.
Patch commited in MOZILLA_1_8_BRANCH and trunk.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
(In reply to comment #2)
> Created an attachment (id=197171) [edit]
> The fix.
> 
> The fix.

Shouldn't it be replaced by   instead of a dumb space, to keep the space
unbreakable and still be compatible with the xml format of the file ?
Typographically speaking, the space before a colon is supposed to be unbreakable
in French.
The space introduced in "The fix" is still unbreakable. It is an UTF-8 encoded
non-breakable space (U+00A0 / char 0160). 

What was wrong is that it was escaped like it should be in properties files
instead of being plain UTF-8, which the right encoding for XML.
(In reply to comment #5)
> The space introduced in "The fix" is still unbreakable. It is an UTF-8 encoded
> non-breakable space (U+00A0 / char 0160). 
> 
> What was wrong is that it was escaped like it should be in properties files
> instead of being plain UTF-8, which the right encoding for XML.

My bad, the default encoding was UTF-8 while viewing the patch, did not see it
was not a regular space. Sorry for the waste of time.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: