View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013860 | Scribus | Translation | public | 2016-03-28 08:28 | 2016-11-04 00:17 |
| Reporter | bubu | Assigned To | Kunda | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.5.2.svn | ||||
| Summary | 0013860: translation dependence from Qt project | ||||
| Description | There is an undocumented translation dependence from Qt project. See this issue: 0013107. A) Please document this feature for other translators: https://wiki.scribus.net/canvas/Official:Translation_Howto B) Or please remove this dependency. _I think, it's a bad strategy_. We have 7000+ strings in Scribus translation files, and we reuse from an other project only cca. <10 strings. For these <10 strings translators must learn Qt project translation workflow and get access for this project. It would be much easier to include all necessary strings to Scribus translation project. | ||||
| Tags | No tags attached. | ||||
| Patch | No | ||||
|
|
>> It would be much easier to include all necessary strings to Scribus translation project. Not so easy. Those strings are dependent on desktop environment. That's why we never use them directly in our code. We just pass appropriate flags to Qt message box. There is other stuff handled by Qt message boxes which also depend on desktop environment like the order of buttons, another thing we prefer not to handle ourselves. If Qt project were to update those strings and if we were to import those strings in Scribus, you would get no notification and you would have: 1) to update those strings in Scribus code yourself for all desktop environments supported by Qt 2) update ts files by running lupdate 3) translate those strings 1) is probably a burden we prefer to avoid. |
|
|
Thanks, Jean. In this case, I think, it would be good to document this Qt translation dependency. |
|
|
bubu, we can work on documenting this. |
|
|
Kunda, let's do it! |
|
|
bubu, lets start the proposal at https://wiki.scribus.net/canvas/Official_talk:Translation_Howto |
|
|
Thanks Kunda. You can see my proposal on the wiki. |
|
|
Kunda, ping. |
|
|
Kunda, can you finish this issue? The Hungarian team just makes the translation of Qt here: https://www.transifex.com/qt-hu/public/ |
|
|
@bubu starting at http://lists.qt-project.org/mailman/listinfo/localization and announcing intentions to volunteer makes sense. What do you think ? |
|
|
@bubu apologies, seems like you've already announced it on there |
|
|
@Kunda, thanks. Can you review my proposal (https://wiki.scribus.net/canvas/Official_talk:Translation_Howto) and finish this issue? |
|
|
'finish this issue' entails: 1) Filling the rest of the info for how to use Transifex 2) State the intention of Transifex and the option to use (some don't) 3) Screenshots of the process 4) Guidelines for Language Coordinators 5) Guidelines for Language Translators 6) editing the current official translation document |
|
|
Noting https://wiki.scribus.net/canvas/Translation_workflow to be added to the wiki page |
|
|
@Kunda, we are talking about the same thing? I think, this issue is about missing Qt translations. We need only to document in Scribus wiki: 1. there are translation dependence from Qt project, 2. and how to start with this task. Please, see referenced issue 0013107. Qt project doesn't support Transifex for his translation workflow. I do not understand your previous comment about Transifex related task list. This issue is not about Transifex. |
|
|
Yea.. we're talking about the same thing. Check my revision. |
|
|
Excellent, I accept! Thanks. (Hm... Kunda = luzpaz?) |
|
|
+1 aka luzpaz :) Updated wiki page. Closing issue |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-03-28 08:28 | bubu | New Issue | |
| 2016-03-28 09:33 | jghali | Note Added: 0039466 | |
| 2016-03-28 09:47 | bubu | Note Added: 0039467 | |
| 2016-03-28 09:52 | jghali | Note Edited: 0039466 | |
| 2016-03-30 19:07 | Kunda | Note Added: 0039557 | |
| 2016-04-02 12:28 | bubu | Note Added: 0039695 | |
| 2016-04-02 13:22 | Kunda | Note Added: 0039706 | |
| 2016-04-02 13:23 | Kunda | Assigned To | => Kunda |
| 2016-04-02 13:23 | Kunda | Status | new => assigned |
| 2016-04-02 15:42 | bubu | Note Added: 0039714 | |
| 2016-04-18 16:02 | bubu | Note Added: 0040277 | |
| 2016-08-06 14:40 | bubu | Note Added: 0041897 | |
| 2016-11-01 16:56 | Kunda | Note Added: 0042283 | |
| 2016-11-01 17:00 | Kunda | Note Added: 0042284 | |
| 2016-11-01 17:11 | bubu | Note Added: 0042285 | |
| 2016-11-02 12:49 | Kunda | Note Added: 0042288 | |
| 2016-11-02 13:00 | Kunda | Note Added: 0042289 | |
| 2016-11-02 13:53 | bubu | Note Added: 0042290 | |
| 2016-11-02 20:35 | Kunda | Note Added: 0042295 | |
| 2016-11-02 20:44 | bubu | Note Added: 0042297 | |
| 2016-11-02 21:02 | Kunda | Status | assigned => closed |
| 2016-11-02 21:02 | Kunda | Resolution | open => fixed |
| 2016-11-02 21:02 | Kunda | Note Added: 0042299 | |
| 2016-11-04 00:17 | Kunda | Relationship added | parent of 0013107 |
