Talk:Category Translation

As you may know we intend to make some important changes to UserBase over the next few months. Language translation is one of the areas that we want to make much easier, so we have been running tests on a sandbox wiki and talking to some of our more prolific translators about problems and solutions.

One aspect that has been brought to our attention is the fact that currently, page names and categories will only appear in English. With regard to page names, Yurchor has done some work on this, and we'll follow that up shortly. First, though, I want to tackle the problem of categories, because I see them as the easy way to guide users into finding other pages of similar interest.

The current system, such as it is, means that you get pages such as Applications, Applications_(de), Applications_(uk), Applications_(zh). This is unsatisfactory on at least two counts - first that we end up with a very cluttered list of categories, making it difficult to find things, and second, even more important, it still depends on the reader recognising the English category name. Even worse, some readers will not be familiar with Latin script. I propose that we use translations of category names. However, we feel that this needs to be controlled, so that consistency is easy.

One way we could do that is to create a table of categories and translations, on this page, for reference by all translators. It would have to be built up over a period, but it means that once one translation of a term has been used, all future category translations will use exactly the same term. If this is felt to be the answer, I'll create a skeleton table for translators to fill as necessary.

I'm willing, too, to listen to any other suggestions. The only criteria is that it should be easy to follow when created, and easy to use while being created. Please post your thoughts here.--annew 17:04, 2 January 2010 (UTC)

It can be useful, surely more useful than English category names, even if, in general in wiki software, I think the bottom position for categories doesn't allow them to express their usefulness totally.--Caig 19:36, 2 January 2010 (UTC)

This should be fine. From a translators point of view it would be straightforward to deal with. It is going to be a large table, though, with all the languages we have. Have You considered making a template table with just one translation - translators could then fill out a copy of that on a separate page for each language. Alternatively there could be a way to show only one translated language at a time - selecting the language from a drop down list or something like this.

One problem we might as well face from the start: Some categories are going to have identical strings in many languages. "Internet" is a good example - it is the same in Danish as in English and probably several other languages using the latin alphabet. I suggest, that we use the same method as with the translated pages, i.e. appending the language code.

The question is: should this be done consistently or only when necessary? The latter might seem best, as the category pages are going to look better without all the appended codes, but I actually favor the former for two reasons. First, not having obligatory language codes will make creating and maintaining the table much more difficult as it is not always obvious which other languages should be checked. Secondly, if two translators choose the same string for their translation of a category, they may not notice the problem straight away. And when the problem is noticed, the category in question may appear on many pages, which means a lot of pages needs to be edited to solve the problem. --Claus chr 08:46, 3 January 2010 (UTC)