Your target document probably uses a font that doesn’t have all the necessary characters. Make sure you choose the right font in your document.
For European languages, virtually all fonts will work fine; for IPA symbols, you may need something like Lucida Sans Unicode Segoe UI or Lucida Grande. Detailed information on recommended fonts is available on the IPA for English and Full IPA pages.
Are you using one of the supported browser versions? TypeIt supports the following browsers: Google Chrome, Mozilla Firefox, Safari, as well as Internet Explorer (10, 11) and Microsoft Edge (except for some issues). Safari for iOS is supported, but subject to OS limitations like poor support for hardware keyboards.
If you’re using a supported browser version, please report any bugs to me at the e-mail address shown on the About page.
If some of the keyboard shortcuts work, but others don’t, there are two possibilities:
As a backup mechanism, TypeIt provides a secondary keyboard shortcut in such cases. For example, when typing Spanish accents, the ¿ character can be typed by pressing either Alt + / or Alt + 2 (Ctrl+/, Ctrl+2 in IE/Edge). The second shortcut is meant for keyboard layouts on which the primary shortcut doesn’t work properly.
First of all, you shouldn’t have to convert the characters into HTML entities (e.g. é or —). That is so 1990s! In the 21st century, all you need is a Unicode-capable editor (even the Windows Notepad will do fine):
Do one of the following:
Content-type: text/html; charset=utf-8
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
TypeIt automatically saves your text in your browser so that it can be restored if you accidentally navigate to another site, close the tab, or if your browser crashes (note that this does not work in all browsers). This data is stored in what is called a “browsing session”. Depending on your browser, the browsing session may persist even after you close the tab or exit the browser – this is designed to enable you to do things like restoring a tab after you close it accidentally, or restoring all your tabs after you exit the browser. This means that someone with access to your computer could read your text, even after you exit TypeIt. Potentially, your text could even be read by another site you visit.
If you want to keep your text completely private, you can do one of two things:
Every major browser except Firefox is crippled in some way when it comes to supporting keyboard shortcuts. For instance, in Google Chrome, we cannot assign the Spanish ñ to Ctrl + N because if you press Ctrl + N, Chrome will open a new window, and this behavior cannot be changed. In Microsoft Edge, we cannot assign ð (used in IPA and Icelandic keyboards) to Alt + D because Alt + D always moves the cursor to the address bar. There’s a whole list of issues like these.
For this reason, TypeIt (as of November 2015) will detect your browser and intelligently choose the “modifier key” – Alt or Ctrl – that it uses for keyboard shortcuts in order to minimize the amount of problems. If possible, it will use Alt, because it’s easier to reach than Ctrl, but if your browser has more complete support for Ctrl-shortcuts than for Alt-shortcuts, it will use Ctrl instead. Currently, the modifier in Firefox, Chrome and Safari is Alt; in Internet Explorer and Edge it’s Ctrl.
You can change the modifier in the Settings menu – but you’re likely to run into problems with certain shortcuts, especially if you use Chrome, Internet Explorer or Edge.
Google Chrome makes it impossible to use certain shortcuts in a Web application. For example, Ctrl + N always opens a new window and there is no way to change that behavior. The same goes for Ctrl + W (close window) and Ctrl + T (new tab). As a result, when you try to type ñ in the Spanish keyboard (shortcut: Ctrl + N), you will not only not get the character you wanted; you will also create a new Chrome window, which you will then have to close.
This annoying issue has been reported to the Chrome developers. The solution that has been suggested is to allow Web apps to ask for permission to access the entire keyboard. However, no actual work is being done to implement this idea. You can help bring more attention to this problem: go to the Chromium bug tracker site and star this issue.*/ ?>