Incorrect spanish reply header, literally says "#4" instead of the actual time

RESOLVED DUPLICATE of bug 1050151

Status

RESOLVED DUPLICATE of bug 1050151
4 years ago
4 years ago

People

(Reporter: dpuenteb, Unassigned)

Tracking

31 Branch
x86_64
Windows 7

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.143 Safari/537.36

Steps to reproduce:

When I reply a message.


Actual results:

It returns "El 02/09/2014 a las #4, Pepa Sánchez de Miguel escribió:" So the hour is not shown correctly


Expected results:

replace #4 with the hour.
(Reporter)

Comment 1

4 years ago
Created attachment 8482827 [details]
date.jpg

Updated

4 years ago
Summary: reply date incorrect → Incorrect spanish reply header, literally says "#4" instead of the actual time
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1050151
For the OP: please note the we have released an updated XPI to fix the problem, since Thunderbird ESR does not accept L10n updates:

http://www.proyectonave.es/node/360
(In reply to Ricardo Palomares from comment #3)
> For the OP: please note the we have released an updated XPI to fix the
> problem, since Thunderbird ESR does not accept L10n updates:

I recall in the past there used to be even new localizations coming in later on in the security releases. 
What is the reason not to allow localizations to include the fixes they need?
Flags: needinfo?(standard8)
(Reporter)

Comment 5

4 years ago
Excellent!!!!!!!!!! With the new file it works fine :)
(In reply to Magnus Melin from comment #4)
> I recall in the past there used to be even new localizations coming in later
> on in the security releases. 
> What is the reason not to allow localizations to include the fixes they need?

Don't really know the reason for certain. I think it is because we (localizers) don't really have access to a "release channel" repository, thus we can't only land fixed in beta, aurora or central channels.
Ricardo is right, we haven't historically taken changes for localizations for ESR cycles. However, given the obvious user-facing impact of this, I've taken the fix referenced from bug 1050151 and applied it for all the future 31.x releases - this fix will be first released in 31.2.0 next Tuesday (14th Oct).
Flags: needinfo?(standard8)
(In reply to Mark Banner (:standard8) from comment #7)
> Ricardo is right, we haven't historically taken changes for localizations
> for ESR cycles. However, given the obvious user-facing impact of this, I've
> taken the fix referenced from bug 1050151 and applied it for all the future
> 31.x releases - this fix will be first released in 31.2.0 next Tuesday (14th
> Oct).


Thank you! :-) I'll post a note in our website to let our users know it.
You need to log in before you can comment on or make changes to this bug.