Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

"Add to bookmarks" changed to Ctrl+Π. How can I change it?

  • 9 replies
  • 5 have this problem
  • 2 views
  • Last reply by Tonnes

more options

"Add to bookmarks" shortcut changed from Ctrl+D to Ctrl+Π. Why is that happening and how can I change it? (Firefox's language is Greek) This happened after the last update to version 56. Thank you.

"Add to bookmarks" shortcut changed from Ctrl+D to Ctrl+Π. Why is that happening and how can I change it? (Firefox's language is Greek) This happened after the last update to version 56. Thank you.

Chosen solution

The command / shortcut key seems to have been modified by one of the Greek localizers back in July and hence for 56 - see here.

I suggest you email one of them (see the top of that page - the first person is the one who made the change) and ask him to modify this and check other command keys as soon as possible, and also uplift that for 57. If you want, I can also send him a message.

I’m afraid the change will not be included for any 56.0.x release, but you should be able to modify it yourself by opening the omni.ja file in your Firefox program folder’s browser subfolder. (Not the program folder itself which contains a file named similar.) Copy that original file elsewhere, create a copy of it, rename it to inclulde .zip and unzip it. The browser.dtd file including the affected string mentioned above file will be under the el\locale\browser subfolder. Then repack the zip file to include your modified file, rename it back to omni.ja and put it back into the program folder’s \browser subfolder. Any update will overwrite the file, so keep a copy of it for any 56.0.x release - hopefully 57 will have it fixed automatically.

Command / shortcut keys should all be identical to the ones in English - only access keys (the ones that underline some characters) are allowed to be modified, matching localized strings. The el localizer(s) may need to check more when at it - at a quick glance, the (2) command keys for hiding this and other apps for Mac are also affected.

Side note: the ast locale has the same issue for this shortcut, as well as for many others.

Read this answer in context 👍 3

All Replies (9)

more options

See line 161 bookmarkThisPageCmd.commandkey:

<!ENTITY bookmarkThisPageCmd.label "Προσθήκη στους σελιδοδείκτες">
<!ENTITY editThisBookmarkCmd.label "Επεξεργασία σελιδοδείκτη">
<!ENTITY bookmarkThisPageCmd.commandkey "π">

I have no idea where this "π" is coming from. If I check the blame links then it shows a "d".

In what Firefox version was this still a 'd'? quote: This happened after the last update to version 56

more options

Thanks for your answer. I also attach a photo. The problem is that I cannot use any shortcut to add a bookmark, noone works - I try Ctrl+D, Ctrl+P, Ctrl+Π. Is there a way to change this shortcut from inside firefox? Thank you.

more options

Chosen Solution

The command / shortcut key seems to have been modified by one of the Greek localizers back in July and hence for 56 - see here.

I suggest you email one of them (see the top of that page - the first person is the one who made the change) and ask him to modify this and check other command keys as soon as possible, and also uplift that for 57. If you want, I can also send him a message.

I’m afraid the change will not be included for any 56.0.x release, but you should be able to modify it yourself by opening the omni.ja file in your Firefox program folder’s browser subfolder. (Not the program folder itself which contains a file named similar.) Copy that original file elsewhere, create a copy of it, rename it to inclulde .zip and unzip it. The browser.dtd file including the affected string mentioned above file will be under the el\locale\browser subfolder. Then repack the zip file to include your modified file, rename it back to omni.ja and put it back into the program folder’s \browser subfolder. Any update will overwrite the file, so keep a copy of it for any 56.0.x release - hopefully 57 will have it fixed automatically.

Command / shortcut keys should all be identical to the ones in English - only access keys (the ones that underline some characters) are allowed to be modified, matching localized strings. The el localizer(s) may need to check more when at it - at a quick glance, the (2) command keys for hiding this and other apps for Mac are also affected.

Side note: the ast locale has the same issue for this shortcut, as well as for many others.

more options

It might be easier to install the en-US Firefox version with the 'el' language pack. That language pack is a lot easier to modify since this is a XPI in the extensions folder in the profile folder.

more options

I located the browser.dtd as you told me, opened it with wordpad, replaced the "π" with "d", saved it, zipped it again to omni.ja and put it back into the program folder’s \browser subfolder but it doesn't work. Did I do something wrong? Thank you

more options

Interesting. This may sound weird, but I have seen that happen occasionally when testing localizations, as if some "caching" was involved for certain strings. (Usually they get picked up.) There would be 2 approaches that worked for me in such case:

- Either create a second profile for Firefox, start Firefox once to use that profile, then close it, and then start it again using the default profile, or

- for the Firefox startup link that is used in its shortcut, add the parameter -purgecaches to the line that contains the program folder and path. I.e. "C:\Program Files\firefox\firefox.exe" -purgecaches for the 32-bit Firefox. That would only be needed once, so you can remove the parameter afterwards when things work.

Perhaps just restarting the computer could also do the trick. Also and of course, make sure to replace the original file - you can experiment by changing other strings to see if they actually changed.

Please report back how it goes.

more options

Try to delete the compatibility.ini file in the profile folder. That will invalidate caches and cause Firefox to rebuild various files.

You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.

more options

"I’m afraid the change will not be included for any 56.0.x release, but you should be able to modify it yourself by opening the omni.ja file in your Firefox program folder’s browser subfolder. (Not the program folder itself which contains a file named similar.) Copy that original file elsewhere, create a copy of it, rename it to inclulde .zip and unzip it. The browser.dtd file including the affected string mentioned above file will be under the el\locale\browser subfolder. Then repack the zip file to include your modified file, rename it back to omni.ja and put it back into the program folder’s \browser subfolder. Any update will overwrite the file, so keep a copy of it for any 56.0.x release - hopefully 57 will have it fixed automatically." & ". . .for the Firefox startup link that is used in its shortcut, add the parameter -purgecaches to the line that contains the program folder and path. I.e. "C:\Program Files\firefox\firefox.exe" -purgecaches for the 32-bit Firefox. That would only be needed once, so you can remove the parameter afterwards when things work. . . ." That finally worked for me. Thank you very much for your help.

30/1/2018: Happened again. Followed both steps above and fixed it.

Modified by papast3

more options

Good to hear, thanks for your feedback. Meanwhile, the issue has been resolved for 57. Could you mark one of the replies above as a solution?