Talk:Translation Workflow: Difference between revisions

Page contents not supported in other languages.
From KDE UserBase Wiki
(→‎Breakage Policy: moved to LQ)
Line 1: Line 1:
__TOC__
__TOC__
== Breakage Policy ==
If someone for some reason break the translations in GNOME, Fedora, and Debian, this person have to unfuzzy '''all''' the translations that have been done, if the changes are just formatting, better modules composition, or something like this.  Such a policy prevent "mad heads" from changing too much at once.
What do you think about pursuing this policy here? --[[User:Yurchor|Yurchor]] 07:23, 28 June 2010 (CEST)
:Recently a feature was added that allows for minor changes to not be fuzzied. Keeping formatting out of the translatable content will also help a lot here to prevent this. Unfortunately a whole lot of pages were already tagged for translation before there was clarity on proper tagging. See next topic for an update on this. [[User:Siebrand|siebrand]] 10:34, 28 June 2010 (CEST)


== Templates ==
== Templates ==

Revision as of 04:11, 7 July 2010

Templates

Some templates such as {{community-app}} exists in translated versions like {{community-app_da}}. They should be included in the translation units like regular text unless the translation system can somehow be made template aware. --Claus chr 17:22, 28 June 2010 (CEST)

The above remark may be mistaken. At least in some cases the template has been included in the translation unit, only the translation system didn't show its precense (at least not clearly enough for me to notice). However, there is another problem: the {{Community-app-footnote}} template seems allways to be separated form the category lines by a blank line and thus does not belong to any translation unit. The easiest solution would seem to be removing the blank line unless that messes up the display. Otherwise, perhaps we should have a separate translation unit for this template, when it is present? --Claus chr 19:33, 28 June 2010 (CEST)
I modified some pages to include the templates, changes not yet marked for translation. I think this is the reason for your perplexity.--Caig 20:21, 28 June 2010 (CEST)
Are You saying, that templates are treated as part of the regular text and so not excluded from translation? If so, I'll just wait for them to be marked and deal with them then. --Claus chr 22:22, 28 June 2010 (CEST)
Yes. When I translated the Applications/something pages, only one template was included in the translatable text. I added the others, now they seem included in the source, but are not prepared for translation yet.--Caig 10:45, 29 June 2010 (CEST)
Until we get some concensus about the catalogue-like pages, Applications/whatever, I'd suggest that you don't do any more translations. We might mark some versions for translation so that you can see how the markup affects you, but don't do any work on those pages. Actually, if we stick to working on the Welcome page for experiments it should keep things more simple. Once we have concensus I'll apply it to all the catalogue pages then mark them for translation. We're trying to find ways to meet most needs without creating unnecessary work. --annew 12:35, 29 June 2010 (CEST)