AVID:Requests for Comment/Remove Translations feature: Difference between revisions
closing |
m added Category:Passed Requests for Comment using HotCat |
||
| Line 36: | Line 36: | ||
[[Category:Requests for Comment]] |
[[Category:Requests for Comment]] |
||
[[Category:Passed Requests for Comment]] |
|||
Latest revision as of 08:28, 28 February 2023
- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.
In 2021, a Translation feature was implemented onto the wiki. Fast-forward, we are nearing 2023, and this feature has remained underutilized on the wiki. Users who supported the original proposal argue that it clogged up the search engine, and that updating articles with translation became complicated due to having to remark the page.
This was originally proposed by User:SuperMax124 in the AVID Forums page.
ifyoudarethenpizzait aka Compooper (talk) 15:19, 2 November 2022 (UTC)
Support
Support What Compooper said CalvinWilkerson (talk) 15:28, 2 November 2022 (UTC)- Support Read my reasoning for further details, but to keep it brief, it makes both navigation and updating the article difficult. Also, as SuperMax said, I think they should be phased out entirely since they have been underutilized and badly executed. Camenati (talk) 15:32, 2 November 2022 (UTC)
Support in the entire face of the galaxy all they do is clutter up the search and give that stupid "you are editing a translated page" banner. I hope we rid this one for good CharlieFiddlesticks (talk) 19:30, 2 November 2022 (UTC)
Support As the one who originally started translations, maybe it was simply a case of "too soon". If we had a larger contingent of multilingual editors to work on these then the wonkiness of the extension might well be worth putting up with, but when I looked at the translation stats, we had a grand total of 2 editors working on translations this month. That's nowhere near enough to justify continuing with this. Perhaps one day if we have a bigger contingent of willing translators we could try again, but for now, I must reluctantly support this proposal. 
Talk · Edits 22:39, 2 November 2022 (UTC)
Support It not only clutters the search engine, but you need to append "{{#translation:}}" to every category you add, otherwise the categories will get cluttered with those "/en" pages. It sounds good as an idea but making it work is way too complicated. Also it makes visual editing impossible for some pages since translatable pages are not compatible with the visual editor. Besides translation services have improved so much in the past years like Google Translate etc. Logohub (talk) 11:47, 5 November 2022 (UTC)
Support What Compooper said. 
· Talk · Edits 13:06, 5 November 2022 (UTC)
Support Need I say more? AlmightyKingPrawn (talk) 03:54, 6 November 2022 (UTC)
Support At first, translations were a brilliant idea. In fact, I was excited for reading the wiki in Spanish (my mother tongue) someday. But I'm starting to realize that this option wasn't necessary at all, I can understand the articles, for doing this you simply can translate it for your own, that's it. Other thing is that the way for translating a page is really hard. User:Luli Logo (User talk:Luli Logo) 20:15, 6 November 2022 (UTC)
Support The translation extension is annoying, and given the low use rate, I don't see a point in using it. Maybe a new wiki for other languages would be better. For now, it's basically pointless. Blad (talk) 14:51, 7 November 2022 (UTC)
