Closed Bug 930528 Opened 11 years ago Closed 11 years ago

[Buri][language] Wrong time format in the statusbar of ES

Categories

(Mozilla Localizations :: es-ES / Spanish, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Pike, Assigned: rpmdisguise-nave)

References

Details

The short month names in Spanish are ending in a '.', which makes the status bar show

oct., operator

which is looking weird.

Can the short months (and possibly days) be used without the '.'?

+++ This bug was initially created as a clone of Bug #929913 +++

DEFECT DESCRIPTION:
 REDUNDANT FULL STOP AFTER THE MONTH
 
  REPRODUCING PROCEDURES:
 1. Open the notifications.
 2. Look at the date in upper left corner. There's a redundant full stop after the month name.
 
  EXPECTED BEHAVIOUR:
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE:
 100%
 
  For FT PR, Please list reference mobile's behavior:
Depends on: 930533
No longer depends on: 930533
Hi Axel,

As a matter of fact, I removed all the full stops from both abbreviated months and days in v1.2 last week. They're all in shareddate file, right? So, considering the last push was on October 20th, this issue should be fixed by now. 

I don't know why those full stops still appear on the status bar in Spanish.
Actually, including the trailing dot in abbreviations is mandatory, according to RAE:

http://lema.rae.es/dpd/?key=abreviatura

The ".," sequence shouldn't look weird to Spanish speakers.
(In reply to Ricardo Palomares from comment #2)
> Actually, including the trailing dot in abbreviations is mandatory,
> according to RAE:
> 
> http://lema.rae.es/dpd/?key=abreviatura
> 
> The ".," sequence shouldn't look weird to Spanish speakers.

Hi guys,

Using trailing/abbreviation dots is correct and mandatory in Spanish, that's why we used them in previous Gaia versions :) 

But then, I realized the status bar looks cluttered with punctuation marks. Punctuation rules were designed for writing/reading contexts where space was not a limitation, which is right the opposite case of mobile devices. 

IMHO, one of our roles as localizers is to try to adapt and update those pre-digital era rules to new environments and content, and make sure there is a proper balance between correction and UX.

Alternatively, we could rephrase the syntax like this: "oct. Operator", the dot functioning both as an abbreviation sign and separator.

Please let me know what you think.
I could live without the comma if absolutely needed. BTW, the whole purpose of abbreviations is saving space, :-) regardless of whether they are used in a paper or a mobile screen, and the dot is used to clearly mark the abbreviation as such and let the reader figure out the full term, instead of having to decide if the writer made a typo.
(In reply to Ricardo Palomares from comment #4)
> I could live without the comma if absolutely needed. BTW, the whole purpose
> of abbreviations is saving space, :-) regardless of whether they are used in
> a paper or a mobile screen, and the dot is used to clearly mark the
> abbreviation as such and let the reader figure out the full term, instead of
> having to decide if the writer made a typo.

That's exactly what I mean. This kind of punctuation rules makes sense in personal handwriting, typing, and old printing methods. 

But in a content that has been reviewed, revised, and proofread to make sure it's correct and meets the QA standards of a specific language, what's the point of using a punctuation mark to warn readers/users the word is abbreviated and not a typo?


BTW, can we remove the comma without other locales being affected?
(In reply to inma_610 from comment #5)
> BTW, can we remove the comma without other locales being affected?

Absolutely yes (that's exactly what I did, now it displays "26 ott. OPERATOR" for Italian).
(In reply to Francesco Lodolo [:flod] from comment #6)
> Absolutely yes (that's exactly what I did, now it displays "26 ott.
> OPERATOR" for Italian).

Thank you, flod!


Marking this bug as resolved.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.