Closed Bug 662902 Opened 14 years ago Closed 6 years ago

[es-AR] SeaMonkey help files are in English

Categories

(Mozilla Localizations :: es-AR / Spanish (Argentina), defect)

Product:
Mozilla Localizations
Component:
es-AR / Spanish (Argentina)
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: kavalec74, Assigned: enzomatrix)

Details

User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20110531 SeaMonkey/2.1pre Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20110531 SeaMonkey/2.1pre the help files of es-AR are not in Spanish, but in English. Every citizen of Latin America understands the Spanish of Spain without any problems, even there are a few, for understanding insignificant, differencies. Most doubled movies here in Argentina are spoken in Spanish of Spain, most books are also printed in Spain. Every latin-hispanic understands better Spanish of Spain than English. There is really no problem with this. I recommend you use the es-ES localization of help files untill the localizators of es-Ar get the files ready, in a few years :) Reproducible: Always Steps to Reproduce: 1. press F1 in es-AR installation 2. 3. Actual Results: Help files in English Expected Results: Help files in Spanish of Latin America or Spanish of Spain, not in English
This is a localization bug.
Assignee: nobody → enzomatrix
Component: Composer → es-AR / Spanish (Argentina)
Product: SeaMonkey → Mozilla Localizations
QA Contact: composer → enzomatrix
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Summary: es-AR help files are in English → [es-AR] SeaMonkey help files are in English

Marcelo, is this a WONTFIX a this point?

Flags: needinfo?(enzomatrix)

Sorry. Help files were localized years ago and I never mark this bug as FIXED.
I can confirm that help is localized in SeaMonkey 2.49.4 downloaded minutes ago.

Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Flags: needinfo?(enzomatrix)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.