為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

I suddenly can't write in Hebrew (I could do it before)

  • 4 回覆
  • 4 有這個問題
  • 1 次檢視
  • 最近回覆由 Toby1

more options

When I use left Alt + shift to change the input language, all the letters are still written in English. I only have to languages installed on the computer - English and Hebrew.

Pressing left/right CTRL +shift does not help, although changing the writing side (from left to right).

I am using Firefox 25.0.1

When I use left Alt + shift to change the input language, all the letters are still written in English. I only have to languages installed on the computer - English and Hebrew. Pressing left/right CTRL +shift does not help, although changing the writing side (from left to right). I am using Firefox 25.0.1

被選擇的解決方法

You're welcome.

Note that you can change the bidi text direction in Firefox via Ctrl+Shift+X.

從原來的回覆中察看解決方案 👍 1

所有回覆 (4)

more options

Does it work if you use the Language bar?

It is usually best to assign a specific key sequence to each language instead of the sequence to cycle as that sequence can easily get triggered if you use an menu shortcut that uses the same shortcut.

more options

Hi cor-el, it didn't help.

But I have good news, today the Hebrew works. I will update if it breaks again.

Thank you

more options

選擇的解決方法

You're welcome.

Note that you can change the bidi text direction in Firefox via Ctrl+Shift+X.

more options

I had the same problem switching the language from English (either using Alt-Shift or trying to change it in the language bar). This happened in all my browsers, not just Firefox. It was working yesterday in Office, but today it wasn't working anywhere.

I seem to have found the solution, though: In the regional and language settings of Windows you uncheck displaying the language bar on the desktop and after applying that you recheck it.

I would assume the problem occurred after I applied an update in Windows.