Patch #2126
closed
Slovak language pack
Added by Stanislav Pach about 16 years ago. Updated about 16 years ago.
100%
Description
I have created Slovak (SK) language pack. The most of translation is finished (~95%). Maybe someone will appreciate it ;)
Files
| sk.yml (28.1 KB) sk.yml | Stanislav Pach, 2008-11-02 20:32 | ||
| calendar-sk.js (3.67 KB) calendar-sk.js | Translated calendar | Stanislav Pach, 2008-11-03 22:23 | |
| jstoolbar-sk.js (765 Bytes) jstoolbar-sk.js | Translated toolbar | Stanislav Pach, 2008-11-03 22:23 | |
| sk.yml (28.1 KB) sk.yml | Translated main language file | Stanislav Pach, 2008-11-03 22:23 | |
| calendar-sk.js (2.83 KB) calendar-sk.js | Calendar SK javascript - fixed version from 9.11.2008 | Stanislav Pach, 2008-11-09 00:50 | |
| sk.yml (28.2 KB) sk.yml | Main translation file - fixed version from 9.11.2008 | Stanislav Pach, 2008-11-09 00:50 | |
| sk.yml (28.2 KB) sk.yml | Main translation file - second version from 9.11.2008 (28.2 KB) | Stanislav Pach, 2008-11-09 11:20 | |
| sk.yml (28.3 KB) sk.yml | Updated new string label_example | Stanislav Pach, 2008-11-09 17:31 |
Updated by Thomas Lecavelier about 16 years ago
- Target version changed from 0.7.3 to 0.8
Thank you for the translation. Please don't target versions already released.
Updated by Azamat Hackimov about 16 years ago
- Assignee set to Azamat Hackimov
Stanislav, you need translate too public/javascripts/calendar/lang/calendar-en.js and public/javascripts/jstoolbar/lang/jstoolbar-en.js
Updated by Stanislav Pach about 16 years ago
- File calendar-sk.js calendar-sk.js added
- File jstoolbar-sk.js jstoolbar-sk.js added
- File sk.yml sk.yml added
2Tomas
Thanks for your advice - I was confused with selection of a version. Now I know that 0.7.3 was wrong decision ...
2Azamat
I have attached both translated files (calendar-sk.js and jstoolbar-sk.js) as well as updateda main language file (sk.yml). There are still 8 not translated terms - can somebody tell where are used following terms : ?
label_bulk_edit_selected_issues:
setting_autofetch_changesets:
label_commits_per_month:
label_commits_per_author:
label_me:
setting_commit_logs_encoding:
Calendar._TT["ABOUT_TIME"]
Calendar._TT["ABOUT"]Translation into SK language is a little bit tricky. Some terms were translated in connection with context.
Thanks for help.
Updated by Jean-Philippe Lang about 16 years ago
Thanks for your work.
Here is where the strings are used:
- label_bulk_edit_selected_issues: issues bulk edit view title (app/views/issues/bulk_edit.rhtml)
- setting_autofetch_changesets: application settings (repository tab)
- label_commits_per_month: commit statistics (eg: http://www.redmine.org/repositories/stats/redmine)
- label_commits_per_author: same as above
- label_me: issue filter drop down list
- setting_commit_logs_encoding: application settings (repository tab)
- Calendar._TT["ABOUT_TIME"]: calendar popup (click on ?)
- Calendar._TT["ABOUT"]: not used
Updated by Azamat Hackimov about 16 years ago
- Due date set to 2008-11-09
- Status changed from New to Closed
- % Done changed from 90 to 100
Done. Updated sk.yml waiting you, Stanislav.
Updated by Stanislav Pach about 16 years ago
- File calendar-sk.js calendar-sk.js added
- File sk.yml sk.yml added
I have just finished the rest of translation - minority translation bugs should be fixed now. But in calendar-sk.js file there was a serious bug, which caused disfunctional Calendar application - it`s fixed too.
Updated by Stanislav Pach about 16 years ago
Updated string label_me: to better form in sk.yml.
P.S.
How should I proceed when there will any updates of SK translation ? Should I use this thread (Patch #2126)? Please advice me.
Updated by Stanislav Pach about 16 years ago
Updated new string label_example: .
Updated by Stanislav Pach about 16 years ago
- Status changed from Closed to Reopened
Please answer my questions. ThX
Updated by Azamat Hackimov about 16 years ago
- Due date changed from 2008-11-09 to 2008-11-12
- Status changed from Reopened to Closed
Hello again. If bug already opened and someone not closed it yet, you may update this bug with new files. But when bug closed, you should create new one.
I added your last file to svn.