[KevinH]

Hi,

As for the "Saved Searches Help" and "Example Searches", those specific menu items are built by reading the search_entries.ini file.

AFAIK ... for those to be auto translatable, there would have to be a separate version for each language since the strings are not literals (ie. need not be constant).

To test this, you could find the "search_entries.ini" file in your Sigil application and hand edit the "Name" entries being careful to not change the / entries that are used to build the menu hierarchy.

Here is a snippet form the top of that file.

[search_entries]
1\Name=Saved Searches Help
1\Find=Right click for menu to add groups or entries.  Edit or re-order any item.  Select a group to run a command for each entry in order.
1\Replace=Right click in Find & Replace text box to load any entry.
2\Name=Example Searches/Join Paragraphs
2\Find="([[:alpha:],])</p>\\s*<p\\b[^>]*>"
2\Replace="\\1 "
3\Name=Example Searches/Remove Non-Breaking Spaces/Empty paragraph
3\Find="(?s)<p\\b[^>]*>(&(nb|em|en|thin)sp;|\\s)*</p>"
3\Replace=
4\Name=Example Searches/Remove Non-Breaking Spaces/Trailing space
4\Find="&(nbsp|#160);(</p>)"
4\Replace=\\2
5\Name=Example Searches/Remove Non-Breaking Spaces/Leading space
5\Find="(<p[^>]*>)&(nbsp|#160);"
5\Replace=\\1
6\Name=Example Searches/Convert Characters to Entities/ensp
6\Find=\x2002
6\Replace="&ensp;"
7\Name=Example Searches/Convert Characters to Entities/emsp
7\Find=\x2003
7\Replace="&emsp;"

If these strings don't change (are simply literals read in from a file), then there is no reason we could not look them up with a tr() function if we could add them to the strings that need to be translated.

Similar issue will probably exist with the clip_entries.ini file contents as well.

I still don't know why the base menu undo, copy, paste, are not translated.

Sorry I can't be more help here but perhaps user_none might be able to let us know for sure.

Take care,

KevinH