You can put the & in front of any letter in the menu as long as that letter is unique for the entire menu (e.g. K is fine if no other word in the File menu has an & before the K). Most people use the keyboard shortcuts anyway, but its nice to have the menu letter shortcuts available too.

Thanks for your answer, meme. So I'll try to do some translations for the main window today.

Up to yesterday I completed a lot other areas and update the file at Transiflex. For user who want to take a first look on it can download the attached file and copy it in the translation folder (don’t forget to save the original file). It's completed up to 61%.

Well from http://www.loc.gov/standards/iso639-...glish_list.php we're using the 639-1 code if it exists, and if not then the 639-2 code. So "ne" is "Nepali" (with "nep" the 639-2 code) and "new" is "Nepal Bhasa" and "Newari". Until someone actually using the code comments that a different code is needed, I think we'll leave it as is for now

Think of the Dublin Core as a challenge

You should have more time now as I think it will be frozen imminently for 0.6.0 and the next updates won't be seen until 0.6.1.

I just recognize that unfortunately an international keyboard layout seems to be not supported in Sigil. That's the problem with language and translations. Surprises came up where you do not expect it.

Your point is correct and I think I need to change this back to Ctrl as long as there is no difference of international keyboard layouts in Sigil. By the way you are the first one who have recognize (ore let me say use) this. I had made the change some when mid October.

Thanks for your comment.

@User_none and meme
I will change this back but it is a problem for translation and documentation. People who a working with IT will have no problem to understand that [Ctrl] is the same as [Strg] but there is still the point that this key do not exist in a keyboard layout for Germany and Austria. As this isn't a common standard for these countries. My guess is to describe this in the documentation and may be in the shortcut editor window. Then there is no misunderstanding.
When I look into other programs like MS Windows, MS Office, Adobe products etc. this key will be translated and used as [Strg]. This is common standard. Maybe this is something you can implement some when in the future.

I did an update at Transiflex. Here is the update german language file. Replace file sigil_de.qm in subdirectory of Silgil translation files ( ...\Sigil\translations\) restart Sigil and reset the shortcuts in preferences.

What? Is the code to actually process the shortcuts using the translated strings? If that's the case, I think it's a bug (or a misfeature).

If the translation system is currently intended to allow adapting shortcuts for different languages, then I suggest adding strings for the different key names, so the code can compare the shortcut strings with them, and set the right shortcut.

(I've been using "May˙s" as a translation for "Shift" in the Spanish translation, and that's what non-computer-savvy people are most likely to understand.)

There appears to be an option notr for no translation for strings that probably should be used in the ui files for all the shortcut strings. It was being used mistakenly for the heading formats - which is good because now I know what to change for the shortcuts