k, now I see. I'm sorry, I thought I had disabled the option in my editor to replace the chars with html equivalents - obviously I haven't. I just committed a fresh copy of welsh.php to the stable branch.
Here's what I did (and a hint to all future translators): all strings in the language file that will later end up in the output as JavaScript alerts are being tagged with
js-alert in the language file - they need to be treated differently than the rest of the translation when it comes to the use of single quotes: instead of only one backslash ("\") that is used to escape the single quote (e.g.
'access_denied' => 'You don\'t have permission to access this page.',
), you have to insert thre backslashes ("\\\") before each single quote, because one of them is used to escape the php single quote, one of them is needed to remain in the code to escape it in the JavaScript output once again, and the third is needed to escape the second one. As an example:
'confirm_delete' => 'Wyt t\'n siwr dy fod eisiau DILEU y categori hwn', //js-alert
in the original file welsh.php that is contained in Owen's contribution has to become
'confirm_delete' => 'Wyt ti\\\'n siwr dy fod eisiau DILEU y categori hwn', //js-alert
. Not doing this will result in JavaScript errors (only visible in IE by default) and of course the JavaScript alerts will not fire up. This used to have a big impact in the past, for example in the french language file, where some translator didn't escape the single quotes in the albmgr.php section of the language file, so users of the french language file were unable to create albums.
Joachim