Download UDP
Answers to Frequently Asked Questions

Read Me
Contact Us

The Unicode

 Word Processing 

Site Search

Search powered by Bravenet


  1. How do I get Tibetan to work? The programs seems to only display English.

    Have you installed any Tibetan Fonts? Be sure to read Read Important Information about Fonts. Once Tibetan fonts are installed, press the F8 function key to enable the Tibetan keyboard.

  2. When I send an e-mail, my recipients who use Netscape receive garbage rather than Tibetan.

    The "Tibetan Modern A" font is a symbol font and is NOT displayed correctly using Netscape. If you send a Tibetan e-mail encoded in "Tibetan Modern A", recipients using Netscape will not be able to view it correctly; recipients using Microsoft Outlook WILL be able to view it correctly. If you send an e-mail using Netscape it will be received correctly by Outlook, even tho it may look wrong when it is sent.

    One solution is to use Unicode fonts. Another is to use fonts from the Tibetan Computer Company but your correspondents will need these fonts as well. Another solution is to download Pierre Robillard's LTibetan font set which is also supported by UDP. Two of these fonts are ANSI fonts and will be displayed properly by Netscape.

  3. Which e-mail program works best for Tibetan?

    UDP has been tested with Thunderbird, Mozilla 1.5, Netscape 4.x & 7.x and Microsoft Outlook Express 6.0. Thunderbird works best. Mozilla and Netscape work better for sending, Outlook Express works better for receiving.

    The drawbacks to Mozilla and Netscape are that they won't wrap long lines at tshegs and that they will not correctly display e-mails that use the "Tibetan Modern A" font. It has the advantage that it can send Tibetan e-mail in-line. You can use the Options/AdvancedOptions dialog box and check the "Send E-mail messages in-line" box.

    Outlook Express displays Tibetan e-mail sent by Mozilla and Netscape perfectly with long lines wrapped at tshegs. But it cannot automatically send Tibetan in-line (or at least I haven't been able to figure out how to convince it to do so yet). If you use Outlook Express to send a Tibetan e-mail, it will display correctly in Mozilla and Netscape if you use Unicode fonts or fonts from the Tibetan Computer Company (except than long lines will not be wrapped). That same e-mail will be received by Outlook Express as an attachment that must be opened in your browser - where it will display perfectly in Internet Explorer (but with no wrapping of long lines if Mozilla or Netscape is your default browser).

    You can Copy text from UDP to the clipboard and Paste it into Outlook Express provided your Outlook Express composition window is a Rich Text window - click the Format / Rich Text menu item to convert the window if necessary.

    You can also use copy and paste to send Tibetan text using Yahoo Mail and Hotmail. See E-mail and UDP in the UDP Help System (press F1) for more information.

    If anyone has the programming details of how to build an in-line HTML MAPI message for Outlook Express, please e-mail me at

  4. Does Tibetan e-mail work with AOL, Eudora, Juno, etc.?

    I don't know about AOL or Eudora - if you find out, please e-mail me at so I can document it here. The free version of Juno does not handle attachments (the last time I checked). so it is NOT supported.

  5. How do I send a Tibetan FAX?

    You need to have a FAX modem and standard Windows FAXing software installed on your system. This kind of software often comes with Windows - check in Start/Programs/Accessories. Or you can install a 3rd party FAX package. Once the package is installed, it will appear to most programs, including UDP, as a printer. To send a FAX in UDP, click the File/PrintSetup menu item and then click the Printer button and select your FAX program in the combo box of the screen that appears. Then use the File/Print menu item to print the document and use your FAX software to send it.

  6. Is there an Apple Macintosh version of UDP?

    It is highly unlikely that UDP will ever be ported to the Mac. However, UDP works very well with CrossOver Mac 6.0 on Mac/OS X. CrossOver Mac costs about $US60 and is well worth the price. If you do install UDP under CrossOver Mac, you should set Options > Text > Line Endings for all Text Files to Convert to Unix and Mac/OS X and you should set Options > Unicode > Write Format to either UTF-8 or UTF-16 for Intel Unix/Linux and Mac/OS X.

  7. Will there be a Linux or Unix version of UDP?

    One of the users of UDP writes "I tried UDP to enter Tibetan text. I successfully launched it through WINE under Linux." So WINE appears to be the solution for Linux. If you do install UDP under WINE, you should set Options > Text > Line Endings for all Text Files to Convert to Unix and Mac/OS X and you should set Options > Unicode > Write Format to either UTF-8 or UTF-16 for Intel Unix/Linux and Mac/OS X.

  8. Does UDP run on Win/95?

    No. UDP uses a number of Win32 API calls that Win/95 does not support so it is highly unlikely it will work correctly (or even at all) on Win/95. But then it has never been tried on Win/95 - so I really don't know. But UDP will never be officially supported on Win/95.

  9. What is the source of the Spelling Checker?

    The Spell Checking Engine by Matt Gullett at The code found there has been modified so that it will work with UDP and also new features and minor bug fixes have been added. Many thanks to Matt for making this code freely available.

  10. Where does the grapics support come from?

    The FreeImage Project at FreeImage is an Open Source library project for developers who wish to support popular graphics image formats like PNG, BMP, JPEG, TIFF and others as needed by today's multimedia applications. Many thanks to the FreeImage Project for this excellent package.

  11. What image formats does UDP support?

    It supports all the common ones like PNG, BMP, JPEG, TIFF and GIF. It actually supports all the ones FreeImage supports - a full list can be found at

Back to UDP Home

This page hosted by

Potala Software / / Revised 24 Dec 2004