Talk: I18nEdit

Improvements

Some improvements I thought of whilst using the new editor:

1. Add some documentation to I18n-js to help users access the page and use it.
2. Add breadcrumbs to improve navigation between stages. Mostly done?
3. Add a link to the editor on appropriate .json pages.
4. Warn and tag edits made to the .json pages manually via abusefilter Done.
5. Special:BlankPage/i18nedit:
   1. Remove the legend tag - or make it useful for something. At the moment it appears to do nothing.
   2. Add some padding between the search box and submit button.
   3. Change the submit button text to something else. At the moment it implies that multiple results could be returned when that isn't the case. Perhaps "Submit" would be a better choice?
6. Special:Blankpage/i18nedit/SCRIPT:
   1. Remove/hide the bullet points - the radio buttons serve the same function.
   2. Split the list of languages into multiple columns.
   3. Add buttons to the top and bottom of the list, same as ?action=history does. I wasn't really sure what to do after selecting a language at first as they're so far down the page in some cases.
   4. What should the highlighting referenced in the page be doing? I can't see it used anywhere.
7. Special:Blankpage/i18nedit/SCRIPT/LANG:
   1. Add a cancel button.
   2. Maybe add a supports wikitext column to be managed by the metadata.
8. Special:Blankpage/i18nedit/SCRIPT/metadata:
   1. Again, a cancel button would be good.
   2. Make it more flexible to allow it to be extended in the future (such as marking which messages support wikitext).
   3. Add some padding between the dropdown and the submit button.
   4. Add some kind of feedback so users can tell which messages are already marked as non-translateable.

This is more a TODO list so I don't forget potential features, so feel free to extend it if necessary. I'll try to action some of the above when I can unless objections are raised. cqm 06:56, 3 Aug 2017 (UTC)

More things to add to the TODO list:

1. Quentum suggested batch editing, that is, adding more than 1 translation per edit.
2. Similar to suggested above, add a notice to .json pages that's stored in a custom system message with $1 variable being the script name for easy linking from the notice. It could either be added to /editor.js, or a /notice.js could be created for that purpose (though that would require another import in ImportJS)
3. Not related directly to the script, but there should be some kind of a forum announcement that explains to developers all advantages of using I18n-js library in their scripts. We can't convert old scripts to the new system that fast, but we can certainly make developers aware of it so they can consider using them in their future scripts.
4. Improve general layout of the "search" interface. I'm not sure what I had in mind when initially designing it, but it's a fact that only actually used components of it are the dropdown and the search button. Dropdown could be split into a much more readable list of links, similar to PrefixIndex/AllPages.

-- Cube-shaped garbage can 07:43, August 3, 2017 (UTC)

It would also be fine if: 1. English could be changable to another, closer language. 2. The script could automatically update language list in infoboxes.
~[Quəntumiið the Wise] 14:40, August 3, 2017 (UTC)

I wondered about adding an i18n channel to the wiki discord for general i18n related discussion and to improve awareness there.

Batch editing I'm not that sold on as I don't feel like it's that often that a translator speaks 2+ languages. While not many people make translations, I suspect it's a very narrow slice of those that would need such a thing.

For the search UI, perhaps starting off with a AllPages style list and refine it via the search box?

Linking back to the script (and/or documentation) I feel should be hardcoded to the name of the script to ensure consistency. There aren't many scripts that have a need for multiple i18n pages, so simply forcing convention early on should solve the vast majority of issues. cqm 18:09, 3 Aug 2017 (UTC)

I've added breadcrumbs to most if not all the pages. I also realised there's no monobook support yet for the page titles. cqm 19:27, 3 Aug 2017 (UTC)

Ad http://dev.wikia.com/?diff=59775 possibly demonstrates, we need edit conflict handling too

Add an easy way to get back to the actual documentation page from e.g. https://dev.wikia.com/wiki/Special:BlankPage/I18nEdit/AddFileToArticle and subpages.

Add a pop-up "do you want to leave the page without saving?"

-- Ninjamask (talk) 15:01, July 22, 2018 (UTC)

Another handy addition would be to show an indicator (asterisk maybe?) after the name of languages with an incomplete translation on Special:BlankPage/I18nEdit/ScriptName. A translation would be considered incomplete if it's missing any keys when compared to the English translation.

Also, it'd be nice if keys (on save) were sorted to match the English object's key order. Of course, that's completely aesthetic, but it makes JSON page easier to scan through in my opinion. - OneTwoThreeFall ^talk 07:31, October 9, 2018 (UTC)

One problem with the language

Here is one language that has some code. I'm also attaching an image here where you need to look for it. Can you fix it? DDPAT _talk 22:01, 15 December 2021 (UTC)

That's a no longer supported language, so we can't grab a translation for its name. The solution would be to remove translations to that language from JSON, since they won't work anyways. -- Cube-shaped garbage can 05:47, 16 December 2021 (UTC)

bug: qqq entries are not loaded in the editor.

"qqq" entries are being saved into a sequence-table. They are not being loaded in the editor. Special:Diff/186061 was my attempt at adding the descriptions. Special:Diff/186062 was my second attempt at adding description but only for the "testcases" message. Both times, I had "Do nothing" selected in the dropdown. Additionally, because the qqq is being saved as a list rather than a dictionary, it makes looking at the table much more difficult (especially given that they currently do not load in the editor). --BryghtShadow (talk) 22:53, 29 May 2022 (UTC)
Note: This affects Lua i18n pages. JavaScript i18n pages are not affected. --BryghtShadow (talk) 23:13, 29 May 2022 (UTC)

Fix for this added in r186077. Turns out it was mw.text.jsonEncode limitation: "Empty tables are always encoded as empty arrays ([]), not empty objects ({})." --BryghtShadow (talk) 17:50, 30 May 2022 (UTC)

Feature: Custom message order

This was brought up in the discord #wiki channel, but adding here for paper trail:

1. Add custom order in _metadata.order (QOL for cleaner Lua i18n diffs)
2. Add a way to re-order messages through the UI.

--BryghtShadow (talk) 07:35, 25 August 2022 (UTC)