On Tue, Nov 01, 2005 at 02:34:55PM +0100, Torsten Marek wrote: > If devel::arch:xyz is included, shouldn't langdevel become devel::lang:xyz as > well, or does it enlarge devel to much? Right now, there are 22 tags in devel, > and 18 languages.
It probably should, but the resulting facet of 22+18=40 tags would be nasty to the interfaces that we currently have (compare how difficult is is to work with the Culture one, and lang would be even more difficult because alphabetical sorting wouldn't help much). For this reason the big merges that would lead to a large number of tags are currently postponed. Luckily, this situation doesn't look like a big problem so far. There could be a difference (albeit thin) between the two facets, though: one answers "what do you do with this?" and the other "in what language do you do it?". Another merge could be putting some things from 'devel' into 'use': use::editing use::devel:debugging use::devel:compiling However, not all of the devel:: tags would fit there (like devel::machinecode or devel::library). > Another, unrelated question: > What about internationalization of tag descriptions? Are there any plans how > to > integrate them? Theorically, it would be easy to do: we can extract a po file out of the vocabulary and give it to people for translating. Then, about using the translations, one could use the tag name (which is invariant) to lookup translated descriptions in the desired language. I have problems however in figuring out how to do it in practice and in code: I admit I don't have much hands-on experience with code i18n. Ciao, Enrico -- GPG key: 1024D/797EBFAB 2000-12-05 Enrico Zini <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
_______________________________________________ Debtags-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debtags-devel
