|
sl@0
|
1 |
<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
|
|
sl@0
|
2 |
<html>
|
|
sl@0
|
3 |
<head>
|
|
sl@0
|
4 |
<meta http-equiv="Content-Type"
|
|
sl@0
|
5 |
content="text/html; charset=iso-8859-1">
|
|
sl@0
|
6 |
<meta name="Copyright"
|
|
sl@0
|
7 |
content="Copyright (c) 2001-2003, International Business Machines Corporation and others. All Rights Reserved.">
|
|
sl@0
|
8 |
<meta name="Author" content="Eric Mader">
|
|
sl@0
|
9 |
<meta name="GENERATOR"
|
|
sl@0
|
10 |
content="Mozilla/4.72 [en] (Windows NT 5.0; U) [Netscape]">
|
|
sl@0
|
11 |
<title>Readme file for letest and gendata</title>
|
|
sl@0
|
12 |
</head>
|
|
sl@0
|
13 |
<body>
|
|
sl@0
|
14 |
<h2> What are letest and gendata?</h2>
|
|
sl@0
|
15 |
letest is a program you can use to verify that you have built and
|
|
sl@0
|
16 |
installed the ICU LayoutEngine correctly. The test is not comprehensive,
|
|
sl@0
|
17 |
it just verifies that the results of laying out some Devanagari, Arabic
|
|
sl@0
|
18 |
and Thai text are as expected. Once this test has passed, you can use
|
|
sl@0
|
19 |
the ICU LayoutEngine in your application knowing that it has been
|
|
sl@0
|
20 |
correctly installed and that the basic functionality is in place.
|
|
sl@0
|
21 |
<p>gendata is a program that is used by the ICU team to build the
|
|
sl@0
|
22 |
source file testdata.cpp, which contains the expected results of running
|
|
sl@0
|
23 |
letest. Unless you have changed your copy of the LayoutEngine and want
|
|
sl@0
|
24 |
to validate the changes on other platforms, there's no reason for you
|
|
sl@0
|
25 |
to run this program. </p>
|
|
sl@0
|
26 |
<p>(The ICU team first runs a Windows application which uses the ICU
|
|
sl@0
|
27 |
LayoutEngine to display the text that letest uses. Once it has been
|
|
sl@0
|
28 |
verified that the text is displayed correctly, gendata is run to produce
|
|
sl@0
|
29 |
testdata.cpp, and then letest is run on Windows to verify that letest
|
|
sl@0
|
30 |
still works with the new data.) <br>
|
|
sl@0
|
31 |
</p>
|
|
sl@0
|
32 |
<h2> How do I build letest?</h2>
|
|
sl@0
|
33 |
First, you need to build ICU, including the LayoutEngine.
|
|
sl@0
|
34 |
<p>On Windows, the layout project should be listed as a dependency of
|
|
sl@0
|
35 |
all, so layout will build when you build all. If it doesn't for some
|
|
sl@0
|
36 |
reason, just select the layout project in the project toolbar and build
|
|
sl@0
|
37 |
it. </p>
|
|
sl@0
|
38 |
<p>On UNIX systems, you need to add the "--enable-layout=yes" option
|
|
sl@0
|
39 |
when you invoke the runConfigureICU script. When you've done that,
|
|
sl@0
|
40 |
layout should build when you do "make all install" </p>
|
|
sl@0
|
41 |
<p>To build letest on Windows, just open the letest project in
|
|
sl@0
|
42 |
<icu>\source\test\letest and build it. On UNIX systems, connect to
|
|
sl@0
|
43 |
<top-build-dir>/test/letest and do "make all" <br>
|
|
sl@0
|
44 |
</p>
|
|
sl@0
|
45 |
<h2> How do I run letest?</h2>
|
|
sl@0
|
46 |
Before you can run letest, you'll need to get the fonts it uses. For
|
|
sl@0
|
47 |
legal reasons, we can't include them with ICU, but you can download them
|
|
sl@0
|
48 |
from the web. To do this, you'll need access to a computer running
|
|
sl@0
|
49 |
Windows. Here's how to get the fonts:
|
|
sl@0
|
50 |
<p>Download the 1.3 version of the JDK from the<a
|
|
sl@0
|
51 |
href="http://www.ibm.com/java"> IBM developerWorks Java technology zone</a>
|
|
sl@0
|
52 |
page. From this page, follow the "Tools and products" link on the left
|
|
sl@0
|
53 |
hand side, and then the link for the "IBM Developer Kit for Linux", or
|
|
sl@0
|
54 |
the "IBM Developer Kit for Windows(R), Release 1.3.0". You'll need to
|
|
sl@0
|
55 |
register with them if you haven't downloaded before. Download and
|
|
sl@0
|
56 |
install the "Runtime Environment Package." You'll need two fonts from
|
|
sl@0
|
57 |
this package. If you've let the installer use it's defaults, the fonts
|
|
sl@0
|
58 |
will be in C:\Program Files\IBM\Java13\jre\lib\fonts. The files you want
|
|
sl@0
|
59 |
are "LucidaSansRegular.ttf" and "Thonburi.ttf" Copy these font files to
|
|
sl@0
|
60 |
the directory from which you'll run letest.<br>
|
|
sl@0
|
61 |
</p>
|
|
sl@0
|
62 |
<p>Next is the Hindi font. Go to the NCST site and download <a
|
|
sl@0
|
63 |
href="http://rohini.ncst.ernet.in/indix/download/font/raghu.ttf">
|
|
sl@0
|
64 |
raghu.ttf</a>. Be sure to look at the <a
|
|
sl@0
|
65 |
href="http://rohini.ncst.ernet.in/indix/download/font/README"> README</a>
|
|
sl@0
|
66 |
file before you download the font. You can download raghu.ttf into the
|
|
sl@0
|
67 |
directory from which you'll run letest.<br>
|
|
sl@0
|
68 |
</p>
|
|
sl@0
|
69 |
<p>There's still one more font to get, the Code2000 Unicode font.Go to
|
|
sl@0
|
70 |
James Kass' <a href="http://home.att.net/%7Ejameskass/">Unicode
|
|
sl@0
|
71 |
Support In Your Browser</a> page and click on the link that says "Click
|
|
sl@0
|
72 |
Here to download Code2000 shareware demo Unicode font." This will
|
|
sl@0
|
73 |
download a .ZIP file which contains CODE2000.TTF and CODE2000.HTM.
|
|
sl@0
|
74 |
Expand this .ZIP file and put the CODE2000.TTF file in the directory
|
|
sl@0
|
75 |
from which you'll run letest.<br>
|
|
sl@0
|
76 |
</p>
|
|
sl@0
|
77 |
<p><span style="font-weight: bold;">Note:</span> The Code2000 font is
|
|
sl@0
|
78 |
shareware. If you want to use it for longer than a trial period, you
|
|
sl@0
|
79 |
should send a shareware fee to James. Directions for how to do this are
|
|
sl@0
|
80 |
in CODE2000.HTM.</p>
|
|
sl@0
|
81 |
<p>That's it! Now all you have to do is run letest (CTRL+F5 in Visual
|
|
sl@0
|
82 |
C++, or "./letest" in UNIX) If everything's OK you should see
|
|
sl@0
|
83 |
something like this: </p>
|
|
sl@0
|
84 |
<blockquote><tt>Test 0, font = raghu.ttf... passed.</tt> <br>
|
|
sl@0
|
85 |
<tt>Test 1, font = CODE2000.TTF... passed.</tt> <br>
|
|
sl@0
|
86 |
<tt>Test 2, font = LucidaSansRegular.ttf... passed.</tt> <br>
|
|
sl@0
|
87 |
<tt>Test 3, font = Thonburi.ttf... passed.</tt></blockquote>
|
|
sl@0
|
88 |
</body>
|
|
sl@0
|
89 |
</html>
|