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

Status: RESOLVED DUPLICATE of bug 1050151

(Thunderbird :: Message Reader UI, defect)

Description

[David Puente]

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.

Comment 1

[David Puente]

Attachment: date.jpg

Comment 3

[RickieES aka Ricardo Palomares]

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

Comment 4

[Magnus Melin [:mkmelin]]

(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?

Comment 5

[David Puente]

Excellent!!!!!!!!!! With the new file it works fine :)

Comment 6

[RickieES aka Ricardo Palomares]

(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.

Comment 7

[Mark Banner (:standard8)]

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).

Comment 8

[RickieES aka Ricardo Palomares]

(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.