Bug 13187 - Access keys should be localizable/translatable
Summary: Access keys should be localizable/translatable
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: I18N/L10N (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-03 07:15 UTC by paxed
Modified: 2020-02-21 11:10 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description paxed 2014-11-03 07:15:42 UTC
For example:

cancelorder.tt:          <input type="submit" class="approve" value="Yes, cancel" accesskey="y" />
cancelorder.tt:          <input type="submit" class="deny" value="No, don't cancel" accesskey="n" onclick="window.location='[% referrer %]';return false;" />

After translating the buttons, the access keys do not reflect the button texts.
Comment 1 paxed 2020-02-21 11:10:29 UTC
These could be done with the i18n template plugin, eg.

<button type="submit" class="approve" accesskey="y"><i class="fa fa-fw fa-check"></i> Yes, close (Y)</button>

would become something like

<button type="submit" class="approve" accesskey="[% tp("accesskey for 'Yes, close'", "y") %]"><i class="fa fa-fw fa-check"></i> Yes, close</button>