• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

Arthur, could you please give more details on this?


In Edit, the Save button is defined like this:
<input type="submit" class="twikiSubmit" name="action_save" id="save" value='%_{"Save"}%' /><label accesskey="s" for="save"></label>

So the accesskey 's' is coded regardless the translation of 'Save'.

I guess that

<label accesskey="s" for="save">
should be in TWiki.pot as well (and the other button's access keys.


Yes, all accesskeys (not only in Edit and Preview) are hardcoded. Consciously.


  1. it would unwise to give translators the string '<label accesskey="s" for="save">' to translate. Maybe only 'accesskey="s"', but I still think it wouldn' be a good idea.
  2. it would be confuse to write only %_{"s"}% and give people "s" for translation.
  3. if we use codes for acceskeys translations like %_{"_save_accesskey"}%, when the language is English this would be "translated" to "_save_accesskey", because English does not translate things (obviously)

Any suggestions?

AT -- definitely non-monospaced font suck for text editing. wink

Perhaps something like this:
#: templates/edit.pattern.tmpl:xx
# html code: <label accesskey="s" for="save">
# only give the tranlation for the key letter, for example: accesskey='b'
msgid "accesskey='s'"
msgstr "accesskey=''"

because English does not translate things (obviously) there are situations (like this one) it would be easier to use string constants that are always translated, for English as well. So the msgid string would never be used in a user interface.


the way this is done in WindowsLand, is that you specify a letter in the label as the access key

for example, the translator would get the string '&Save' to translate into '&Guardar' (i'm guessing from the es.po), and then when we come to use the po file, we extract the letter after the & - SD

In a GUI application this is much easier. wink

This is being done, but only to underline that letter. putting it inside the <a> would be too invasive and could break in more complicated HTML snippets.


I guess the lack of progress makes this an enhancment -- SD

SVN 7818. -- AC

Summary Access keys in Edit and Preview are not localized
ReportedBy ArthurClemens
SVN Range

AppliesTo Engine

Priority Enhancement
CurrentState Closed

Checkins 7818
Edit | Attach | Watch | Print version | History: r11 < r10 < r9 < r8 < r7 | Backlinks | Raw View |  Raw edit | More topic actions
Topic revision: r11 - 2005-12-08 - ArthurClemens
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback