109519 - Exporting bookmarks containing non-ASCII characters produces unreadable characters

Status: RESOLVED WORKSFORME

(SeaMonkey :: Bookmarks & History, defect)

Description

[Martin Paquet]

When exporting bookmarks from mozilla 0.9.5 (Build ID: 2001101201), entries
containing french characters in their title area are not exported properly. 
When opening the exported bookmarks in Netscape or Konqueror, french characters
are unreadable.

Example:

Fédération de l'Informatique du Québec 

exports as:

Fédération de l'Informatique du Québec

Comment 1

[alge]

Seems like Moz always exports the bookmarks.html as Unicode.
Sure Unicode is great but IMHO it should export international symbols (like
å(that's an "a" with a ring over, fyi)) as html codes, "å", not unicode codes.

Comment 2

[Claudius Gayle]

reporter, help me out. add a url with a title containg french characters to the
url field of this bug.

Comment 3

[Martin Paquet]

Sorry about the missing URL.  Included now.  Thanks for your help.  Regards.

Comment 4

[Asa Dotzler [:asa]]

->default assignee.

Comment 5

[Andrew Hagen]

Related bug 120759 is now resolved as worksforme. Reporter, could you please
install a recent build, such as 0.9.9 milestone build, and try it again?

Comment 6

[alge]

still seeing this with norwegian characters on a pre-0.9.9 cvs build (couple of
days old)

Comment 7

[Peter Trudelle]

nsbeta1- per Nav triage team.

Comment 8

[Chris Lyon]

This bug should be marked as a duplicate of Bug 109796, wince that bug has a
more complete discussion of the problem.

Comment 9

[Martin Paquet]

Was unable to answer until now.  Just tested exporting French bookmarks and bug
is still present.  Thanks for all your work.  Would like to do more to help but
don't know C enough.  My expertise is more in IBM mainframes.

Comment 10

[Simon Montagu :smontagu]

Changing summary to reflect more accurately the scope of the problem (and avoid
an unfortunate ambiguity in UK English)

Comment 11

[Chris Lyon]

*** Bug 172741 has been marked as a duplicate of this bug. ***

Comment 12

[Daniel Wang]

*** Bug 191074 has been marked as a duplicate of this bug. ***

Comment 13

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 14

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 15

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 16

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 17

[Peter Weilbacher]

I guess all browsers that are now still in existence are smart enough to be able to display the exported bookmarks file in unicode automatically (I just tried SM from comm-central, FF 3.0.11, and Opera 9.64). Just because NS 4.x was broken doesn't mean that we should still keep this bug open. -> WFM