226342 - Faulty links in glossary

Status: VERIFIED FIXED

(SeaMonkey :: Help Documentation, defect)

Description

[u60234]

The links for "Certificate Manager", "cryptographic algorithm", "fingerprint",
"Hypertext Markup Language (HTML)", and "Secure Sockets Layer (SSL)" are broken.
The "server authentication" link in the "authentication" description is also wrong.

Comment 1

[u60234]

Attachment: Proposed patch

Comment 2

[R.J. Keller]

Comment on attachment 135999 [details] [diff] [review]
Proposed patch

r=[e-mail].

Nice catch! Anyone know how to set the approval1.6b flag? I think I'll move it
to Browser: Help in a sec so we can have the flag.

Comment 3

[R.J. Keller]

--> Hasse

Comment 4

[Asa Dotzler [:asa]]

Comment on attachment 135999 [details] [diff] [review]
Proposed patch

a=asa (on behalf of drivers) for checkin to 1.6 beta.

Comment 5

[Brendan Eich [:brendan]]

Do these need to change from SSL to Secure_Sockets_Layer for the anchor name?

http://lxr.mozilla.org/mozilla/search?string=a+name%3D%22SSL%22

/be

Comment 6

[R.J. Keller]

Fix checked in.

Brenden, on what you said, the localizations need to be updated for the new help
content. There have been quite a few changes. In their current state, they do
not need to be modified because they use a different glossary file (which is in
the language of the language pack), which contains different links. Once they
move over to the new, cleaned up glossary, whoever maintains these localizations
will probably change the links. And even if they don't, SSL currently links to a
definition that will refer them to the correct SSL defintion, so it's not a huge
deal if whoever maintains those localizations passes it by (which I doubt they
will do, since it's obvious once you make the anchor changes that links need
updating). I know that currently a lot of changes made to help make it difficult
to update localizations since diff'ing the old files may not work (because they
were removed).

Comment 7

[Brendan Eich [:brendan]]

Are you in touch with localizers?  Maybe a newsgroup post, if not a bug or bugs
on file for followup, would help.

/be

Comment 8

[Daniel Wang]

v