Closed
Bug 1184566
Opened 9 years ago
Closed 9 years ago
[l10n: ar] Updated file 'firefox/sync.lang' for SVN repository
Categories
(www.mozilla.org :: L10N, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: abdelrahman1samy, Unassigned)
Details
Attachments
(1 file)
2.28 KB,
text/plain
|
Details |
I finished translating all the strings.
Comment 1•9 years ago
|
||
Strings are reviewed and committed
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 2•9 years ago
|
||
I reverted the file you committed in r144455. As in bug 1184561, make sure to check what you're committing, especially if coming from new contributors. Not UTF-8, removed ; at the beginning of the English strings, changed spacing (empty lines) between strings.
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: FIXED → ---
Comment 3•9 years ago
|
||
I copied over the strings in the attachment to the correct file, please verify if everything looks good in r144459. For the future, please always make sure to attach the file you download from SVN using the "Your translated file" link. https://l10n.mozilla-community.org/~pascalc/langchecker/?locale=ar#firefox/whatsnew_38.lang Also make sure to use a proper text editor, for example SublimeText, Notepad++, etc.
Comment 4•9 years ago
|
||
Thanks Francesco, The file look good and also checked it on the website.. I took notes for all your comments.
Comment 5•9 years ago
|
||
OK, marking fixed then. Note that your files didn't have any issues. Fixing empty lines is easy and done automatically by scripts, it's a lot harder to understand what happened when a file with the wrong encoding lands (in this case it was considered binary on my system).
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
Comment 6•9 years ago
|
||
I downloaded Notepad++ and I checked now the settings for that to make sure that it is saved with UTF8. I will inform the localizers too about this.
Comment 7•9 years ago
|
||
One more suggestion: before committing, always run "svn diff" to check what the actual differences are. If you're on *nix systems, you can pipe the command, e.g. svn diff|gedit
Comment 8•9 years ago
|
||
I did that with the last commit to make sure that there is nothing missing in the file. I think I have more understanding of the process now.
You need to log in
before you can comment on or make changes to this bug.
Description
•