Your message dated Sun, 19 Apr 2020 16:48:20 +0200
with message-id <[email protected]>
and subject line Re: [debian-faq-fr] 6.2.2 D'où proviennent les noms de code ?: 
"wheezy est le nom du manchot au n½ud papillon rouge" (wrong encoding)
has caused the Debian Bug report #721683,
regarding [debian-faq-fr] 6.2.2 D'où proviennent les noms de code ?: "wheezy 
est le nom du manchot au n½ud papillon rouge" (wrong encoding)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
721683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721683
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debian-faq-fr
Version: 5.0.2
Severity: minor
X-Debbugs-Cc: [email protected]

Section 6.2.2 "D'où proviennent les noms de code ?" contains:
wheezy est le nom du manchot au n½ud papillon rouge
"noeud" really reads "n½ud". This is surely due to the ligature, since it isn't 
an ASCII character, yet all other characters are fine and even the source looks fine: 
http://anonscm.debian.org/viewvc/ddp/manuals/trunk/debian-faq/po4a/po/fr.po?view=markup

Could the build be buggy?

--
Filipus Klutiero
http://www.philippecloutier.com

--- End Message ---
--- Begin Message ---
Version: 10.0


Filipus Klutiero <[email protected]> wrote:
> Section 6.2.2 "D'où proviennent les noms de code ?" contains:
> > wheezy est le nom du manchot au n½ud papillon rouge
> "noeud" really reads "n½ud". This is surely due to the ligature, since it 
> isn't an ASCII character, yet all other characters are fine and even the 
> source looks fine: 
> http://anonscm.debian.org/viewvc/ddp/manuals/trunk/debian-faq/po4a/po/fr.po?view=markup
> 
> Could the build be buggy?

This has been fixed with the conversion to Docbook in package version 10.0

Closing this bug.

Holger


-- 
Holger Wansing <[email protected]>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

--- End Message ---

Reply via email to