Issue 98304 - [ES] printing dialog: paginas derechas e izquierdas"
Summary: [ES] printing dialog: paginas derechas e izquierdas"
Status: CLOSED FIXED
Alias: None
Product: Internationalization
Classification: Code
Component: ui (show other issues)
Version: OOo 2.3.1
Hardware: Unknown All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: petr.dudacek
QA Contact: issues@l10n
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-21 08:38 UTC by rene
Modified: 2017-05-20 10:29 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description rene 2009-01-21 08:38:36 UTC
[ 2.3.0 is not in the box.. ]

forwarding from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=452345, it's
still there in 3.0.1.

--- snip ---
In the printing dialog options when you can choose to print the odds or even pages,
The spanish words that will better reflect that will be "impares" and "pares".
Use "paginas derechas e izquierdas" is confusing.

--- snip --

(I don't speak spanish, so I can't judge the vadility of this..)
Comment 1 rene 2009-01-21 16:17:44 UTC
ENOTENOUGHCAFFEINE. This of course should be at l10n...
Comment 2 richard.holt 2009-01-22 01:54:23 UTC
the op is correct:
"impares" = odd
"pares"   = even

If the statement reads, "Odd or even pages."
then the translation should be, "Páginas impares o pares."

Thanks.
Comment 3 ivo.hinkelmann 2009-01-28 14:25:10 UTC
petr, pls have a look or forward to the spanish folks
Comment 4 stefan.baltzer 2009-06-29 14:13:40 UTC
Note that in the online help, these strings must be adjusted, too.
In OOo 3.1 it reads
 - - - snip - - -
Páginas izquierdas (no disponible para documentos HTML)
Especifica si se deben imprimir todas las páginas izquierdas del documento.
Páginas derechas (no disponible para documentos HTML)
Especifica si se deben imprimir todas las páginas derechas del documento.
 - - - snip - - -
Comment 5 rene 2009-10-02 08:58:03 UTC
This looks fixed long(er) agoi, I at least see it fixed in 3.1.1