Jump to content

New translation interface

You can add &tux=0 as URL parameter, then it should be remembered.

Nemo (talk)13:57, 1 April 2013

Okay, thanks!

\m/etalhead 14:01, 1 April 2013
 

Do be aware that in a few weeks, the old interface will be removed completely.

Siebrand12:34, 2 April 2013

Why? The new interface is completely unusable (white background on everything, messy and etc).

Crt (talk)06:39, 3 April 2013

The new interface was tested with many diverse users, who found it intuitive and nice and said that it makes their translation work more efficient. They reported some issues, which were fixed. So the developers have a good reason to believe that the new interface is better than the old one.

If you have particular comments that can say what exactly is wrong with the new interface, the developers can do something about it. Comments like "disgusting" and "messy" are not helpful.

Amir E. Aharoni (talk)07:30, 3 April 2013

"the developers have a good reason to believe that the new interface is better than the old one." The developers? I really, really don't understand what you are doing (with "you" meaning the WMF). Did you ever considered to ask the community? What they want and need? The community does not care what the developers think. Developers always tend to reinvent the wheel no matter if the old wheel was good enough for everybody that used the wheel (I know this, I'm a developer too). What was the problem with the old interface? Currently the new interface is a total mess. In all browsers. (I tested it with IE 9, Firefox 9 and Opera 12.) Nothing is better in the new interface. Features are removed. Buttons do not work or are misplaced. It wastes insanely huge amounts of space while at the same time important information are hidden in tiny little iframe popups that can't be enlarged. This does not make any sense.

At least keep the old interface. You can't kick the community in the face and force them to switch to a worse tool without asking them. You (the WMF) did this so many times. Didn't you learned something? LiquidThreads? Gone to hell (not here, obviously, but everywhere else). The Article Feedback Tool? The users said "burn it with fire". To bad the translatewiki community is a minority. You will not hear much protest. This does not mean the new stuff is better. It simply means the users stopped to care years ago. And so will I if you ever delete the old, very well working tool. I will not use the new crap. Not as it is.

TMg (talk)23:31, 3 April 2013
 
 

You must be joking. For what reason needs the old interface to be removed? This is insane. Keep it as a fallback if the new interface does not work. You already told me (in the thread above) you will stop to support certain browsers. You must provide a fallback for these users! You can't lock a whole group of users out of contributing to the translatewiki! For what reason? Because their web browser is 2 years old? Again, this is insane.

TMg (talk)20:27, 3 April 2013

I am not joking.

Siebrand23:07, 3 April 2013

You must. The new tool is a pain in the ass. See my other thread above.

TMg (talk)23:31, 3 April 2013

We decided to do it anyway. I understand it's not your wanted course, but it's going to happen. We will not keep on maintaining two editors, and we do require recent browsers and decent screen resolutions.

Siebrand00:05, 4 April 2013

Sorry? Who is "we"? The WMF? What does that mean? Isn't this a community project any more? In which way is a screen with 1024 pixels in height not a "decent screen resolution"? Why do you think you need to maintain two editors? The old editor works. Keep it as long as there is no problem. Simple as that.

TMg (talk)01:03, 4 April 2013

I support the idea of keeping the old editing interface as long as it does not create any problems. I certainly would not recomment to create unnecessary labour - on either side.

Purodha Blissenbach (talk)01:26, 4 April 2013

I do support too the idea of keeping the old translation interface. I have expressed my concerns on this new interface on Meta. I do not know if upgrading the editor is the cause of ruining translations. I leave that here for investigation too.

Dferg (talk)18:15, 15 April 2013

Thanks for the feedback.

Maintaining two editors is out of question. Rather, we want to make the new editor as good as possible with the resources we have. If you encounter concrete issues with the new editor, you can help by reporting those issues.

I feel that the new editor is more intuitive and the user testing we have done confirms that people can easily understand how to use it.

The issue of "ruining translations" is an independent change not related to the new editor.

Nike (talk)09:38, 16 April 2013

Why do you think you need to "maintain two editors"? Simply keep the working editor as it is.

I'm not your beta tester. All I want to do is to edit a few single lines of text. I think that's why we are here. I was able to do this with the working editor. There was nothing wrong. Instead of replacing a working tool with something completely different that is confusing and broken and horribly slow and only works on the most modern high-end computers you should focus on fixing bugs. All the so called "new interface" does is introducing new bugs and removing features. The requirements for the "new interface" are so high that almost all people from smaller and poorer countries are kicked from the project. This is stupid. Insanely stupid. You must provide an interface that works everywhere. For everyone. Even on very old computers.

TMg (talk)14:53, 18 April 2013