Project talk:Terminology gadget
Disabled
@Nike: Why did you disable the gadget? —Tacsipacsi (talk) 17:17, 9 April 2023 (UTC)
- It was a mistake. Nike (talk) 09:53, 11 April 2023 (UTC)
Link from terminology.json to Project:Terminology gadget
The message on terminology.json has a link to "Project:Terminology Gadget" (G in upper case) which dosen't exist. Existing page name is "Project:Terminology gadget" (g in lower case). Kokage si (talk) 11:04, 31 May 2023 (UTC)
- @Kokage si: Thanks for the heads-up! It was a mistake in the Japanese translation, which I just fixed. Jon Harald Søby (talk) 13:47, 31 May 2023 (UTC)
Extension
This is super neat! Any plans for turning it into a proper extension? Or at least enabling the gadget for all users? Tgr (talk) 17:02, 9 July 2023 (UTC)
- @Tgr: Thanks! It is already enabled by default for everyone here on TWN. No plans for making it into an extension at the moment, I don't have the time for that any time soon I think (as long as it works as it should here, that's the most important thing I think.) Jon Harald Søby (talk) 21:27, 9 July 2023 (UTC)
- In the Language team we are thinking of bringing glossary support, at least partially, to the Translate extension. No concrete plans yet. Nike (talk) 13:24, 12 July 2023 (UTC)
Categorization
Previously, we used this table for Hungarian. I think there is some value in being able to say which extension a given translation is for. Both because in very rare cases there might be conflicts (e.g. FlaggedRevs uses "editor" in a non-intuitive way) and because it helps with maintainability in general. Tgr (talk) 17:36, 9 July 2023 (UTC)
- @Tgr: Yes, in my initial idea I wanted to be able to specify what "domain" a certain translation is valid for. But that would add a lot of complexity, not only in the gadget code, but also for end users in how they would enter/add terms. So I think it is better to annotate such things in "free-form", e.g. by noting in the usage notes field if a translation is only meant to be for a certain domain. Does that make sense? Jon Harald Søby (talk) 21:30, 9 July 2023 (UTC)
- It's certainly much simpler, so I can understand that choice. In some cases it would be nice to avoid showing bogus/irrelevant annotations. It's probably an uncommon problem though.
- I guess it also depends on how much you expect the tool to be used - e.g. if people start using it for non-Wikimedia software, those definitely need separate dictionaries. Tgr (talk) 22:03, 9 July 2023 (UTC)