Viewing a history listing
|22:01, 13 July 2012||Nemo bis|
|06:59, 21 September 2010||Waldyrious||(Reply to group-specific doc)|
|06:49, 21 September 2010||Waldyrious||(Reply to group-specific doc)|
|20:23, 20 September 2010||McDutchie||(Reply to group-specific doc)|
|15:51, 20 September 2010||Siebrand||(Reply to group-specific doc)|
|15:19, 20 September 2010||Waldyrious||(Reply to group-specific doc)|
|11:38, 20 September 2010||Siebrand||(Reply to group-specific doc)|
|08:55, 20 September 2010||Waldyrious|
Would it be possible to have group-specific documentation? For example, words like "badge" or "template" can be translated in several ways in Portuguese, and this creates problems of consistency; especially when different message groups mean it in different ways. I was wondering if a page like Mediawiki:GroupName/pt (or maybe Mediawiki:GroupName/qqq/pt) could be made to show up among the translation helpers (translation memory, etc) for all messages from that group. Are these changes feasible/desirable?
What you're basically asking for is a localised product based terminology respository. Or maybe it should only be product based if so indicated explicitely. We have no idea yet how to implement such a thing, or what it should be doing exactly. For now my advise is to create these manually as a subpage of your language portal, and refer from there.
Yes, indeed, it would be sort of a dictionary, albeit a very brief one --a cheatsheet, if you will--, containing only the core terms for the message group, so that it would fit into 2 or 3 lines of text. Then it could be embedded the same way the qqq files are right now. The idea is for it to work quite similarly to the current scheme of /qqq subpages. The pattern to look for would be slightly different, but the rest of the current implementation could be reused (I suppose). Or are there other obstacles I'm overlooking?
(As for your statement "it should only be product based if so indicated explicitely", yes, that would make sense if we were talking about a large dictionary, but the idea here is about very short lists of terms used by that specific product, and therefore tailored to it, which would make them not exactly reusable.)
A few remarks: "quick and small hacks" tend to turn into unworkable long term solutions. manually implementing this in qqq is not the way to go. There needs to be some process that will match words in the source message to defined terminology and translations so that everything works automagically.
I agree with the quick hacks thing, but I wasn't suggesting to manually(?) append these cheatsheets to the qqq messages, but rather to replicate that mechanism, with some changes in the pattern it uses to fetch the pages to transclude. This in principle addresses your concern about quick hacks -- unless the qqq thing is itself considered a quick hack. But if so, even though one wrong (is it?) does not justify another, I gotta say, while what you're talking about makes perfect sense and would be awesome, it seems like something that would take a while to be implemented (if ever). And on the meantime, maintaining consistency across translations stays a cumbersome task...
Thanks for the suggestion. We actually did that, some time ago, but it was chronically incomplete, and not very usable, because (1) we'd have to have the page open in a separate tab while translating and move forwards and backwards and (2) some terms would have to be translated differently depending on the message group.