Talk:Adiutor/Archives/2023-08

i18n and l10n

@Vikipolimer: Your scripts don't have internationalization (i18n) system so they are difficult to update. Can you refactor your code to use standard MediaWiki i18n system (using mw.messages.set() / mw.msg())? As an example of its use check out my script and its localization (l10n) file: ru:Участник:D6194c-1cc/ve.ui.CitoidInspectorWD.js, ru:Участник:D6194c-1cc/ve.ui.CitoidInspectorWD.l10n.json. D6194c-1cc (talk) 17:29, 7 August 2023 (UTC)

Hello, @D6194c-1cc. Currently, we are working on it as it was in our to-do list. Thank you for your valuable feedback. 𝗩𝗶𝗸𝗶𝗽𝗼𝗹𝗶𝗺𝗲𝗿 ℣ 18:10, 7 August 2023 (UTC)

Also separate json files for each language (in oppose to my example, which I will fix soon) will be better, because there is no need to load all the languages. D6194c-1cc (talk) 18:58, 7 August 2023 (UTC)

Also take a look at [1]. I18n is not the same as l10n (and i18 is wrong abbreviation). If you choose wrong file names for localization files, fixing the names will be difficult task after scripts will be used widely. D6194c-1cc (talk) 06:08, 8 August 2023 (UTC)

I found that Gadget-Adiutor.js uses non-localized user namespace ("Kullanıcı"). You can use namespace ids to localize built-in namespaces using wgFormattedNamespaces config parameter, see mw:Manual:Namespace and mw:Manual:Interface/JavaScript#Site-wide. D6194c-1cc (talk) 04:56, 9 August 2023 (UTC)

@Vikipolimer: Also I found some untranslated words among files (in Gadget-Adiutor-CMR.js), but you are added Multilingual interface as capabilities to the description. This way of doing things is wrong, because it is misleading. You need to create separate branch in your project and make all changes there until they will be finished. And then merge them (ideally after testing and review by somebody else). D6194c-1cc (talk) 04:49, 10 August 2023 (UTC)

Hello @D6194c-1cc. Indeed, there are ongoing efforts to translate certain modules. We've taken a two-fold approach by segregating interface translations from the content relevant to our local wiki. Our focus currently revolves around enhancing the fundamental modules, as not all modules utilized in the Turkish Wikipedia seamlessly adapt to other languages. Rest assured, our team is diligently working to deliver the best results. Your expertise could greatly contribute to this endeavor, and we'd be more than happy to seek your assistance. Once module translations reach completion, we'd love to invite you to participate as a beta tester on the Turkish Wikipedia. Your insights would be invaluable. 𝗩𝗶𝗸𝗶𝗽𝗼𝗹𝗶𝗺𝗲𝗿 ℣ 11:49, 10 August 2023 (UTC)

Some GitHub repository issues

You have a typo in you files which is an excess closed bracket ("]") after the license name (you can just modify the commit using git commit --amend command to fix the issue). D6194c-1cc (talk) 19:26, 7 August 2023 (UTC)

Although you still don't have neither the license files nor links to the licenses (for easy access to the licenses). GitHub projects usually have license files, take a look at this guide: [2]. D6194c-1cc (talk) 19:26, 7 August 2023 (UTC)

And as I think it would be better to remove "and attribution" from "Licencing and attribution" (in all the files), attribution means specifying the authors (or a link to the authors list), not just a license. Such a phrase can be misunderstood as specifying the license is enough for attribution (which isn't). D6194c-1cc (talk) 19:26, 7 August 2023 (UTC)

README.md file must have a link to the https://meta.wikimedia.org/wiki/Adiutor page as it contains adaptation manual. D6194c-1cc (talk) 19:26, 7 August 2023 (UTC)

@D6194c-1cc, thanks for your suggestions I will do it as soon as possible. 𝗩𝗶𝗸𝗶𝗽𝗼𝗹𝗶𝗺𝗲𝗿 ℣ 19:29, 7 August 2023 (UTC)

License

CC BY-SA and GFDL aren't the best licenses for the code. CC BY-SA is compatible with Wikipedia Terms of use, but GFDL is useless. Check out commonly used licenses for the extensions and gadgets (en:Wikipedia:Gadget/Repositories). MIT and GTLv3 are the usual choice, but as I think MIT would be more appropriate for JS scripts. Dual-licensing under the MIT and CC BY-SA 4.0 (see also [3]) will be a good decision. As I understand, currently you are the only author, so you can choose any license you like. Choosing the license is the most important step before starting collaborative development. D6194c-1cc (talk) 20:40, 7 August 2023 (UTC)

Although I found contribution of another developer: [4], but I cannot say whether such edits are copyright protected, since reordering by alphabet don't bring any creative content. Changing the license might require asking every author permission. D6194c-1cc (talk) 21:08, 7 August 2023 (UTC)

Could some kind of feature to insert/manage hatnotes be added?

Hatnotes are widely used, yet the templates can be difficult to find and manage. A "insert/edit hatnote(s)" function could help streamline hatnote editing. Thanks, Edward-Woodrow (talk) 22:47, 7 August 2023 (UTC)

Hi @Edward-Woodrow, I've added this feature suggestion to the to-do list. 𝗩𝗶𝗸𝗶𝗽𝗼𝗹𝗶𝗺𝗲𝗿 ℣ 11:52, 10 August 2023 (UTC)

Thanks a lot! Edward-Woodrow (talk) 12:47, 10 August 2023 (UTC)

Contributors vs Developers vs Team

What does Contributors section means? Do it lists those who want to participate? If such then the section title is misleading, because it assumes those who have already participated in the development. D6194c-1cc (talk) 04:54, 10 August 2023 (UTC)

The people in this section are the people who helped me with questions and answers during the development process, only I am the developer. 𝗩𝗶𝗸𝗶𝗽𝗼𝗹𝗶𝗺𝗲𝗿 ℣ 11:51, 10 August 2023 (UTC)

This did mislead me... This tool is a young project, and the advertising may have outweighed the code quality needed for its popularity among more wikis.

Although, I've made some changes (not pushed). I'm waiting for more development activity/plan here and user comments in Chinese Wikipedia. YFdyh000 (talk) 17:02, 10 August 2023 (UTC)