Topic on Talk:Content translation

The bugs are too much

13
Bageense (talkcontribs)

Not only did my automatic translation from English to Portuguese not work, but it also failed to publish, and I'll have to do everything manually. Sorry, but I've had enough.

HaussmannSaintLazare (talkcontribs)

02:26, 10 May 2020 (UTC)

Hello Bageense !!!

Judging from my experience,

Amire80 has only contacted Wikimedia Phablicator and is not trying to fix the problem himself (Amire80 is a man).

And the members of Wikimedia Phablicator don't seem to be very interested in eliminating the bug of content translation.

Therefore, it is better to think of this page as a page for users to consult themself rather than a page for reporting a beta version.

Thank you !!!

--HaussmannSaintLazare (talk) 02:26, 10 May 2020 (UTC)

AKlapper (WMF) (talkcontribs)

@HaussmannSaintLazare It would be great if you stopped throwing random names (like Amire80) for no good reasons into conversations, as that is just to confuse other people.

YTRK (talkcontribs)

Automatic translation IS NOT the purpose of the Content Translation tool. It is the translators' (you and I) job to do the actual translation and the automatic translations are only there to assist you, as a starting point for translations.


@HaussmannSaintLazare Your comment is downright rude towards the developers on Phablicator. What is more, while you don't seem to realize, this particular case is not a bug. It is the filter doing it's job properly. I've already said it to you on Topic:Vkspd0bcx3a6nf9r, you must not rely completely on automatic translations.

"an unedited machine translation, left as a Wikipedia article, is worse than nothing" -en:WP:MACHINETRANSLATION

HaussmannSaintLazare (talkcontribs)

07:34, 11 May 2020 (UTC)

Hello YTRK !!!

YTRK wrote "Your comment is downright rude towards the developers on Phablicator."

However, this message is inappropriate.

I did not blame Wikimedia Phablicator members.

I only wrote the situation objectively.

In the first place, the members of Wikimedia Phablicator develop their programs with their own interests.

Even the developers of Content translation haven't participated in programming to eliminate bugs.

So it's no wonder other members don't.

Also, YTRK is missing in another point.

YTRK writes " It is the filter doing it's job properly. "

As I reported before, there is an anomaly that the filter works on a target that should not work.

Perhaps this is a content translation issue.

Perhaps, fortunately, YTRK may have never experienced this phenomenon.

However, it is inappropriate to treat the experience of others lightly.

Thank you !!!

--HaussmannSaintLazare (talk) 07:34, 11 May 2020 (UTC)

YTRK (talkcontribs)

"Amire80 has only contacted...", "...the members of Wikimedia Phablicator don't seem to be very interested...", and what about your comment here, "Amire80 cannot say that Amire80 is fulfilling his responsibility as a product manager simply by..."?

The developers are volunteers, and they aren't "not interested", they have too much bugs to fix that they can't cope enough. Sure, you haven't written "it's the developers' fault", but you're being offensive all the same.


Bageense writes that the "automatic translation" did not work and that it failed to publish. He/she also moans having to "do everything manually". Given the number of people who misunderstand what this tool is (that may perhaps include you), it is likely that this is another such case. If so, it is indeed the filter doing its job, to prevent unmodified content from being published.


I am aware that the filters sometimes misbehave, but from what is written in the initial comment, it is probably not the case here. Nor is it the case for you, presumably.

Also, you've used the word "inappropriate" twice in your comment towards me, but your initial comment towards Bageense was nothing but "inappropriate". What did it do to help him/her?

Bageense (talkcontribs)

Isn't the automatic translation is supposed to be a place to start? I never intented to publish an unmodified translation. I was complaining about the fact that, when I clicked on the right column, only the original text was pasted. Not only that, but when I finished writing everything manually, the translation wouldn't be published, not even in my sandbox.


I was a bit angry when I started this discussion, but I don't regret that entirely. I've been trying to use this tool for three years. It has in fact worked a few times, but its unstabe nature makes it not worth it in the end. If after all this time the tool still doesn't work properly, I think my complaint is justififed. The tool had its chance.

Trib.to.kreeh (talkcontribs)

I'm having the same issue, it's really annoying. Also, when I'm able to publish the references are all messed up.

YTRK (talkcontribs)

About the references, could you give more information on how it's messed up? Could this be related?

Trib.to.kreeh (talkcontribs)

Here are two examples


I think what is happening is that the tool does not translate the reference parameters, such as author, title, etc.

Trib.to.kreeh (talkcontribs)

I'm having some other issues, the main being:


Abuse filters keep blocking paragraphs in every article in ways that seem too random

I'm unable to type some accents that exist in my language, so I have to copy and paste the letters from somewhere else (examples: ó,á,ê)

YTRK (talkcontribs)

@Trib.to.kreeh It looks like the references were all gathered at the end instead of in the sentences. I've fixed the first one.

Did you by any chance translate the reference list as well? That might be the cause.


As for the abuse filters, what kind of filters are they?

Also, are you able to type the accents on visual editor? Content translation is based on that so it might have its roots there.

YTRK (talkcontribs)

Yes indeed. Apologies for my mistake. I'd (perhaps mistakingly) become accustomed to people not understanding the nature of the tool.

That problem does seem rather serious. Whether to copy the original text or use an automatic translation service can be changed on the very right section, around the same place you get the error messages, but you probably know that already and it's unlikely that's the case since the default seems to be google translations in the first place. Hmm...

Sorry again for the misunderstanding.

Reply to "The bugs are too much"