Closed
Bug 346613
Opened 19 years ago
Closed 19 years ago
Spanish language message incorrect when opening pages over a secure connection
Categories
(Mozilla Localizations :: es-ES / Spanish, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: juane_col, Assigned: knocte)
Details
Attachments
(1 file)
|
16.73 KB,
image/jpeg
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Win98; es-ES; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5
Build Identifier: Mozilla/5.0 (Windows; U; Win98; es-ES; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5
When opening pages over a secure (SSL) connection, Firefox (the version in Spanish that can be downloaded from http://www.mozilla-europe.org/es/products/firefox/), gives a Spanish-language message with a mistake. The message is:
"Ha solicitado una pagina sin cifrar. El sitio web se ha identificado correctamente, y la informacion que vea o introduzca en esta pagina no puede ser leida facilmente por terceras personas."
The first phrase "Ha solicitado una pagina sin cifrar.", is wrong. The correct phrase is "Ha solicitado una pagina cifrada."
Reproducible: Always
Steps to Reproduce:
1. Install Firefox (Spanish language version)
1. Launch Firefox
2. Type the URL of a SSL page
3. You will get the wrong message (unless you have disabled the messages to appear by leaving blank the checkbox "Avisarme cada vez que vaya a ver una pagina cifrada." that appears when you open a SSL connection for the first time, after you install Firefox)
Expected Results:
Display the right message.
| Reporter | ||
Comment 1•19 years ago
|
||
| Reporter | ||
Updated•19 years ago
|
Version: unspecified → 1.5.0.x Branch
Updated•19 years ago
|
Assignee: nobody → knocte
Component: General → es-ES / Spanish
Product: Firefox → Mozilla Localizations
QA Contact: general
Version: 1.5.0.x Branch → unspecified
Comment 2•19 years ago
|
||
The string is fixed, as it can be seen at:
http://lxr.mozilla.org/l10n-mozilla1.8/source/es-ES/security/manager/chrome/pipnss/security.properties#4
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•