Closed
Bug 827424
Opened 13 years ago
Closed 13 years ago
[l10n: ro] updated upgradedialog.lang file for www.mozilla.org
Categories
(www.mozilla.org :: L10N, defect)
www.mozilla.org
L10N
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: spartakusmd, Unassigned)
Details
Attachments
(1 file, 1 obsolete file)
|
2.30 KB,
text/plain
|
Details |
Confirmed the identical string
| Reporter | ||
Comment 1•13 years ago
|
||
| Reporter | ||
Updated•13 years ago
|
Locale: ro / Romanian
Comment 2•13 years ago
|
||
:)
For confirmation identical string: URGENT! {ok}
You must add this : {ok} after string.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 3•13 years ago
|
||
(In reply to Raul Malea from comment #2)
> :)
>
> For confirmation identical string: URGENT! {ok}
> You must add this : {ok} after string.
Ignored my comment.
| Reporter | ||
Comment 4•13 years ago
|
||
Attachment #698771 -
Attachment is obsolete: true
Comment 5•13 years ago
|
||
Marin, when you add any attachment please add review flag with "?" for my. Email is: raul.malea@gmail.com
Pascal, this file is ok, you can put online. Thanks.
| Reporter | ||
Comment 6•13 years ago
|
||
(In reply to Raul Malea from comment #5)
> Marin, when you add any attachment please add review flag with "?" for my.
> Email is: raul.malea@gmail.com
>
> Pascal, this file is ok, you can put online. Thanks.
OK, I'm sorry.
Comment 7•13 years ago
|
||
This file is has Windows (CRLF)end of lines and a BOM, I will convert it to LF and no BOM first
Comment 8•13 years ago
|
||
also, the {ok} tag should be on the same line as your translation and not the line after:
INCORRECT:
;URGENT!
URGENT!
{ok}
CORRECT:
GOOD
;URGENT!
URGENT!{ok}
Comment 9•13 years ago
|
||
committed in r112029
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 10•13 years ago
|
||
Thanks Pascal. Firstly I wrote {ok} at the end of the line, after the I misunderstood the comment of Raul and I inserted it after the line.
Comment 11•13 years ago
|
||
no problem don't worry :)
You need to log in
before you can comment on or make changes to this bug.
Description
•