You have a question you hope I can answer? Chances are I have already answered it, a number of times. Before contacting me, read through this page and see if your favourite question is here.
Can you translate something into Elvish for me?
That question is more complicated than it may seem, for a number of reasons:
I want a Tengwar transcription for a tattoo / ring. Can you help me?
This is the request I get most frequently. Sadly, I don’t have enough spare time to help everyone who wants me to. I therefore recommend these steps to everyone interested in a personal Tengwar text:
The transcription programs (such as TengScribe, KTT, YaTT) only generate nonsense text! What is wrong?
For most of these programs to work, you need to install a Tengwar font with a keyboard layout compatible with that invented by Daniel Smith for his font Tengwar Quenya. All fonts listed on my Links page work, except the Unicode font Tengwar Telcontar. The fonts Tengwar Parmaite and Tengwar Eldamar, downloadable from this site, also work.
The transcription generated by the Tengwar Scribe looks strange. There are strange gaps or spaces in the text!
When displaying tengwar and other formatted text, the TengScribe relies on a Windows component known as the RichText control. In some Windows versions (specifically some editions of Windows 2000 and XP), there is a bug in this component which prevents it from showing tehtar above tengwar, instead placing them between tengwar. (A more technical answer is that the control is uncapable to display characters with a width of zero correctly. Since most tehtar are zero-width in Tengwar fonts, so as to overlap the preceding letter, Windows inserts extra spacing where these characters occur.)
Note that the generated transcription might still be technically correct, it is just displayed badly in the TengScribe. If you save your transcription as an RTF document and then open it in a word processor such as Word, it will be shown correctly. (The small word processor WordPad that is included with Windows also employs the RichText control, so the bug will show up there as well.)
There are other transcription utilities available which do not have this error, simply because they don’t depend on the Windows-native RichText control. I am not primarily a programmer, and I lack the skills necessary to correct the bug. To those that encounter it I am therefore obliged to recommend trying some of the other excellent transcription utilities available. See the Fonts and utilities section of my Links page for a list of those.