Talk:Translate a Page

Jump to: navigation, search


Thread titleRepliesLast modified
Translation Memory514:52, 14 February 2013
Categories215:47, 9 July 2011
open to edit007:43, 6 July 2011
"Click on the Edit tab..."107:02, 13 June 2011
Templates and unbalanced brackets111:00, 2 January 2011
FAQ517:40, 22 September 2010

Translation Memory

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.

Dimkard (talk)11:38, 12 February 2013

Fixed, I think. Please let us know if you have more difficulties with it.

annew (talk)12:52, 13 February 2013

Sorry again, but no TM suggestions are displayed. Having checked 4-5 pages which are "suspect" for suggestions :)

Dimkard (talk)08:50, 14 February 2013

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 ;)

Neverendingo (talk)10:28, 14 February 2013

I am referring to translated strings. E.g. in you can find msgid "==Features==", which has been translated in Nevertheless, there is no suggestion :)

Dimkard (talk)11:51, 14 February 2013

Yes, we understand. However, the translations are stored in a database. If that db is lost or corrupted, it has to be re-built. In this case it has no facility to build from scans of existing translations. It has to learn from your input. Annoying, but necessary, I'm afraid.

annew (talk)14:52, 14 February 2013


The current practice for translating categories is

  • All categories can (should?) be translated.
    • The translated category name must end with /lg, where lg is the usual language code (to avoid accidental clashes with other languages)
    • To ensure, that we translate categories consistently, all the categories we use are listed in a subpage of Translation_Help_Needed
  • There is a category page for all categories in a given language: "Pages in language/lg", where "Pages in language" can (should?) be translated - so fx instead of "Pages in Danish/da" I use "Sider på dansk/da".
    • A category statement with this text should be placed on every translated category page
    • This aggregated category page itself should have the category "Pages" (not translated)

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?

Claus chr20:00, 8 July 2011
Edited by author.
Last edit: 15:47, 9 July 2011

Just translate the section of the category would create a page/ca untranslated. I think the "solution" report a bug (wishlist) over mediawiki software.

Abella20:16, 8 July 2011

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?)

Claus chr20:56, 8 July 2011

open to edit

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.

Zhao Han07:43, 6 July 2011

"Click on the Edit tab..."

In the current theme, the Edit tab is actually a Edit icon.

Zhao Han04:39, 13 June 2011

Fixed, thanks

annew07:02, 13 June 2011

Templates and unbalanced brackets

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.

Claus chr09:08, 2 January 2011

Thanks. I've done just that.

annew11:00, 2 January 2011

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.)

Hans17:53, 21 September 2010

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?

annew07:21, 22 September 2010

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.)

Hans11:21, 22 September 2010

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.

annew12:44, 22 September 2010

OK. How about a short note then? The situation described above actually happened during the Plasma documentation writing.

Hans14:37, 22 September 2010

Next time you see it, show it to me.

annew17:40, 22 September 2010

This page was last modified on 21 September 2010, at 17:53. Content is available under Creative Commons License SA 4.0 unless otherwise noted.