257928 - apostrophe and other characters corrupted in bookmarks

Status: RESOLVED DUPLICATE of bug 245758

(SeaMonkey :: Bookmarks & History, defect)

Description

[Richard Briscoe]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a3) Gecko/20040902
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.4, 20040903)

Upon launching Moz 1.7.x for some time there has been a problem with apostrophes
and quotation marks being corrupted.  This problem no longer exists in 1.8a3.  

I have used a set of bookmarks which I have inspected to be free of the problem
and immediately upon launching Moz 1.7.4 the apostrophes and quotation marks are
corrupted.  

This appears to be related to some of the bug reports filed for PCs and one
which I seem to remember as being "all", but is closed.  Firefox bug #246419
appears to be the same occurrence insofar as it involves the apostrophe.  I am
unaware of a bug report on the quotation marks, but there could have been one.

Reproducible: Always
Steps to Reproduce:
1.Launch Moz 1.7.4 using existing profile with "clean" bookmarks.
2.Open bookmarks either in side bar or manage bookmarks and examine.
3.By observation the apostrophes and quotation marks which were OK before the
Moz 1.7.4 launch are corrupted.



Expected Results:  
Apostrophes and quotation marks should have been rendered as intended rather
than a string of other characters.

This is probably a *partial* duplication of other bugs in that it involves the
same subject matter, but I have not found a current bug dealing with Moz 1.7.x
in OS X.

Comment 1

[Gérard Talbot]

> Launch Moz 1.7.4
Is there a 1.7.4 version released?

Please have a look at
http://bugzilla.mozilla.org/show_bug.cgi?id=255087#c1

One way to work around this bug is to delete the bookmark and then bookmark the
page again: that trick works for me under XP Pro. The idea is that the new
format of the bookmark will be unicode.

I'm going to mark this bugfile as a DUPLICATE of bug 245758 instead of bug 252031.

*** This bug has been marked as a duplicate of 245758 ***