On Thu, Jul 14, 2011 at 9:22 AM, Jason Etheridge <[email protected]> wrote: > Hi Linda, > >> Is there a way to make (customized) textual descriptions of MARC fields >> visible - instead of the usual tags? > > It'd take some programming however you slice it. > >> If one opens the staff client, chooses an item from the menu and then the >> subitem, in some cases some letters are underlined and that letters (in each >> case a single letter) are a part of the shortcut key. My questions is this - >> how are these letters chosen? As we use both the native English and the >> translated Czech version of the staff client, this would be a very useful >> piece of information for us... > > They're not chosen programmatically, but by hand. > > So for example, we have a file containing "entities" like this: > > <!ENTITY staff.cat.opac.menu.accesskey "A"> > <!ENTITY staff.cat.opac.menu.label "Actions for this Record"> > > And the label is what gets displayed, and the accesskey is what gets > underlined. These are defined initially in English, and then > translated. There are a few principles that we (or maybe I) try to > adhere to when choosing the accesskey, but they're not explicit, and > we're not consistent. I have no idea what translators do and whether > they test their choices for usability. :(
Translators don't see the separate ENTITY definitions; the translate-toolkit translation tools combine those into a single string in the POT/PO files with an ampersand (&) marker for the access key and that's what is presented to the translator. So the English string is: &Actions for this Record And the current Czech translation is: &Akce pro tento záznam In each case, the access key will be "A".
