From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search

Cannot save the translation[edit]

I just finished translating into greek (el) but strange things happened! Nothing shows up @ Recent changes but looking my contributions, it seems that the translations were saved at no normal titles:

Also no link to Greek was created. —Ah3kal (talk) 14:10, 11 October 2019 (UTC)

There's a very annoying bug we're dealing with right now: phab:T235027. Until that's been fixed, there's a simple workaround: one can edit the existing translation (e.g. just add a space to the first item, like I did) and it'll turn up. I'll add more information about this, and I've kept an eye on translations to fix this. /Johan (WMF) (talk) 14:18, 11 October 2019 (UTC)
For the time being, I've added some information to the documentation that shows up when translating. /Johan (WMF) (talk) 14:20, 11 October 2019 (UTC)
Thank you Johan (WMF). I'll stay in touch.—Ah3kal (talk) 14:22, 11 October 2019 (UTC)
You can add the space and then remove it (so you press Space then Backspace), this lets you press the Save button. Frigory (talk) 17:31, 11 October 2019 (UTC)

‘Supporting IE 6 and 7 made the wikis less secure for everyone else’[edit]

This sentence is a dangerous shortcut. Usually we talk about ‘security’ to think about the technical limitations of a written process. But here, there are no technical limitations: you can have a secure version of the wikis for modern browsers, and another version specific for IE 6 and 7, which could be secured if your developers are very skilled in dealing with these very old browsers.

Therefore I understand that this sentence is telling the difficulty for the developers to continue to support IE 6 and 7. For such a thing, we don’t say ‘security’, we say ‘economic cost’. Keep in mind that maintaining the support for these old and forgotten browsers is tiring for the developers, so this tiredness causes less security. But security is not the first consequence, the first consequence is the tiredness. According to usual economic theories, you can fight against tiredness by employing more people, so that you will have many employees to deal with everything efficiently. So ‘tiredness’ (which is quite a familiar and indecent word) is assimilable to ‘economic cost’. This is why it would be more appropriate to say ‘economic cost’ instead of ‘security’.

To stay a bit close to the original, I’ve decided to include both terms in my translation, so I’ve written: ‘Supporting the old browsers couldn’t go with securing the way that wikis work without involving a high economic cost.’

I also decided to change ‘securing the wikis’ to ‘securing the ways that wikis work’, because the first expression is very, very abstract! If I understand correctly, the security problem is that, since you claim you’re supporting a certain browser, then users of this browser can expect using the wikis will give coherent, logical results. But if the results are not as expected, then people will contact the ‘security support’ to say ‘hey, it doesn’t work’ and this will be your fault. But usually, we say ’security’ to talk about background problems that the normal people don’t care about. But here, we care much about these problems, because it affects the result of our work! So I hope my expression gives more this feeling.

Frigory (talk) 00:22, 12 October 2019 (UTC)

Security is the only one problem for users and security means internet security (https, privacy etc.). --Wargo (talk) 08:50, 12 October 2019 (UTC)