--- /dev/null
+Kenichi Handa <handa@m17n.org>
+ Core developer.
+
+Mikiko Nishikimi <nisikimi@m17n.org>
+ Core developer.
+
+Naoto Takahashi <ntakahas@m17n.org>
+ Core developer.
+
+Satoru Tomura <tomura@m17n.org>
+ Core developer.
--- /dev/null
+ GNU LESSER GENERAL PUBLIC LICENSE
+ Version 2.1, February 1999
+
+ Copyright (C) 1991, 1999 Free Software Foundation, Inc.
+ 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+[This is the first released version of the Lesser GPL. It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.]
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+ This license, the Lesser General Public License, applies to some
+specially designated software packages--typically libraries--of the
+Free Software Foundation and other authors who decide to use it. You
+can use it too, but we suggest you first think carefully about whether
+this license or the ordinary General Public License is the better
+strategy to use in any particular case, based on the explanations below.
+
+ When we speak of free software, we are referring to freedom of use,
+not price. Our General Public Licenses are designed to make sure that
+you have the freedom to distribute copies of free software (and charge
+for this service if you wish); that you receive source code or can get
+it if you want it; that you can change the software and use pieces of
+it in new free programs; and that you are informed that you can do
+these things.
+
+ To protect your rights, we need to make restrictions that forbid
+distributors to deny you these rights or to ask you to surrender these
+rights. These restrictions translate to certain responsibilities for
+you if you distribute copies of the library or if you modify it.
+
+ For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you. You must make sure that they, too, receive or can get the source
+code. If you link other code with the library, you must provide
+complete object files to the recipients, so that they can relink them
+with the library after making changes to the library and recompiling
+it. And you must show them these terms so they know their rights.
+
+ We protect your rights with a two-step method: (1) we copyright the
+library, and (2) we offer you this license, which gives you legal
+permission to copy, distribute and/or modify the library.
+
+ To protect each distributor, we want to make it very clear that
+there is no warranty for the free library. Also, if the library is
+modified by someone else and passed on, the recipients should know
+that what they have is not the original version, so that the original
+author's reputation will not be affected by problems that might be
+introduced by others.
+\f
+ Finally, software patents pose a constant threat to the existence of
+any free program. We wish to make sure that a company cannot
+effectively restrict the users of a free program by obtaining a
+restrictive license from a patent holder. Therefore, we insist that
+any patent license obtained for a version of the library must be
+consistent with the full freedom of use specified in this license.
+
+ Most GNU software, including some libraries, is covered by the
+ordinary GNU General Public License. This license, the GNU Lesser
+General Public License, applies to certain designated libraries, and
+is quite different from the ordinary General Public License. We use
+this license for certain libraries in order to permit linking those
+libraries into non-free programs.
+
+ When a program is linked with a library, whether statically or using
+a shared library, the combination of the two is legally speaking a
+combined work, a derivative of the original library. The ordinary
+General Public License therefore permits such linking only if the
+entire combination fits its criteria of freedom. The Lesser General
+Public License permits more lax criteria for linking other code with
+the library.
+
+ We call this license the "Lesser" General Public License because it
+does Less to protect the user's freedom than the ordinary General
+Public License. It also provides other free software developers Less
+of an advantage over competing non-free programs. These disadvantages
+are the reason we use the ordinary General Public License for many
+libraries. However, the Lesser license provides advantages in certain
+special circumstances.
+
+ For example, on rare occasions, there may be a special need to
+encourage the widest possible use of a certain library, so that it becomes
+a de-facto standard. To achieve this, non-free programs must be
+allowed to use the library. A more frequent case is that a free
+library does the same job as widely used non-free libraries. In this
+case, there is little to gain by limiting the free library to free
+software only, so we use the Lesser General Public License.
+
+ In other cases, permission to use a particular library in non-free
+programs enables a greater number of people to use a large body of
+free software. For example, permission to use the GNU C Library in
+non-free programs enables many more people to use the whole GNU
+operating system, as well as its variant, the GNU/Linux operating
+system.
+
+ Although the Lesser General Public License is Less protective of the
+users' freedom, it does ensure that the user of a program that is
+linked with the Library has the freedom and the wherewithal to run
+that program using a modified version of the Library.
+
+ The precise terms and conditions for copying, distribution and
+modification follow. Pay close attention to the difference between a
+"work based on the library" and a "work that uses the library". The
+former contains code derived from the library, whereas the latter must
+be combined with the library in order to run.
+\f
+ GNU LESSER GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License Agreement applies to any software library or other
+program which contains a notice placed by the copyright holder or
+other authorized party saying it may be distributed under the terms of
+this Lesser General Public License (also called "this License").
+Each licensee is addressed as "you".
+
+ A "library" means a collection of software functions and/or data
+prepared so as to be conveniently linked with application programs
+(which use some of those functions and data) to form executables.
+
+ The "Library", below, refers to any such software library or work
+which has been distributed under these terms. A "work based on the
+Library" means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is
+included without limitation in the term "modification".)
+
+ "Source code" for a work means the preferred form of the work for
+making modifications to it. For a library, complete source code means
+all the source code for all modules it contains, plus any associated
+interface definition files, plus the scripts used to control compilation
+and installation of the library.
+
+ Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it). Whether that is true depends on what the Library does
+and what the program that uses the Library does.
+
+ 1. You may copy and distribute verbatim copies of the Library's
+complete source code as you receive it, in any medium, provided that
+you conspicuously and appropriately publish on each copy an
+appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any
+warranty; and distribute a copy of this License along with the
+Library.
+
+ You may charge a fee for the physical act of transferring a copy,
+and you may at your option offer warranty protection in exchange for a
+fee.
+\f
+ 2. You may modify your copy or copies of the Library or any portion
+of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) The modified work must itself be a software library.
+
+ b) You must cause the files modified to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ c) You must cause the whole of the work to be licensed at no
+ charge to all third parties under the terms of this License.
+
+ d) If a facility in the modified Library refers to a function or a
+ table of data to be supplied by an application program that uses
+ the facility, other than as an argument passed when the facility
+ is invoked, then you must make a good faith effort to ensure that,
+ in the event an application does not supply such function or
+ table, the facility still operates, and performs whatever part of
+ its purpose remains meaningful.
+
+ (For example, a function in a library to compute square roots has
+ a purpose that is entirely well-defined independent of the
+ application. Therefore, Subsection 2d requires that any
+ application-supplied function or table used by this function must
+ be optional: if the application does not supply it, the square
+ root function must still compute square roots.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Library,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Library, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote
+it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library. To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License. (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.) Do not make any other change in
+these notices.
+\f
+ Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+ This option is useful when you wish to copy part of the code of
+the Library into a program that is not a library.
+
+ 4. You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form
+under the terms of Sections 1 and 2 above provided that you accompany
+it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a
+medium customarily used for software interchange.
+
+ If distribution of object code is made by offering access to copy
+from a designated place, then offering equivalent access to copy the
+source code from the same place satisfies the requirement to
+distribute the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 5. A program that contains no derivative of any portion of the
+Library, but is designed to work with the Library by being compiled or
+linked with it, is called a "work that uses the Library". Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+ However, linking a "work that uses the Library" with the Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a "work that uses the
+library". The executable is therefore covered by this License.
+Section 6 states terms for distribution of such executables.
+
+ When a "work that uses the Library" uses material from a header file
+that is part of the Library, the object code for the work may be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library. The
+threshold for this to be true is not precisely defined by law.
+
+ If such an object file uses only numerical parameters, data
+structure layouts and accessors, and small macros and small inline
+functions (ten lines or less in length), then the use of the object
+file is unrestricted, regardless of whether it is legally a derivative
+work. (Executables containing this object code plus portions of the
+Library will still fall under Section 6.)
+
+ Otherwise, if the work is a derivative of the Library, you may
+distribute the object code for the work under the terms of Section 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+\f
+ 6. As an exception to the Sections above, you may also combine or
+link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work
+under terms of your choice, provided that the terms permit
+modification of the work for the customer's own use and reverse
+engineering for debugging such modifications.
+
+ You must give prominent notice with each copy of the work that the
+Library is used in it and that the Library and its use are covered by
+this License. You must supply a copy of this License. If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one
+of these things:
+
+ a) Accompany the work with the complete corresponding
+ machine-readable source code for the Library including whatever
+ changes were used in the work (which must be distributed under
+ Sections 1 and 2 above); and, if the work is an executable linked
+ with the Library, with the complete machine-readable "work that
+ uses the Library", as object code and/or source code, so that the
+ user can modify the Library and then relink to produce a modified
+ executable containing the modified Library. (It is understood
+ that the user who changes the contents of definitions files in the
+ Library will not necessarily be able to recompile the application
+ to use the modified definitions.)
+
+ b) Use a suitable shared library mechanism for linking with the
+ Library. A suitable mechanism is one that (1) uses at run time a
+ copy of the library already present on the user's computer system,
+ rather than copying library functions into the executable, and (2)
+ will operate properly with a modified version of the library, if
+ the user installs one, as long as the modified version is
+ interface-compatible with the version that the work was made with.
+
+ c) Accompany the work with a written offer, valid for at
+ least three years, to give the same user the materials
+ specified in Subsection 6a, above, for a charge no more
+ than the cost of performing this distribution.
+
+ d) If distribution of the work is made by offering access to copy
+ from a designated place, offer equivalent access to copy the above
+ specified materials from the same place.
+
+ e) Verify that the user has already received a copy of these
+ materials or that you have already sent this user a copy.
+
+ For an executable, the required form of the "work that uses the
+Library" must include any data and utility programs needed for
+reproducing the executable from it. However, as a special exception,
+the materials to be distributed need not include anything that is
+normally distributed (in either source or binary form) with the major
+components (compiler, kernel, and so on) of the operating system on
+which the executable runs, unless that component itself accompanies
+the executable.
+
+ It may happen that this requirement contradicts the license
+restrictions of other proprietary libraries that do not normally
+accompany the operating system. Such a contradiction means you cannot
+use both them and the Library together in an executable that you
+distribute.
+\f
+ 7. You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+the Library and of the other library facilities is otherwise
+permitted, and provided that you do these two things:
+
+ a) Accompany the combined library with a copy of the same work
+ based on the Library, uncombined with any other library
+ facilities. This must be distributed under the terms of the
+ Sections above.
+
+ b) Give prominent notice with the combined library of the fact
+ that part of it is a work based on the Library, and explaining
+ where to find the accompanying uncombined form of the same work.
+
+ 8. You may not copy, modify, sublicense, link with, or distribute
+the Library except as expressly provided under this License. Any
+attempt otherwise to copy, modify, sublicense, link with, or
+distribute the Library is void, and will automatically terminate your
+rights under this License. However, parties who have received copies,
+or rights, from you under this License will not have their licenses
+terminated so long as such parties remain in full compliance.
+
+ 9. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Library or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Library or works based on it.
+
+ 10. Each time you redistribute the Library (or any work based on the
+Library), the recipient automatically receives a license from the
+original licensor to copy, distribute, link with or modify the Library
+subject to these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties with
+this License.
+\f
+ 11. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Library at all. For example, if a patent
+license would not permit royalty-free redistribution of the Library by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+If any portion of this section is held invalid or unenforceable under any
+particular circumstance, the balance of the section is intended to apply,
+and the section as a whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 12. If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Library under this License may add
+an explicit geographical distribution limitation excluding those countries,
+so that distribution is permitted only in or among countries not thus
+excluded. In such case, this License incorporates the limitation as if
+written in the body of this License.
+
+ 13. The Free Software Foundation may publish revised and/or new
+versions of the Lesser General Public License from time to time.
+Such new versions will be similar in spirit to the present version,
+but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library
+specifies a version number of this License which applies to it and
+"any later version", you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation. If the Library does not specify a
+license version number, you may choose any version ever published by
+the Free Software Foundation.
+\f
+ 14. If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+write to the author to ask for permission. For software which is
+copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this. Our
+decision will be guided by the two goals of preserving the free status
+of all derivatives of our free software and of promoting the sharing
+and reuse of software generally.
+
+ NO WARRANTY
+
+ 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+\f
+ How to Apply These Terms to Your New Libraries
+
+ If you develop a new library, and you want it to be of the greatest
+possible use to the public, we recommend making it free software that
+everyone can redistribute and change. You can do so by permitting
+redistribution under these terms (or, alternatively, under the terms of the
+ordinary General Public License).
+
+ To apply these terms, attach the following notices to the library. It is
+safest to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least the
+"copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the library's name and a brief idea of what it does.>
+ Copyright (C) <year> <name of author>
+
+ This library is free software; you can redistribute it and/or
+ modify it under the terms of the GNU Lesser General Public
+ License as published by the Free Software Foundation; either
+ version 2.1 of the License, or (at your option) any later version.
+
+ This library is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ Lesser General Public License for more details.
+
+ You should have received a copy of the GNU Lesser General Public
+ License along with this library; if not, write to the Free Software
+ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+
+Also add information on how to contact you by electronic and paper mail.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the library, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the
+ library `Frob' (a library for tweaking knobs) written by James Random Hacker.
+
+ <signature of Ty Coon>, 1 April 1990
+ Ty Coon, President of Vice
+
+That's all there is to it!
+
+
--- /dev/null
+2006-03-24 Kenichi Handa <handa@m17n.org>
+
+ * Version 0.9.0 released.
+
+\f
+Copyright (C) 2006
+ National Institute of Advanced Industrial Science and Technology (AIST)
+ Registration Number H15PRO112
+
+This file is part of m17n-pango; a sub-part of the m17n library.
+
+The m17n library is free software; you can redistribute it and/or
+modify it under the terms of the GNU Lesser General Public License
+as published by the Free Software Foundation; either version 2.1 of
+the License, or (at your option) any later version.
+
+The m17n library is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+Lesser General Public License for more details.
+
+You should have received a copy of the GNU Lesser General Public
+License along with the m17n library; if not, write to the Free
+Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA
+02111-1307, USA.
--- /dev/null
+Installation Instructions
+*************************
+
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
+Software Foundation, Inc.
+
+This file is free documentation; the Free Software Foundation gives
+unlimited permission to copy, distribute and modify it.
+
+Basic Installation
+==================
+
+These are generic installation instructions.
+
+ The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation. It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions. Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+
+ It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring. (Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.)
+
+ If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release. If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+ The file `configure.ac' (or `configure.in') is used to create
+`configure' by a program called `autoconf'. You only need
+`configure.ac' if you want to change it or regenerate `configure' using
+a newer version of `autoconf'.
+
+The simplest way to compile this package is:
+
+ 1. `cd' to the directory containing the package's source code and type
+ `./configure' to configure the package for your system. If you're
+ using `csh' on an old version of System V, you might need to type
+ `sh ./configure' instead to prevent `csh' from trying to execute
+ `configure' itself.
+
+ Running `configure' takes awhile. While running, it prints some
+ messages telling which features it is checking for.
+
+ 2. Type `make' to compile the package.
+
+ 3. Optionally, type `make check' to run any self-tests that come with
+ the package.
+
+ 4. Type `make install' to install the programs and any data files and
+ documentation.
+
+ 5. You can remove the program binaries and object files from the
+ source code directory by typing `make clean'. To also remove the
+ files that `configure' created (so you can compile the package for
+ a different kind of computer), type `make distclean'. There is
+ also a `make maintainer-clean' target, but that is intended mainly
+ for the package's developers. If you use it, you may have to get
+ all sorts of other programs in order to regenerate files that came
+ with the distribution.
+
+Compilers and Options
+=====================
+
+Some systems require unusual options for compilation or linking that the
+`configure' script does not know about. Run `./configure --help' for
+details on some of the pertinent environment variables.
+
+ You can give `configure' initial values for configuration parameters
+by setting variables in the command line or in the environment. Here
+is an example:
+
+ ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
+
+ *Note Defining Variables::, for more details.
+
+Compiling For Multiple Architectures
+====================================
+
+You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory. To do this, you must use a version of `make' that
+supports the `VPATH' variable, such as GNU `make'. `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script. `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.
+
+ If you have to use a `make' that does not support the `VPATH'
+variable, you have to compile the package for one architecture at a
+time in the source code directory. After you have installed the
+package for one architecture, use `make distclean' before reconfiguring
+for another architecture.
+
+Installation Names
+==================
+
+By default, `make install' will install the package's files in
+`/usr/local/bin', `/usr/local/man', etc. You can specify an
+installation prefix other than `/usr/local' by giving `configure' the
+option `--prefix=PREFIX'.
+
+ You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files. If you
+give `configure' the option `--exec-prefix=PREFIX', the package will
+use PREFIX as the prefix for installing programs and libraries.
+Documentation and other data files will still use the regular prefix.
+
+ In addition, if you use an unusual directory layout you can give
+options like `--bindir=DIR' to specify different values for particular
+kinds of files. Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.
+
+ If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+Optional Features
+=================
+
+Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System). The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+ For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+Specifying the System Type
+==========================
+
+There may be some features `configure' cannot figure out automatically,
+but needs to determine by the type of machine the package will run on.
+Usually, assuming the package is built to be run on the _same_
+architectures, `configure' can figure that out, but if it prints a
+message saying it cannot guess the machine type, give it the
+`--build=TYPE' option. TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name which has the form:
+
+ CPU-COMPANY-SYSTEM
+
+where SYSTEM can have one of these forms:
+
+ OS KERNEL-OS
+
+ See the file `config.sub' for the possible values of each field. If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the machine type.
+
+ If you are _building_ compiler tools for cross-compiling, you should
+use the `--target=TYPE' option to select the type of system they will
+produce code for.
+
+ If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with `--host=TYPE'.
+
+Sharing Defaults
+================
+
+If you want to set default values for `configure' scripts to share, you
+can create a site shell script called `config.site' that gives default
+values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/config.site' if it exists, then
+`PREFIX/etc/config.site' if it exists. Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+
+Defining Variables
+==================
+
+Variables not defined in a site shell script can be set in the
+environment passed to `configure'. However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost. In order to avoid this problem, you should set
+them in the `configure' command line, using `VAR=value'. For example:
+
+ ./configure CC=/usr/local2/bin/gcc
+
+causes the specified `gcc' to be used as the C compiler (unless it is
+overridden in the site shell script). Here is a another example:
+
+ /bin/bash ./configure CONFIG_SHELL=/bin/bash
+
+Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
+configuration-related scripts to be executed by `/bin/bash'.
+
+`configure' Invocation
+======================
+
+`configure' recognizes the following options to control how it operates.
+
+`--help'
+`-h'
+ Print a summary of the options to `configure', and exit.
+
+`--version'
+`-V'
+ Print the version of Autoconf used to generate the `configure'
+ script, and exit.
+
+`--cache-file=FILE'
+ Enable the cache: use and save the results of the tests in FILE,
+ traditionally `config.cache'. FILE defaults to `/dev/null' to
+ disable caching.
+
+`--config-cache'
+`-C'
+ Alias for `--cache-file=config.cache'.
+
+`--quiet'
+`--silent'
+`-q'
+ Do not print messages saying which checks are being made. To
+ suppress all normal output, redirect it to `/dev/null' (any error
+ messages will still be shown).
+
+`--srcdir=DIR'
+ Look for the package's source code in directory DIR. Usually
+ `configure' can determine that directory automatically.
+
+`configure' also accepts some other, not widely useful, options. Run
+`configure --help' for more details.
+
--- /dev/null
+## Process this file with automake to create Makefile.in.
+
+PANGO_XTRA_CFLAGS = -DG_LOG_DOMAIN=\"Pango\" \
+ -DPANGO_ENABLE_ENGINE \
+ -DPANGO_ENABLE_BACKEND \
+ -DG_DISABLE_DEPRECATED
+
+moduledir = ${pkglibdir}/${PANGO_MODULE_VERSION}/modules
+module_LTLIBRARIES = m17n-pango-fc.la
+
+m17n_pango_fc_la_SOURCES = m17n-fc.c
+m17n_pango_fc_la_CFLAGS = ${PANGO_XTRA_CFLAGS} ${PANGOFT2_CFLAGS} ${M17N_CLFAGS}
+m17n_pango_fc_la_LDFLAGS = -export-dynamic -avoid-version -module
+m17n_pango_fc_la_LIBADD = ${PANGOFT2_LIBS} ${M17N_LIBS}
+
+install-data-hook:
+ pango-querymodules ${moduledir}/m17n-pango-fc.so \
+ > ${moduledir}/pango.modules
+ pango-querymodules \
+ | sed -n -e '/pango-basic/p' -e '/pango-hangul/p' \
+ >> ${moduledir}/pango.modules
+ echo "[Pango]" > ${moduledir}/pangorc
+ echo "ModuleFiles = ${moduledir}/pango.modules" >> ${moduledir}/pangorc
--- /dev/null
+This directory tree holds version 0.9.0 of m17n-pango. -*- text -*-
+
+Copyright (C) 2006
+ National Institute of Advanced Industrial Science and Technology (AIST)
+ Registration Number H15PRO112
+See the end for copying conditions.
+
+This package "m17n-pango" provides a Pango shaping module for various
+scripts that requires CTL (Complex Text Layout) language. It utilizes
+the rendering capability of the m17n library.
+
+
+(1) INSTALLATION
+
+(1-1) From CVS working directory.
+
+Run the script "bootstrap.sh" in this directory. It is tested that
+the script run successfully with these versions of autotools.
+
+ libtool-1.5.6
+ automake-1.9.5
+ autoconf-2.59
+
+Then, proceed to the next step.
+
+(1-2) From the tarball.
+
+It requires Pango (ver.1.4 or the later) and the m17n library
+(ver.1.3.3 or the later).
+
+Type the followings on the command line.
+
+ % ./configure
+ % make
+ % make install
+
+The default installation path is "/usr/local".
+Thus, this loadable module is installed in /usr/local/lib/m17n-pango/1.4.0/modules
+ m17n-core.h, m17n.h, m17n-gui.h, m17n-err.h, m17n-X.h
+These library files are installed in /usr/local/lib:
+ libm17n-core.{a,so*,la}
+ libm17n.{a,so*,la}
+ libm17n-gui.{a,so*,la}
+ libm17n-X.{a,so*,la}
+ libm17n-gd.{a,so*,la}
+ libimx-anthy.{a,so*,la},
+ libimx-ispell.{a,so*,la},
+This shell script is installed in /usr/local/bin:
+ m17n-config
+These sample programs are installed in /usr/local/bin too:
+ m17n-conv, m17n-date, m17n-view, m17n-dump, m17n-edit
+
+If you don't need GUI libraries (libm17n-gui.so and etc.), you can
+instruct the `configure' script not to build them as below:
+
+ % ./configure --without-gui
+
+This file under `example' sub-directory is a Japanese resource file
+for m17n-edit. It is not installed but useful in Japanese locale. Copy
+it to your home directory (or, for instance,
+/usr/X11R6/lib/X11/ja/app-defaults) and rename it to "M17NEdit" if you
+want to see labels in Japanese:
+ M17NEdit.ja
+
+These text files under `example' sub-directory are not installed but
+useful for testing the rendering engine of the m17n library:
+ HELLO.utf8 HELLO.xml HELLO-ja.utf8 HELLO-ja.xml HELLO.html
+XXX.xml are generated from XXX.utf8 by attaching text property
+`language' and serializing.
+
+Please read also INSTALL for the generic installation instructions.
+
+
+(2) DATABASE
+
+The m17n library utilizes the m17n database available at:
+ http://www.m17n.org/m17n-lib/m17n-db
+Without this database, the m17n library loses half its value. Please
+install it (Ver.1.3.3 or the later is required) too before you try the
+above sample programs or develop a program that uses the m17n library.
+
+
+(3) DOCUMENTATION
+
+This page has a link to full documentation of the m17n library:
+ http://www.m17n.org/m17n-lib
+
+Actually, the documentation was generated by Doxygen using comments in
+the source files. There are English and Japanese comments in
+parallel.
+
+
+(4) USAGE
+
+The library provides three levels of APIs, CORE, SHELL, and GUI. For
+CORE API, include <m17n-core.h>, for SHELL API, include <m17n.h>, and
+for GUI API, include <m17n-gui.h >. See the documentation above, or
+the manual of m17nIntro(3) for more detail.
+
+The shell script "m17n-config" helps compiling and linking of a
+program that uses the m17n library. For instance this compiles PROG.c
+that uses SHELL API and builds executable PROG.
+
+ % gcc -o PROG `m17n-config --cflags` `m17n-config --libs` PROG.c
+
+This compiles PROX.c that uses GUI API and builds executable PROX.
+
+ % gcc -o PROX `m17n-config GUI --cflags` `m17n-config GUI --libs` PROX.c
+
+
+----------------------------------------------------------------------
+Copyright information
+
+Copyright (C) 2006
+ National Institute of Advanced Industrial Science and Technology (AIST)
+ Registration Number H15PRO112
+
+This file is part of m17n-pango; a sub-part of the m17n library.
+
+The m17n library is free software; you can redistribute it and/or
+modify it under the terms of the GNU Lesser General Public License
+as published by the Free Software Foundation; either version 2.1 of
+the License, or (at your option) any later version.
+
+The m17n library is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+Lesser General Public License for more details.
+
+You should have received a copy of the GNU Lesser General Public
+License along with the m17n library; if not, write to the Free
+Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA
+02111-1307, USA.
--- /dev/null
+#!/bin/sh
+# autogen.sh -- shell script to build libotf from CVS.
+# Copyright (C) 2006
+# National Institute of Advanced Industrial Science and Technology (AIST)
+# Registration Number H15PRO167
+# See the end for copying conditions.
+
+echo "Running libtoolize..."
+libtoolize --automake
+echo "Running aclocal..."
+aclocal
+echo "Running autoheader..."
+autoheader
+echo "Running automake..."
+automake -a -c
+echo "Running autoconf..."
+autoconf
+echo "The remaining steps to install this library are:"
+echo " % ./configure"
+echo " % make"
+echo " % make install"
+
+# Copyright (C) 2006
+# National Institute of Advanced Industrial Science and Technology (AIST)
+# Registration Number H15PRO167
+
+# This file is part of m17n-pango; a sub-part of the m17n library.
+
+# The m17n library is free software; you can redistribute it and/or
+# modify it under the terms of the GNU Lesser General Public License
+# as published by the Free Software Foundation; either version 2.1 of
+# the License, or (at your option) any later version.
+
+# The m17n library is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+# Lesser General Public License for more details.
+
+# You should have received a copy of the GNU Lesser General Public
+# License along with this library, in a file named COPYING; if not,
+# write to the Free Software Foundation, Inc., 59 Temple Place, Suite
+# 330, Boston, MA 02111-1307, USA
--- /dev/null
+dnl configure.ac -- autoconf script for m17n-pango.
+
+dnl Copyright (C) 2006
+dnl National Institute of Advanced Industrial Science and Technology (AIST)
+dnl Registration Number H15PRO112
+
+dnl This file is part of m17n-pango; a sub-part of the m17n
+dnl library.
+
+dnl The m17n library is free software; you can redistribute it and/or
+dnl modify it under the terms of the GNU Lesser General Public License
+dnl as published by the Free Software Foundation; either version 2.1 of
+dnl the License, or (at your option) any later version.
+
+dnl The m17n library is distributed in the hope that it will be useful,
+dnl but WITHOUT ANY WARRANTY; without even the implied warranty of
+dnl MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+dnl Lesser General Public License for more details.
+
+dnl You should have received a copy of the GNU Lesser General Public
+dnl License along with the m17n library; if not, write to the Free
+dnl Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA
+dnl 02111-1307, USA.
+
+dnl Process this file with autoconf to produce a configure script.
+
+AC_INIT(m17n-pango, 0.9.0, m17n-lib-bug@m17n.org)
+AM_INIT_AUTOMAKE
+AM_CONFIG_HEADER(config.h)
+
+dnl Checks for programs for compiling.
+AC_PROG_CC
+AM_DISABLE_STATIC
+AM_PROG_LIBTOOL
+
+dnl Checks for standard header files.
+AC_HEADER_STDC
+
+dnl Check for m17n-lib.
+PKG_CHECK_MODULES(M17N, m17n-gui >= 1.3.3)
+
+dnl Check for Pango.
+PKG_CHECK_MODULES(PANGO, pango >= 1.4.0)
+PKG_CHECK_MODULES(PANGOFT2, pangoft2 >= 1.4.0)
+AC_CHECK_PROG(HAVE_PANGO_QMODULE, pango-querymodules, yes)
+if test "x$HAVE_PANGO_QMODULE" != "xyes"; then
+ exit 1
+fi
+PANGO_MODULE_VERSION=1.4.0
+AC_SUBST(PANGO_MODULE_VERSION)
+
+AC_CONFIG_FILES([Makefile])
+
+AC_OUTPUT
+
+dnl Local Variables:
+dnl comment-start: "dnl "
+dnl comment-end: ""
+dnl comment-start-skip: "\\bdnl\\b\\s *"
+dnl End:
--- /dev/null
+/* Pango
+ * m17n-fc.c: Generic shaper using the m17n library for FreeType-based backends
+
+ Copyright (C) 2004, 2005
+ National Institute of Advanced Industrial Science and Technology (AIST)
+ Registration Number H15PRO112
+
+ This file is part of the m17n library.
+
+ The m17n library is free software; you can redistribute it and/or
+ modify it under the terms of the GNU Lesser General Public License
+ as published by the Free Software Foundation; either version 2.1 of
+ the License, or (at your option) any later version.
+
+ The m17n library is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ Lesser General Public License for more details.
+
+ You should have received a copy of the GNU Lesser General Public
+ License along with the m17n library; if not, write to the Free
+ Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA
+ 02111-1307, USA. */
+
+#include <config.h>
+
+#include <string.h>
+#include <stdlib.h>
+
+#include <pango/pango-engine.h>
+#include <pango/pango-utils.h>
+#include <pango/pangofc-font.h>
+
+#include <m17n-gui.h>
+#include <m17n-misc.h>
+
+#ifdef G_LOG_DOMAIN
+#undef G_LOG_DOMAIN
+#endif
+#define G_LOG_DOMAIN "M17N-Pango-FC"
+
+/* Control printing of debug information. It is initialized from the
+ environment variable PANGO_M17N_FC_DEBUG. Currently, any positive
+ value turns on all debug messages. */
+static int debug_level;
+
+/* Commonly used frame on nulldevice. */
+static MFrame *frame;
+
+/* Initialize this module. The main task is to open a frame on
+ nulldevice. */
+
+static void
+init_module ()
+{
+ const char *envvar = g_getenv ("PANGO_M17N_FC_DEBUG");
+ MPlist *param;
+ MFace *face;
+ MFontset *fontset;
+
+ debug_level = envvar ? atoi (envvar) : 0;
+
+ param = mplist ();
+ face = mface ();
+ fontset = (mdatabase_find (Mfontset, msymbol ("generic"), Mnil, Mnil)
+ ? mfontset ("generic") : mfontset (NULL));
+ mface_put_prop (face, Mfontset, fontset);
+ mplist_put (param, Mface, face);
+ mplist_put (param, Mdevice, Mnil);
+ frame = mframe (param);
+ m17n_object_unref (fontset);
+ m17n_object_unref (face);
+ m17n_object_unref (param);
+}
+
+/* Finalize this module by freeing frame. */
+
+static void
+fini_module ()
+{
+ m17n_object_unref (frame);
+}
+
+/* No extra fields needed for these structures. */
+typedef PangoEngineShape M17NEngineFc;
+typedef PangoEngineShapeClass M17NEngineFcClass;
+
+#define SCRIPT_ENGINE_NAME "M17NScriptEngineFc"
+#define RENDER_TYPE PANGO_RENDER_TYPE_FC
+
+static PangoEngineScriptInfo m17n_scripts[] = {
+ { PANGO_SCRIPT_ARABIC, "*" },
+ { PANGO_SCRIPT_BENGALI, "*" },
+ { PANGO_SCRIPT_DEVANAGARI, "*" },
+ { PANGO_SCRIPT_ETHIOPIC, "*" },
+ { PANGO_SCRIPT_GEORGIAN, "*" },
+ { PANGO_SCRIPT_GUJARATI, "*" },
+ { PANGO_SCRIPT_GURMUKHI, "*" },
+ { PANGO_SCRIPT_HEBREW, "*" },
+ { PANGO_SCRIPT_KANNADA, "*" },
+ { PANGO_SCRIPT_KHMER, "*" },
+ { PANGO_SCRIPT_LAO, "*" },
+ { PANGO_SCRIPT_MALAYALAM, "*" },
+ { PANGO_SCRIPT_MYANMAR, "*" },
+ { PANGO_SCRIPT_ORIYA, "*" },
+ { PANGO_SCRIPT_SINHALA, "*" },
+ { PANGO_SCRIPT_SYRIAC, "*" },
+ { PANGO_SCRIPT_TAMIL, "*" },
+ { PANGO_SCRIPT_TELUGU, "*" },
+ { PANGO_SCRIPT_THAANA, "*" },
+ { PANGO_SCRIPT_THAI, "*" },
+ { PANGO_SCRIPT_TIBETAN, "*" },
+};
+
+static PangoEngineInfo script_engines[] = {
+ {
+ SCRIPT_ENGINE_NAME,
+ PANGO_ENGINE_TYPE_SHAPE,
+ RENDER_TYPE,
+ m17n_scripts, G_N_ELEMENTS (m17n_scripts)
+ }
+};
+
+
+/* Convert PANGO_LANGUAGE to m17n-lib's language symbol. If m17n-lib
+ doesn't know about PANGO_LANGUAGE, return Mnil. */
+
+static MSymbol
+m17n_fc_get_language (PangoLanguage *pango_language)
+{
+ MSymbol language;
+
+ if (pango_language)
+ {
+ const char *lang = pango_language_to_string (pango_language);
+
+ language = msymbol (lang);
+ if (! msymbol_get (language, Mlanguage))
+ {
+ if (strlen (lang) <= 2)
+ language = Mnil;
+ else
+ {
+ /* Remove region part (e.g. "zh_CN" -> "zh"). */
+ char shortlang[3];
+
+ shortlang[0] = lang[0], shortlang[1] = lang[1], shortlang[2] = 0;
+ language = msymbol (shortlang);
+ if (! msymbol_get (language, Mlanguage))
+ language = Mnil;
+ }
+ }
+ }
+ else
+ language = Mnil;
+ return language;
+}
+
+/* Shaper function. */
+
+static void
+m17n_fc_engine_shape (PangoEngineShape *engine,
+ PangoFont *pango_font,
+ const char *text,
+ gint length,
+ PangoAnalysis *analysis,
+ PangoGlyphString *glyphs)
+{
+ /* Symbols for character property `category'. */
+ static MSymbol MZs, MCf;
+ static MDrawControl control;
+ MSymbol language;
+ PangoGlyphInfo *g;
+ MText *mt;
+ MDrawGlyph *m_glyphs;
+ int nchars, nglyphs;
+ PangoFcFont *fc_font;
+ char *fontname;
+ MFont *font;
+ int i;
+ const char *p;
+ int *offsets;
+
+ g_return_if_fail (pango_font != NULL);
+ g_return_if_fail (text != NULL);
+ g_return_if_fail (length >= 0);
+ g_return_if_fail (analysis != NULL);
+
+ if (debug_level > 0)
+ {
+ char *msg = alloca (length + 1);
+
+ if (msg)
+ {
+ memcpy (msg, text, length);
+ msg[length] = '\0';
+ }
+ else
+ msg = "...";
+ g_debug ("shape \"%s\"", msg);
+ }
+
+ if (! MZs)
+ {
+ MZs = msymbol ("Zs");
+ MCf = msymbol ("Cf");
+ }
+
+ language = m17n_fc_get_language (analysis->language);
+
+ mt = mtext_from_data (text, length, MTEXT_FORMAT_UTF_8);
+ nchars = mtext_len (mt);
+ offsets = alloca (sizeof (int) * nchars);
+ g_return_if_fail (offsets != NULL);
+ for (i = 0, p = text; i < nchars; i++, p = g_utf8_next_char (p))
+ offsets[i] = p - text;
+
+ fc_font = PANGO_FC_FONT (pango_font);
+ fontname = (char *) FcNameUnparse (fc_font->font_pattern);
+ font = mfont_parse_name (fontname, Mfontconfig);
+ free (fontname);
+ {
+ FcChar8 *filename;
+ int size;
+
+ if (FcPatternGetString (fc_font->font_pattern, FC_FILE, 0, &filename)
+ == FcResultMatch)
+ mfont_put_prop (font, Mfontfile, msymbol ((char *) filename));
+ size = (int) mfont_get_prop (font, Msize);
+ if (size)
+ mfont_put_prop (font, Msize, (void *) (size * 256));
+ if (debug_level > 0)
+ g_debug (" by %s", (char *) filename);
+ }
+
+ mtext_put_prop (mt, 0, nchars, Mfont, font);
+ if (language != Mnil)
+ mtext_put_prop (mt, 0, nchars, Mlanguage, language);
+
+ control.enable_bidi = 1;
+ m_glyphs = alloca (sizeof (MDrawGlyph) * nchars * 2);
+ g_return_if_fail (m_glyphs != NULL);
+ if (mdraw_glyph_list (frame, mt, 0, nchars, &control, m_glyphs,
+ nchars * 2, &nglyphs) < 0)
+ {
+ m_glyphs = alloca (sizeof (MDrawGlyph) * nglyphs);
+ g_return_if_fail (m_glyphs != NULL);
+ mdraw_glyph_list (frame, mt, 0, nchars, &control, m_glyphs,
+ nglyphs, &nglyphs);
+ }
+
+ pango_glyph_string_set_size (glyphs, nglyphs);
+
+ for (i = 0, g = glyphs->glyphs; i < nglyphs; i++, g++)
+ {
+ if (m_glyphs[i].glyph_code >= 0)
+ {
+ g->glyph = m_glyphs[i].glyph_code;
+ g->geometry.x_offset = m_glyphs[i].x_off * PANGO_SCALE / 256;
+ g->geometry.y_offset = m_glyphs[i].y_off * PANGO_SCALE / 256;
+ g->geometry.width = m_glyphs[i].x_advance * PANGO_SCALE / 256;
+ }
+ else
+ {
+ int c = mtext_ref_char (mt, m_glyphs[i].from);
+ MSymbol category = mchar_get_prop (c, Mcategory);
+ PangoRectangle logical_rect;
+
+ if (category == MZs)
+ {
+ g->glyph = 0;
+ g->geometry.width = m_glyphs[i].x_advance * PANGO_SCALE / 256;
+ }
+ else if (category == MCf)
+ {
+ g->glyph = 0;
+ g->geometry.width = 0;
+ }
+ else
+ {
+ g->glyph = pango_fc_font_get_unknown_glyph (fc_font, c);
+ pango_font_get_glyph_extents (pango_font, g->glyph, NULL,
+ &logical_rect);
+ g->geometry.width = logical_rect.width;
+ }
+ g->geometry.x_offset = 0;
+ g->geometry.y_offset = 0;
+ }
+ g->attr.is_cluster_start
+ = (i == 0
+ || m_glyphs[i - 1].from != m_glyphs[i].from);
+ glyphs->log_clusters[i] = offsets[m_glyphs[i].from];
+ }
+
+ m17n_object_unref (mt);
+ free (font);
+}
+
+/* Check if PANGO_FONT is suitable for the character WC. */
+
+static PangoCoverageLevel
+m17n_fc_engine_covers (PangoEngineShape *engine,
+ PangoFont *pango_font,
+ PangoLanguage *pango_language,
+ gunichar wc)
+{
+ static gunichar last_wc = 0;
+ /* Symbols for character property `script'. */
+ static MSymbol Mlatin, Mcommon, Minherited;
+ PangoCoverage *coverage;
+ PangoCoverageLevel result;
+ PangoFcFont *fc_font;
+ char *fontname;
+ MFont *font;
+ MSymbol script, language;
+ int check_result;
+
+ if (! Mlatin)
+ {
+ Mlatin = msymbol ("latin");
+ Mcommon = msymbol ("common");
+ Minherited = msymbol ("inherited");
+ }
+
+ if (debug_level > 0 && wc != last_wc)
+ {
+ g_debug ("covers for U+%04X", wc);
+ last_wc = wc;
+ }
+
+ coverage = pango_font_get_coverage (pango_font, pango_language);
+ result = pango_coverage_get (coverage, wc);
+ pango_coverage_unref (coverage);
+
+ if (result == PANGO_COVERAGE_NONE)
+ {
+ if (debug_level > 0)
+ {
+ fc_font = PANGO_FC_FONT (pango_font);
+ fontname = (char *) FcNameUnparse (fc_font->font_pattern);
+ font = mfont_parse_name (fontname, Mfontconfig);
+ g_debug (" %s none",
+ msymbol_name (mfont_get_prop (font, Mfamily)));
+ free (fontname);
+ free (font);
+ }
+ return result;
+ }
+
+ fc_font = PANGO_FC_FONT (pango_font);
+ fontname = (char *) FcNameUnparse (fc_font->font_pattern);
+ font = mfont_parse_name (fontname, Mfontconfig);
+
+ if (wc < 0x100)
+ script = Mlatin;
+ else
+ {
+ script = mchar_get_prop ((int) wc, Mscript);
+ if (script == Mcommon || script == Minherited)
+ script = mchar_get_prop ((int) wc, msymbol ("block"));
+ }
+ language = m17n_fc_get_language (pango_language);
+
+ check_result = mfont_check (frame, NULL, script, language, font);
+ if (debug_level > 0)
+ {
+ char *result_text = (check_result == 2 ? "exact"
+ : check_result == 1 ? "approximate"
+ : "fallback");
+
+ g_debug (" (%s,%s): %s %s",
+ (script ? msymbol_name (script) : ""),
+ (language ? msymbol_name (language) : ""),
+ msymbol_name (mfont_get_prop (font, Mfamily)),
+ result_text);
+ }
+
+ free (fontname);
+ free (font);
+ return (check_result == 2 ? PANGO_COVERAGE_EXACT
+ : check_result == 1 ? PANGO_COVERAGE_APPROXIMATE
+ : PANGO_COVERAGE_FALLBACK);
+}
+
+static void
+m17n_engine_fc_class_init (PangoEngineShapeClass *class)
+{
+ class->script_shape = m17n_fc_engine_shape;
+ class->covers = m17n_fc_engine_covers;
+}
+
+PANGO_ENGINE_SHAPE_DEFINE_TYPE (M17NEngineFc, m17n_engine_fc,
+ m17n_engine_fc_class_init, NULL)
+
+void
+PANGO_MODULE_ENTRY(init) (GTypeModule *module)
+{
+ m17n_engine_fc_register_type (module);
+
+ M17N_INIT ();
+ init_module ();
+}
+
+void
+PANGO_MODULE_ENTRY(exit) (void)
+{
+ fini_module ();
+ M17N_FINI ();
+}
+
+void
+PANGO_MODULE_ENTRY(list) (PangoEngineInfo **engines,
+ int *n_engines)
+{
+ *engines = script_engines;
+ *n_engines = G_N_ELEMENTS (script_engines);
+}
+
+PangoEngine *
+PANGO_MODULE_ENTRY(create) (const char *id)
+{
+ return (!strcmp (id, SCRIPT_ENGINE_NAME)
+ ? g_object_new (m17n_engine_fc_type, NULL)
+ : NULL);
+}
projects / m17n / m17n-pango.git / commitdiff