Thu, Nov 16
Mon, Nov 13
Aug 3 2023
Jun 5 2023
I was led into this task by this conversation. As you'll find explained in details in the link, this adds an increased degree of difficulty to what was already a very confusing experience for new users.
Jun 1 2023
A less strict threshold is considered for paragraphs that a user marks as resolved—taken as a signal that the user reviewed and confirmed the status of the translation. For paragraphs where the unmodified content warning is shown, but the user marks it as resolved, a less strict threshold is applied (accepting 95% of Machine translation or 75% of source content). This will provide a way to accommodate cases where the automatic translation was exceptionally good, but still avoid potential abuse of the feature (i.e., not blindly following a user's confirmation).
The percentage of user modifications is also measured for each paragraph. A paragraph is considered problematic when it contains more than 85% of the initial machine translation (or, when copying the contents from the source document, it contains more than 60% of unmodified content).
@KartikMistry, yes, I was seeing that now while working on the code (why I wrote that my patch may be wrong). This was rather unexpected as I was told from some manual tests that my community performed that the default threshold was 85%. Do you think it would be a meaningful change if we set it to 97%? Or maybe we should aim even higher?
Trying to help, based on past similar tickets, I've already created a patch for this (which may as well be wrong).
Apr 15 2023
@Jdlrobson, is my patch the right way to fix this?
Dec 22 2022
Dec 21 2022
Dec 19 2022
Dec 16 2022
Dec 10 2022
Sep 16 2022
Sep 15 2022
Aug 16 2022
Aug 7 2022
Jul 12 2022
Jun 20 2022
Jun 8 2022
I would like to add that the kind of collapsing/expanding I suggested differs with the overall idea explained here. The system I suggest deals with marking topics as resolved or open (which would coincide with their states as collapsed or expanded) not with the readability preference of how one might want to have the talk page topics presented to it. If anything, I'm not very fond of having to interact with collapsed topics (in my suggestion, collapsed topics would be resolved, already "semi-archived", and one would generally have no reason to interact with them). That already happens in the mobile version and it makes following reply emails hard for me.
Jun 6 2022
Jun 3 2022
In regard to typo fixing personally I can see changing the timestamp as being equal to "this comment was edited". Generally speaking, I'm not too fond of heavy notices that tell that so a "time confusion" would be a subtle enough clue that comment editing had happened. Indentation would preserve the logical flow of the conversation.
Regarding the whole signature discussion... I believe the importance of the timestamp must be stressed. If one comment changes, there's no logical sense to keep the old timestamp. Keeping that in mind, maybe the signature should be removed automatically altogether and re-introduced in the new version of the comment every time an edit happens.
May 22 2022
May 21 2022
May 15 2022
Prepared the patch. Feel free to abandon if not necessary.
May 10 2022
May 9 2022
May 7 2022
Can someone add this link in the list of typos above, assign it to me and mark it as pending? It's one of the most common typos apparently and I've already fixed the majority of them. I'm scared of tables.
May 6 2022
May 4 2022
May 3 2022
@thiemowmde, would it be possible explaining to me why exactly do we need the regex \.js$ as a filepath filter? Why are we only looking at the js pages? Are those the only ones which should be corrected?
Is there any way to exclude searches from some file path patterns using the CodeSearch tool?
May 2 2022
I hate, hate tables. I was trying to add some patch-links and ended up butchering the whole table. Tried fixing it twice but failed. Afraid to annoy everyone with extra emails by my experiments, I'm leaving it like that for someone more experienced than me to fix it. I'm sorry.
May 1 2022
Apr 29 2022
Apr 20 2022
Allowing the first comment that starts the discussion (what comes immediately after the title of the section), the so called "post" or "topic" or "question", stand aside in a way (maybe by highlighting it) would also help in navigating threads and ease participation in them. This would also formalize the discussion elements better: Post, comments and replies (and replies of replies in multi-level subthreads) by making it easier to see which is which and subsequently making it easier for you to choose how to participate in that discussion.
Keeping up with the collapsing/expanding part, if discussions could have the ability to be marked as resolved, maybe they could get fully hidden once they were marked like that. This would make help seeking pages appear less crowded I believe.
Beside thread collapsing/expanding, (and maybe comment/reply counting) being able to provide summaries might also be a good thing to consider. I was inspired by this long discussion to start the thread at MediaWiki and in it I've had to do the summary approach in a subsection manner. (See in bottom.) This may be also useful in closing remarks in RFCs.
Apr 11 2022
Apr 4 2022
No, it probably wouldn’t. Summaries are used at a lot of places, and lifting a 18-year-old restriction (7c1b75d, although Phabricator refuses to show the diff for the interesting part, Skin.php, probably just because the author is written as Erik M�ller instead of Erik Möller) needs much more discussion than just this ticket. Exactly because edit summaries can’t be edited afterwards, letting users use various formatting would make it possible to create a hard-to-read edit histories (colors, font sizes, maybe even images) without a way to moderate them except for the total removal.
Mar 23 2022
@Jdlrobson, sorry for the noobish question but can you tell me what's the file's path that should be edited in the said extension? I'd like to help but I'm still not that versatile in these details. This seemed like a pretty straightforward job and I thought it could help me build more self-trust if I could get it done.
Mar 19 2022
Mar 18 2022
Mar 16 2022
Maybe, instead of Special:MassMessage, Special:CreateMassMessageList can be considered as the targeted special page for the change to happen.
Feb 8 2022
Feb 7 2022
Jan 31 2022
I believe that's coming because the https://translatewiki.net/wiki/MediaWiki:Translate-manage-import-ignore page doesn't exist yet. Someone with the needed privilege should create it with this text:
Jan 30 2022
Jan 28 2022
@Tgr, take a look at this short discussion which led to the creation of the task. Apparently I had erroneously believed that you got specific emails from being replied to and from getting messages from threads you were subscribed + watchlist emails (which would make the total emails received from 1 action 3). This explains why in the original task I mentioned "Echo" and "bundling". Then I changed from 3 to 2 when I saw that reply notifications and comments on subscripted threads were actually already bundled. Please do check the aforementioned discussion as that would make everything clear and I don't want to make the thread any longer here by replicating the conversation.
Jan 27 2022
Jan 25 2022
Jan 11 2022
General comment: At my community (SqWiki) in many edit-a-thons that we've held, the phrase "edit it normally, like you're using Microsoft Word" gets tossed around a lot by mentors and mentees when describing VE. It is generally considered a very beneficial thing that when you're editing, the overall page layout doesn't change and you can view your changes in real time, like they'd appear when "printed". I think that whatever route is chosen to be followed on this (I do think we need ways to distinguish between the two modes) we should be careful to preserve that characteristic as much as possible.
Dec 9 2021
@Rjwilmsi, yes. I was thinking about newlines as the delimiter/separator. If we have 5 entries in 5 individual lines and try to have them pasted in normal settings, they get squeezed in 1 cell. Instead the initial format should be preserved and each line should be able to get automatically aligned in different individual cells, thus having them spread in 5 different cells.
Nov 19 2021
Oct 24 2021
Oct 20 2021
Oct 15 2021
Our CS1 redundant parameters in SqWiki went from almost 0 to 3k articles in around a week.
This link that was given to me some days ago by another user shows that there are more than 1k results only with the archive[-]url problem. And this is only for SqWiki that has less that 100k articles in total.