| Thread title | Replies | Last modified |
|---|---|---|
| Translation Memory | 5 | 15:52, 14 February 2013 |
| Categories | 2 | 16:47, 9 July 2011 |
| open to edit | 0 | 08:43, 6 July 2011 |
| "Click on the Edit tab..." | 1 | 08:02, 13 June 2011 |
| Templates and unbalanced brackets | 1 | 12:00, 2 January 2011 |
| FAQ | 5 | 18:40, 22 September 2010 |
Some time ago, for several msgids there were suggestions from translation memory (Greek language). Currently, no suggestions are displayed, even if an exact translation exists.
Sorry again, but no TM suggestions are displayed. Having checked 4-5 pages which are "suspect" for suggestions :)
That is to be expected. The translation memory got started with a fresh database, and needs to be filled with data again. So unless you already did translate the suspects somewhere else, you won't see suggestions yet ;)
I am referring to translated strings. E.g. in http://userbase.kde.org/Kdenlive you can find msgid "==Features==", which has been translated in http://userbase.kde.org/KHangMan/el. Nevertheless, there is no suggestion :)
The current practice for translating categories is
The disadvantage of this scheme is, that pages will not show up in the translated category pages until they have been placed there by a translator. It seems like a good idea, that all pages - translated or not - should show up there, but we haven't found a method to do so.
One solution would be for translators to simply translate the category statement on each page - allways the last translation unit. Not an elegant solution, but perhaps workable? Are there any downsides to that?
Just translate the section of the category would create a page/ca untranslated. I think the "solution" report a bug (wishlist) over mediawiki software.
You are right, off course, but it doesn't seem to be very much different from the situation when the translated page doesn't exist at all: In both cases the user will see the original English text. The only difference is that your language will appear in the language selection bar and that the page contains a translated category. How big a difference will this be to ordinary users?
(I am not exactly pleased with this proposal myself - it isn't really a tidy solution, but would anyone notice the difference?)
I suggests this page to be open for editing since UserBase is a wiki site. Collaboration is the sprite of wiki. And this page is supposed to be kept updated by contributions from other contributors/translators. And I have some improvement on this page in mind.
I think we should add something about translating templates and the problems with unbalanced brackets in the Hints and Tips section. I have a suggestion here: User:Claus_chr/Translation. What do you think. It should be possible to simply paste the content in.
I think a common question is, "It says the translation is outdated but why can't I translate it?". I'm thinking about adding this to a FAQ section.
(This is mostly a note to myself, but if someone has time to do it before me - go ahead if you want.)
I don't understand this question. If the system says something is outdated it knows there is an update marked for translation, so why would you not be able to translate it?
I probably remember it wrong then. The situation is as follows: Person A has written a page and marked it for translation, Person B translates it. Now Person A adds some text, but Person B can't translate the new text, because the new version hasn't been marked for translation yet.
So the "It says the translation is outdated" part is probably not correct, the question is why a translator sometimes can't update a translation. (A: The new version hasn't been marked for translation.)
I think you are mistaken. As far as I know the translators only see messages that refer to the version already marked for translation. It's possible to have a development version of a page for some time that does not get marked for translation until the author clears it. In that case the translator sees nothing about it.
OK. How about a short note then? The situation described above actually happened during the Plasma documentation writing.
KDE UserBase Wiki 