\r\r\n line breaks are now \r\n. (Which means they'll be \n on Unix

sandboxes, and \r\n on Windows sandboxes, which is what you want.)
master
dchandler 20 years ago
parent 074adbf06a
commit 63757c30c1
  1. 488
      ReadMe.Txt
  2. 872
      opl_license.txt
  3. 92
      thdl_license.txt
  4. 144
      thdl_rationale.html
  5. 2012
      tibwn.ini

@ -1,244 +1,244 @@
************************************************************************
* INSTRUCTIONS FOR WYLIE WORD VERSION 1.0 *
* MS Word Macro for Windows *
* Written by Than Garson *
* Samantabhadra Project, UVa *
* September, 2001 *
************************************************************************
ACKNOWLEDGEMENTS:
The public domain Tibetan fonts provided in this package
have been made available through the gracious donations of the Tibetan Computer
Company and the Trace Foundation. All other material is the result of the
collaborative efforts of the Tibetan and Himalayan Digital Library.
Web-sites: http://faculty.virginia.edu/tibet-initiative/library/frameset.html
http://jefferson.village.virginia.edu/tibet/
LICENSE INFO:
The contents of this file are subject to the THDL Open Community License
Version 1.0 (the "License"); you may not use this file except in compliance
with the License. The license is included in this Zip archive, or you may
obtain a copy of the License on the THDL web site (http://www.thdl.org/).
Software distributed under the License is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied. See the
License for the specific terms governing rights and limitations under the
License.
The Initial Developer of this software is the Tibetan and Himalayan Digital
Library (THDL). Portions created by the THDL are Copyright 2001 THDL.
All Rights Reserved.
ABOUT WYLIE WORD 1.0:
This Zip file contains all the necessary files you will need to install and run
the Wylie Word macro for Microsoft Word, EXCEPT the font files which are available
for free download from the Tibetan and Himalayan Digital Library's tools page.
This document describes three aspects of the Wylie Word macro: I. Installation,
II. Fonts, III. How to Use the Macro.
I. INSTALLATION
The Zip archive contains the following files:
1. Extended Wylie Scheme-rev.doc - This is a Word document that contains
the latest extended Wylie transliteration scheme (6/10/2001), as
used by the Tibetan and Himalayan Digital Library and proposed by
the Library as a draft for a standard transliteration scheme. The
Wylie Word program uses this scheme with a slight modification for
entering Sanskrit stacks.
2. wywrd1.dot - This is a Word document template that actually houses
the macro. It can be used in a number of ways.
a. Stored on your hard drive it will act like a regular document and
the macro can be run only from within this document.
b. If it is placed in the templates folder for MS Word, it will act
as a standard template and will be one of the options available
when you choose New under the File menu. The macro will only be
runnable from within documents that use this template. To set this
up, put the wywrd1.dot file in the following folder, assuming "C"
is your hard drive:
C:\Windows\Application Data\Microsoft\Templates
c. If it is placed in the start up folder, the macro will be available
from ANY word document, since it is loaded the minute you start word.
To do this, put the WyEd2.2b.dot file in the following folder:
C:\Program Files\Office\StartUp
or, if you are networked,
C:\WINDOWS\All Users\Start Menu\Programs\StartUp
3. tibwn.ini - This is the data file that is used to convert the extended Wylie
to the Tibetan fonts. It needs to reside at the root level of your
primary hard drive, such as C:. Not in any folder. This way wherever
the document it is knows where to fide it and can read the necessary
information.
II. FONTS
The macro is written so that it can be used with any font as long as that fonts
code pages are avaialable. In this first release, we have included the most useful
font, Tibetan Machine Web, because this font is available for download free from the
THDL's tools page and because it is a cross-platform, web-usable font that should
significantly ease the transfer of data in Tibetan script. The Tibetan Machine Web
font is actually a set of fonts made public-domain through the collaboration between
the Tibetan Computer Company, the Trace Organization, and the THDL. Other fonts may
be added, though our ultimate goal is to utilize a public-domain Unicode Tibetan font,
once such a font is available. There are ten font files: "timwn.ttf" through "timwn9.ttf".
They can be downloaded from the tools section of the Tibetan and Himalayan Digital Library at:
(http://faculty.virginia.edu/tibet-initiative/library/frameset.html).
All ten files must be installed in your font folder, which is contained within the
control panel. To install the fonts, first unpack them into a temporary folder.
Then, under the Start menu, choose Settings and then Control Panel and click on
the Font option. From the Font folder window, click on the File menu and choose
Install New Font. With the resulting pop-up window navigate to the temporary folder,
where the Fonts were unpacked, and choose all 10 fonts. When you click OK, they will
be installed in your font folder.
III. USING THE MACRO
The Wylie Word macro is very simple to use, provided one is familiar with
the extended Wylie transliteration scheme. When the wywrd1.dot file is opened in any
of the ways described above, a new menu will appear between the Table and the Window menus.
It is labelled Tibetan. It gives you the following options:
A. Type Tibetan with Wylie (F8): Converts Wylie to Tibetan font as it is typed in.
B. Convert Wylie to Tibetan (F9): Converts already-typed in and highlighted Wylie to Tibetan.
C. Insert English in Tibetan (F7): Changes to the default English font and size, positioning
it so that it is in line with the Tibetan.
D. Adjust Preferences (Ctrl+Alt+Shift P): Brings up the preference form that provides you with
a number of changeable features, discussed below.
Each of these will be discussed in turn.
A. Type Tibetan with Wylie (F8):
1. Starting the macro
Choosing the Tibetan option begins running the macro. One can also start the macro by
typing CTRL + F8. At this point, one can type in standard Wylie and the corresponding
Tibetan glyphs should appear. Standard Tibetan stacks will be created automatically
as one types. For non-Standard, Sanskrit stacks, see 3. below. The macro will continue
running if you use the navigational arrows, the home or end key, page-up or down, delete
or backspace, Enter, Ctrl S to save, Ctrl A to select all, Ctrl P to print. However, the
macro will stop once you use the mouse or press the ESC key. The ESC key will automatically
set the font back to the default English font. Once either the mouse is used or the ESC key
is pressed, the program will need to be restarted if you wish to return to typing Tibetan.
2. Common Sanskrit-derived Glyphs
Common, stand-alone transliterations of Sanskrit letters are generally accessible by
using capitals. That is, for the reverse Tibetan 'da' which represents the retroflex
'da' in Sanskrit, type capital D. For long vowels, such as long a, type capital A;
long i, type capital I; and so forth. Thus, "dakini" would be "DAkinI".
3. Non-Standard Sanskrit-derived Stacks
To achieve the less-common stacks that are the result of Sanskrit transliteration,
the method is also outlined in the transliteration scheme. This is an easy and
unambiguous way to enter unusual Tibetan stacks that represent Sanskrit characters.
The method is to use the "+" key, placing a plus sign between each letter of the stack.
Thus, the word "sattva" would be typed in as "sat+t+wa" (There is no "v" in Tibetan.
"w" is always used instead!") and "samuccaya" would be "samuts+tsaya" (The "ts", "tsh",
and "dz" are used to transcribe the Sanskrit palatals "c", "ch", and "j".)
4. Punctuation
WyEd2.3 allows for the use of Western punctuation interspersed with Tibetan. Common
Tibetan punctuation remains the same:
(space) - tshek
_ (underscore) - (white space)
/ (slash) - shad
However, the parentheses (), the brackets [], the colon :, and the quotation marks "" all will
appear in their Latin-font glyphs in line with the Tibetan. To obtain, the Tibetan symbol that
any of these represent in the Transliteration Scheme, use the Sanskrit stack window.
B. Convert Wylie to Tibetan (F9)
This option allows for the conversion of already typed in Wylie. To use it, the Wylie first needs to be
highlighted, then one chooses this option either by pressing F9 or from the menu. The program
will REPLACE the highlighted Wylie with the corresponding glyphs from the Tibetan font.
C. Insert English in Tibetan (F7)
This option allows for the insertion of English font within a Tibetan line. This is necessary
because of the nature of the font. As Tibetan glyphs in general require more line height, their base
line is raise to provide more room. As a result, Tibetan glyphs appear raised when next to a Latin-
based font. This is solved by adjusting the relative position of the English or Tibetan. In the
preference form discussed below, one can choose whether to have the Tibetan font be base-line (that is,
the document is primarily Tibetan with English interspersed) or English base-line (where the docuement
is primarily English with Tibetan inserted). In either case, choosing this option will adjust the
relative height of the insertion point so that the English entered will be in line with the Tibetan.
(NOTE: This will work only if the base-line option is the same for both fonts. One does NOT want to
type in Tibetan, then switch the base-line option, and then type in English. If the base-line option
remains the same, the fonts should be in line. Slight variations between fonts and computers can be
adjusted through the preferences window.)
D. Adjust Preferences (Ctrl+Alt+Shift P)
The final option in the menu allows one to adjust the preferences for the macro. These are written as
an ini file to the hard drive in the root directory (e.g., C:\weprefs.ini). If the file is not found,
the macro will automatically create it and update it as changes to the preferences are made. The
following is an explanation of each item in the preference window:
Tibetan Font: TibetanMachineWeb -- At the moment this cannot be changed. The only font that works with
this program is that font.
Size: 22 -- This is the default size of the Tibetan font when the macro is used. It can be changed
according to one's needs. Of course, once entered the size of the Tibetan font can be
changed as one would any font.
Position: 0 -- This is the relative vertical position of the Tibetan character glyphs above (+) or
below (-) what Word considers to be the base line in points. 0 is the position that fonts
normally appear in. However, next to a Latin-font also at position 0, the Tibetan font
will appear below or subscripted in comparison with the Latin-font. Thus, to insert
Tibetan into already extant English, it needs to be raised 6pts. Conversely, English
within base-line Tibetan, needs to be lowered by 6pts or -6.
English Font: Times New Roman
&
Size: 12 -- These represent the default English font. They can both be changed by clicking on the
"Choose English Font" button. The size can also be changed manually in the corresponding
box.
Position: 6 -- This is the relative vertical position of the English font in comparison to the Tibetan.
If the Tibetan and English do not appear in line on your computer, minor adjustments
can be made by changing these two position values.
Tibetan Base-line or English Base-line --
These two toggle buttons provide the user with different options according to whether
one wants primarily to enter Tibetan with English inserted within it (Tibetan Base-line)
or one wants to enter English with Tibetan inserted within it (English Base-line).
Whichever font is considered to be the base-line will have a vertical position of 0 and
the other font will be correspondingly raised or lowered to be in-line with the
base-line. Thus, with Tibetan Base-line the default is Tibetan position 0 and
English position -6. If English Base-line is chosen, these are switched so that Tibetan
position is 6 and the English position is 0.
Punctuation (followed by a list box) -- This option allows the user to indicate which punctuation
marks are to remain in the English default font. In general, all the punctuation
marks available on the standard keyboard are used to transliterate a Tibetan punctuation
mark. However, as many of these marks are used very rarely while many of the "English"
punctuation marks are used with the Tibetan font--quotation marks, colon, parentheses,
etc.--any of the marks on this list will remain in their "English" form. The list comes
with the following punctuation marks as its default: ()"[]:?!_<>
Marks can be added to the list by clicking on the label "Puncutation:". The user will
then be prompted for the mark to be added.
Marks can be deleted from the list by scrolling to that particular mark on the list
and clicking on it. The program will then ask if that is the mark one wants to remove.
Size: 16 -- This indicates the size of the puncutation marks that remain in the English default font.
Because the Tibetan font needs to be larger in size to be readable, inserted "English"
punctuation needs to be slightly larger than the default English size, if used with
Tibetan, i.e., quotes or parentheses around a Tibetan phrase. This number can be adjusted
according to the user's needs.
Position: -8 -- This is the relative vertical position of the inserted punctuation marks and can be
adjusted according to the user's needs. Note that the punctuation position will be
lowered or raised automatically when either Tibetan-base line or English-base line is
chosen.
************************************************************************
* INSTRUCTIONS FOR WYLIE WORD VERSION 1.0 *
* MS Word Macro for Windows *
* Written by Than Garson *
* Samantabhadra Project, UVa *
* September, 2001 *
************************************************************************
ACKNOWLEDGEMENTS:
The public domain Tibetan fonts provided in this package
have been made available through the gracious donations of the Tibetan Computer
Company and the Trace Foundation. All other material is the result of the
collaborative efforts of the Tibetan and Himalayan Digital Library.
Web-sites: http://faculty.virginia.edu/tibet-initiative/library/frameset.html
http://jefferson.village.virginia.edu/tibet/
LICENSE INFO:
The contents of this file are subject to the THDL Open Community License
Version 1.0 (the "License"); you may not use this file except in compliance
with the License. The license is included in this Zip archive, or you may
obtain a copy of the License on the THDL web site (http://www.thdl.org/).
Software distributed under the License is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied. See the
License for the specific terms governing rights and limitations under the
License.
The Initial Developer of this software is the Tibetan and Himalayan Digital
Library (THDL). Portions created by the THDL are Copyright 2001 THDL.
All Rights Reserved.
ABOUT WYLIE WORD 1.0:
This Zip file contains all the necessary files you will need to install and run
the Wylie Word macro for Microsoft Word, EXCEPT the font files which are available
for free download from the Tibetan and Himalayan Digital Library's tools page.
This document describes three aspects of the Wylie Word macro: I. Installation,
II. Fonts, III. How to Use the Macro.
I. INSTALLATION
The Zip archive contains the following files:
1. Extended Wylie Scheme-rev.doc - This is a Word document that contains
the latest extended Wylie transliteration scheme (6/10/2001), as
used by the Tibetan and Himalayan Digital Library and proposed by
the Library as a draft for a standard transliteration scheme. The
Wylie Word program uses this scheme with a slight modification for
entering Sanskrit stacks.
2. wywrd1.dot - This is a Word document template that actually houses
the macro. It can be used in a number of ways.
a. Stored on your hard drive it will act like a regular document and
the macro can be run only from within this document.
b. If it is placed in the templates folder for MS Word, it will act
as a standard template and will be one of the options available
when you choose New under the File menu. The macro will only be
runnable from within documents that use this template. To set this
up, put the wywrd1.dot file in the following folder, assuming "C"
is your hard drive:
C:\Windows\Application Data\Microsoft\Templates
c. If it is placed in the start up folder, the macro will be available
from ANY word document, since it is loaded the minute you start word.
To do this, put the WyEd2.2b.dot file in the following folder:
C:\Program Files\Office\StartUp
or, if you are networked,
C:\WINDOWS\All Users\Start Menu\Programs\StartUp
3. tibwn.ini - This is the data file that is used to convert the extended Wylie
to the Tibetan fonts. It needs to reside at the root level of your
primary hard drive, such as C:. Not in any folder. This way wherever
the document it is knows where to fide it and can read the necessary
information.
II. FONTS
The macro is written so that it can be used with any font as long as that fonts
code pages are avaialable. In this first release, we have included the most useful
font, Tibetan Machine Web, because this font is available for download free from the
THDL's tools page and because it is a cross-platform, web-usable font that should
significantly ease the transfer of data in Tibetan script. The Tibetan Machine Web
font is actually a set of fonts made public-domain through the collaboration between
the Tibetan Computer Company, the Trace Organization, and the THDL. Other fonts may
be added, though our ultimate goal is to utilize a public-domain Unicode Tibetan font,
once such a font is available. There are ten font files: "timwn.ttf" through "timwn9.ttf".
They can be downloaded from the tools section of the Tibetan and Himalayan Digital Library at:
(http://faculty.virginia.edu/tibet-initiative/library/frameset.html).
All ten files must be installed in your font folder, which is contained within the
control panel. To install the fonts, first unpack them into a temporary folder.
Then, under the Start menu, choose Settings and then Control Panel and click on
the Font option. From the Font folder window, click on the File menu and choose
Install New Font. With the resulting pop-up window navigate to the temporary folder,
where the Fonts were unpacked, and choose all 10 fonts. When you click OK, they will
be installed in your font folder.
III. USING THE MACRO
The Wylie Word macro is very simple to use, provided one is familiar with
the extended Wylie transliteration scheme. When the wywrd1.dot file is opened in any
of the ways described above, a new menu will appear between the Table and the Window menus.
It is labelled Tibetan. It gives you the following options:
A. Type Tibetan with Wylie (F8): Converts Wylie to Tibetan font as it is typed in.
B. Convert Wylie to Tibetan (F9): Converts already-typed in and highlighted Wylie to Tibetan.
C. Insert English in Tibetan (F7): Changes to the default English font and size, positioning
it so that it is in line with the Tibetan.
D. Adjust Preferences (Ctrl+Alt+Shift P): Brings up the preference form that provides you with
a number of changeable features, discussed below.
Each of these will be discussed in turn.
A. Type Tibetan with Wylie (F8):
1. Starting the macro
Choosing the Tibetan option begins running the macro. One can also start the macro by
typing CTRL + F8. At this point, one can type in standard Wylie and the corresponding
Tibetan glyphs should appear. Standard Tibetan stacks will be created automatically
as one types. For non-Standard, Sanskrit stacks, see 3. below. The macro will continue
running if you use the navigational arrows, the home or end key, page-up or down, delete
or backspace, Enter, Ctrl S to save, Ctrl A to select all, Ctrl P to print. However, the
macro will stop once you use the mouse or press the ESC key. The ESC key will automatically
set the font back to the default English font. Once either the mouse is used or the ESC key
is pressed, the program will need to be restarted if you wish to return to typing Tibetan.
2. Common Sanskrit-derived Glyphs
Common, stand-alone transliterations of Sanskrit letters are generally accessible by
using capitals. That is, for the reverse Tibetan 'da' which represents the retroflex
'da' in Sanskrit, type capital D. For long vowels, such as long a, type capital A;
long i, type capital I; and so forth. Thus, "dakini" would be "DAkinI".
3. Non-Standard Sanskrit-derived Stacks
To achieve the less-common stacks that are the result of Sanskrit transliteration,
the method is also outlined in the transliteration scheme. This is an easy and
unambiguous way to enter unusual Tibetan stacks that represent Sanskrit characters.
The method is to use the "+" key, placing a plus sign between each letter of the stack.
Thus, the word "sattva" would be typed in as "sat+t+wa" (There is no "v" in Tibetan.
"w" is always used instead!") and "samuccaya" would be "samuts+tsaya" (The "ts", "tsh",
and "dz" are used to transcribe the Sanskrit palatals "c", "ch", and "j".)
4. Punctuation
WyEd2.3 allows for the use of Western punctuation interspersed with Tibetan. Common
Tibetan punctuation remains the same:
(space) - tshek
_ (underscore) - (white space)
/ (slash) - shad
However, the parentheses (), the brackets [], the colon :, and the quotation marks "" all will
appear in their Latin-font glyphs in line with the Tibetan. To obtain, the Tibetan symbol that
any of these represent in the Transliteration Scheme, use the Sanskrit stack window.
B. Convert Wylie to Tibetan (F9)
This option allows for the conversion of already typed in Wylie. To use it, the Wylie first needs to be
highlighted, then one chooses this option either by pressing F9 or from the menu. The program
will REPLACE the highlighted Wylie with the corresponding glyphs from the Tibetan font.
C. Insert English in Tibetan (F7)
This option allows for the insertion of English font within a Tibetan line. This is necessary
because of the nature of the font. As Tibetan glyphs in general require more line height, their base
line is raise to provide more room. As a result, Tibetan glyphs appear raised when next to a Latin-
based font. This is solved by adjusting the relative position of the English or Tibetan. In the
preference form discussed below, one can choose whether to have the Tibetan font be base-line (that is,
the document is primarily Tibetan with English interspersed) or English base-line (where the docuement
is primarily English with Tibetan inserted). In either case, choosing this option will adjust the
relative height of the insertion point so that the English entered will be in line with the Tibetan.
(NOTE: This will work only if the base-line option is the same for both fonts. One does NOT want to
type in Tibetan, then switch the base-line option, and then type in English. If the base-line option
remains the same, the fonts should be in line. Slight variations between fonts and computers can be
adjusted through the preferences window.)
D. Adjust Preferences (Ctrl+Alt+Shift P)
The final option in the menu allows one to adjust the preferences for the macro. These are written as
an ini file to the hard drive in the root directory (e.g., C:\weprefs.ini). If the file is not found,
the macro will automatically create it and update it as changes to the preferences are made. The
following is an explanation of each item in the preference window:
Tibetan Font: TibetanMachineWeb -- At the moment this cannot be changed. The only font that works with
this program is that font.
Size: 22 -- This is the default size of the Tibetan font when the macro is used. It can be changed
according to one's needs. Of course, once entered the size of the Tibetan font can be
changed as one would any font.
Position: 0 -- This is the relative vertical position of the Tibetan character glyphs above (+) or
below (-) what Word considers to be the base line in points. 0 is the position that fonts
normally appear in. However, next to a Latin-font also at position 0, the Tibetan font
will appear below or subscripted in comparison with the Latin-font. Thus, to insert
Tibetan into already extant English, it needs to be raised 6pts. Conversely, English
within base-line Tibetan, needs to be lowered by 6pts or -6.
English Font: Times New Roman
&
Size: 12 -- These represent the default English font. They can both be changed by clicking on the
"Choose English Font" button. The size can also be changed manually in the corresponding
box.
Position: 6 -- This is the relative vertical position of the English font in comparison to the Tibetan.
If the Tibetan and English do not appear in line on your computer, minor adjustments
can be made by changing these two position values.
Tibetan Base-line or English Base-line --
These two toggle buttons provide the user with different options according to whether
one wants primarily to enter Tibetan with English inserted within it (Tibetan Base-line)
or one wants to enter English with Tibetan inserted within it (English Base-line).
Whichever font is considered to be the base-line will have a vertical position of 0 and
the other font will be correspondingly raised or lowered to be in-line with the
base-line. Thus, with Tibetan Base-line the default is Tibetan position 0 and
English position -6. If English Base-line is chosen, these are switched so that Tibetan
position is 6 and the English position is 0.
Punctuation (followed by a list box) -- This option allows the user to indicate which punctuation
marks are to remain in the English default font. In general, all the punctuation
marks available on the standard keyboard are used to transliterate a Tibetan punctuation
mark. However, as many of these marks are used very rarely while many of the "English"
punctuation marks are used with the Tibetan font--quotation marks, colon, parentheses,
etc.--any of the marks on this list will remain in their "English" form. The list comes
with the following punctuation marks as its default: ()"[]:?!_<>
Marks can be added to the list by clicking on the label "Puncutation:". The user will
then be prompted for the mark to be added.
Marks can be deleted from the list by scrolling to that particular mark on the list
and clicking on it. The program will then ask if that is the mark one wants to remove.
Size: 16 -- This indicates the size of the puncutation marks that remain in the English default font.
Because the Tibetan font needs to be larger in size to be readable, inserted "English"
punctuation needs to be slightly larger than the default English size, if used with
Tibetan, i.e., quotes or parentheses around a Tibetan phrase. This number can be adjusted
according to the user's needs.
Position: -8 -- This is the relative vertical position of the inserted punctuation marks and can be
adjusted according to the user's needs. Note that the punctuation position will be
lowered or raised automatically when either Tibetan-base line or English-base line is
chosen.

@ -1,436 +1,436 @@
OPEN PUBLIC LICENSE
Version 1.0
1. Definitions.
1.1. "Contributor" means each entity that creates or contributes to
the creation of Modifications.
1.2. "Contributor Version" means the combination of the Original
Code, prior Modifications used by a Contributor, and the
Modifications made by that particular Contributor.
1.3. "Covered Code" means the Original Code or Modifications or the
combination of the Original Code and Modifications, in each case
including portions thereof.
1.4. "Electronic Distribution Mechanism" means a mechanism
generally accepted in the software development community for the
electronic transfer of data.
1.5. "Executable" means Covered Code in any form other than Source
Code.
1.6. "Initial Developer" means the individual or entity identified
as the Initial Developer in the Source Code notice required by
Exhibit A.
1.7. "Larger Work" means a work, which combines Covered Code or
portions thereof with code not governed by the terms of this
License.
1.8. "License" means this document and the corresponding addendum
described in section 6.4 below.
1.9. "Modifications" means any addition to or deletion from the
substance or structure of either the Original Code or any previous
Modifications. When Covered Code is released as a series of files,
a Modification is:
A. Any addition to or deletion from the contents of a file
containing Original Code or previous Modifications.
B. Any new file that contains any part of the Original Code
or previous Modifications.
1.10. "Original Code" means Source Code of computer software code
which is described in the Source Code notice required by Exhibit A
as Original Code, and which, at the time of its release under this
License is not already Covered Code governed by this License.
1.11. "Source Code" means the preferred form of the Covered Code
for making modifications to it, including all modules it contains,
plus any associated interface definition files, scripts used to
control compilation and installation of an Executable, or a list of
source code differential comparisons against either the Original
Code or another well known, available Covered Code of the
Contributor's choice. The Source Code can be in a compressed or
archival form, provided the appropriate decompression or
de-archiving software is widely available for no charge.
1.12. "You" means an individual or a legal entity exercising rights
under, and complying with all of the terms of, this License or a
future version of this License issued under Section 6.1. For legal
entities, "You'' includes any entity which controls, is controlled
by, or is under common control with You. For purposes of this
definition, "control'' means (a) the power, direct or indirect, to
cause the direction or management of such entity, whether by
contract or otherwise, or (b) ownership of fifty percent (50%) or
more of the outstanding shares or beneficial ownership of such
entity.
1.13 "License Author" means Lutris Technologies, Inc.
2. Source Code License.
2.1. The Initial Developer Grant.
The Initial Developer hereby grants You a worldwide, royalty-free,
non-exclusive license, subject to third party intellectual property
claims:
(a) under intellectual property rights (other than patent or
trademark) to use, reproduce, modify, display, perform,
sublicense and distribute the Original Code (or portions
thereof) with or without Modifications, or as part of a
Larger Work; and
(b) under patents now or hereafter owned or controlled by
Initial Developer, to make, have made, use and sell (``offer
to sell and import'') the Original Code (or portions
thereof), but solely to the extent that any such patent is
reasonably necessary to enable You to Utilize the Original
Code (or portions thereof) and not to any greater extent
that may be necessary to Utilize further Modifications or
combinations.
2.2. Contributor Grant.
Each Contributor hereby grants You a worldwide, royalty-free,
non-exclusive license, subject to third party intellectual property
claims:
(a) under intellectual property rights (other than patent or
trademark) to use, reproduce, modify, display, perform,
sublicense and distribute the Modifications created by such
Contributor (or portions thereof) either on an unmodified
basis, with other Modifications, as Covered Code or as part
of a Larger Work; and
(b) under patents now or hereafter owned or controlled by
Contributor, to to make, have made, use and sell (``offer to
sell and import'') the Contributor Version (or portions
thereof), but solely to the extent that any such patent is
reasonably necessary to enable You to Utilize the
Contributor Version (or portions thereof), and not to any
greater extent that may be necessary to Utilize further
Modifications or combinations
3. Distribution Obligations.
3.1. Application of License.
The Modifications which You create or to which You contribute are
governed by the terms of this License, including without limitation
Section 2.2. The Source Code version of Covered Code may be
distributed only under the terms of this License or a future
version of this License released under Section 6.1, and You must
include a copy of this License with every copy of the Source Code
You distribute. You may not offer or impose any terms on any Source
Code version that alters or restricts the applicable version of
this License or the recipients' rights hereunder. However, You may
include an additional document offering the additional rights
described in Section 3.5.
3.2. Availability of Source Code.
Any Modification which You create or to which You contribute must
be made available, prior to any use, except for internal
development and practice, in Source Code form under the terms of
this License either on the same media as an Executable version or
via an accepted Electronic Distribution Mechanism to anyone to whom
you made an Executable version available; and if made available via
Electronic Distribution Mechanism, must remain available for at
least twelve (12) months after the date it initially became
available, or at least six (6) months after a subsequent version of
that particular Modification has been made available to such
recipients. You shall notify the Initial Developer of the
Modification and the location of the Source Code via the contact
means provided for in the Developer Specific license. Initial
Developer will be acting as maintainer of the Source Code and may
provide an Electronic Distribution mechanism for the Modification
to be made available.
3.3. Description of Modifications.
You must cause all Covered Code to which you contribute to contain
a file documenting the changes You made to create that Covered Code
and the date of any change. You must include a prominent statement
that the Modification is derived, directly or indirectly, from
Original Code provided by the Initial Developer and including the
name of the Initial Developer in (a) the Source Code, and (b) in
any notice in an Executable version or related documentation in
which You describe the origin or ownership of the Covered Code.
3.4. Intellectual Property Matters
(a) Third Party Claims.
If You have knowledge that a party claims an intellectual
property right in particular functionality or code (or its
utilization under this License), you must include a text
file with the source code distribution titled "LEGAL" which
describes the claim and the party making the claim in
sufficient detail that a recipient will know whom to
contact. If you obtain such knowledge after You make Your
Modification available as described in Section 3.2, You
shall promptly modify the LEGAL file in all copies You make
available thereafter and shall take other steps (such as
notifying appropriate mailing lists or newsgroups)
reasonably calculated to inform those who received the
Covered Code that new knowledge has been obtained.
(b) Representations.
Contributor represents that, except as disclosed pursuant to
Section 3.4(a) above, Contributor believes that
Contributor's Modifications are Contributor's original
creation(s) and/or Contributor has sufficient rights to
grant the rights conveyed by this License.
3.5. Required Notices.
You must duplicate the notice in Exhibit A in each file of the
Source Code, and this License in any documentation for the Source
Code, where You describe recipients' rights relating to Covered
Code. If You created one or more Modification(s), You may add your
name as a Contributor to the notice described in Exhibit A. If it
is not possible to put such notice in a particular Source Code file
due to its structure, then you must include such notice in a
location (such as a relevant directory file) where a user would be
likely to look for such a notice. You may choose to offer, and to
charge a fee for, warranty, support, indemnity or liability
obligations to one or more recipients of Covered Code. However, You
may do so only on Your own behalf, and not on behalf of the Initial
Developer or any Contributor. You must make it absolutely clear
that any such warranty, support, indemnity or liability obligation
is offered by You alone, and You hereby agree to indemnify the
Initial Developer and every Contributor for any liability incurred
by the Initial Developer or such Contributor as a result of
warranty, support, indemnity or liability terms You offer.
3.6. Distribution of Executable Versions.
You may distribute Covered Code in Executable form only if the
requirements of Section 3.1-3.5 have been met for that Covered
Code, and if You include a notice stating that the Source Code
version of the Covered Code is available under the terms of this
License, including a description of how and where You have
fulfilled the obligations of Section 3.2. The notice must be
conspicuously included in any notice in an Executable version,
related documentation or collateral in which You describe
recipients' rights relating to the Covered Code. You may distribute
the Executable version of Covered Code under a license of Your
choice, which may contain terms different from this License,
provided that You are in compliance with the terms of this License
and that the license for the Executable version does not attempt to
limit or alter the recipient's rights in the Source Code version
from the rights set forth in this License. If You distribute the
Executable version under a different license You must make it
absolutely clear that any terms which differ from this License are
offered by You alone, not by the Initial Developer or any
Contributor. You hereby agree to indemnify the Initial Developer
and every Contributor for any liability incurred by the Initial
Developer or such Contributor as a result of any such terms You
offer. If you distribute executable versions containing Covered
Code, you must reproduce the notice in Exhibit B in the
documentation and/or other materials provided with the product.
3.7. Larger Works.
You may create a Larger Work by combining Covered Code with other
code not governed by the terms of this License and distribute the
Larger Work as a single product. In such a case, You must make sure
the requirements of this License are fulfilled for the Covered
Code.
4. Inability to Comply Due to Statute or Regulation.
If it is impossible for You to comply with any of the terms of this
License with respect to some or all of the Covered Code due to
statute or regulation then You must: (a) comply with the terms of
this License to the maximum extent possible; and (b) Cite all of
the statutes or regulations that prohibit you from complying fully
with this license. (c) describe the limitations and the code they
affect. Such description must be included in the LEGAL file
described in Section 3.4 and must be included with all
distributions of the Source Code. Except to the extent prohibited
by statute or regulation, such description must be sufficiently
detailed for a recipient of ordinary skill to be able to understand
it.
5. Application of this License.
This License applies to code to which the Initial Developer has
attached the notice in Exhibit A, and to related Covered Code.
6. Versions of the License.
6.1. New Versions.
License Author may publish revised and/or new versions of the
License from time to time. Each version will be given a
distinguishing version number and shall be submitted to
opensource.org for certification.
6.2. Effect of New Versions.
Once Covered Code has been published under a particular version of
the License, You may always continue to use it under the terms of
that version. You may also choose to use such Covered Code under
the terms of any subsequent version of the License published by
Initial Developer. No one other than Initial Developer has the
right to modify the terms applicable to Covered Code created under
this License.
6.3. Derivative Works.
If you create or use a modified version of this License, except in
association with the required Developer Specific License described
in section 6.4, (which you may only do in order to apply it to code
which is not already Covered Code governed by this License), you
must (a) rename Your license so that the phrases ``Open'',
``OpenPL'', ``OPL'' or any confusingly similar phrase do not appear
anywhere in your license and (b) otherwise make it clear that your
version of the license contains terms which differ from the Open
Public License. (Filling in the name of the Initial Developer,
Original Code or Contributor in the notice described in Exhibit A
shall not of themselves be deemed to be modifications of this
License.)
6.4. Required Additional Developer Specific License
This license is a union of the following two parts that should be
found as text files in the same place (directory), in the order of
preeminence:
[1] A Developer specific license.
[2] The contents of this file OPL_1_0.TXT, stating the general
licensing policy of the software.
In case of conflicting dispositions in the parts of this license,
the terms of the lower-numbered part will always be superseded by
the terms of the higher numbered part.
7. DISCLAIMER OF WARRANTY.
COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS,
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING,
WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF
DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR
NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF
THE COVERED CODE IS WITH YOU. SHOULD ANY COVERED CODE PROVE
DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER
CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR
CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART
OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER
EXCEPT UNDER THIS DISCLAIMER.
8. TERMINATION.
8.1 Termination upon Breach
This License and the rights granted hereunder will terminate
automatically if You fail to comply with terms herein and fail to cure
such breach within 30 days of becoming aware of the breach. All
sublicenses to the Covered Code, which are properly granted, shall
survive any termination of this License. Provisions that, by their
nature, must remain in effect beyond the termination of this License
shall survive.
8.2. Termination Upon Litigation. If You initiate litigation by
asserting a patent infringement claim (excluding declatory judgment
actions) against Initial Developer or a Contributor (the Initial
Developer or Contributor against whom You file such action is referred
to as "Participant") alleging that:
(a) such Participant's Contributor Version directly or
indirectly infringes any patent, then any and all rights
granted by such Participant to You under Sections 2.1 and/or
2.2 of this License shall, upon 60 days notice from Participant
terminate prospectively, unless if within 60 days after receipt
of notice You either: (i) agree in writing to pay Participant a
mutually agreeable reasonable royalty for Your past and future
use of Modifications made by such Participant, or (ii) withdraw
Your litigation claim with respect to the Contributor Version
against such Participant. If within 60 days of notice, a
reasonable royalty and payment arrangement are not mutually
agreed upon in writing by the parties or the litigation claim
is not withdrawn, the rights granted by Participant to You
under Sections 2.1 and/or 2.2 automatically terminate at the
expiration of the 60 day notice period specified above.
(b) any software, hardware, or device, other than such
Participant's Contributor Version, directly or indirectly
infringes any patent, then any rights granted to You by such
Participant under Sections 2.1(b) and 2.2(b) are revoked
effective as of the date You first made, used, sold,
distributed, or had made, Modifications made by that
Participant.
8.3. If You assert a patent infringement claim against Participant
alleging that such Participant's Contributor Version directly or
indirectly infringes any patent where such claim is resolved (such as
by license or settlement) prior to the initiation of patent
infringement litigation, then the reasonable value of the licenses
granted by such Participant under Sections 2.1 or 2.2 shall be taken
into account in determining the amount or value of any payment or
license.
8.4. In the event of termination under Sections 8.1 or 8.2 above, all
end user license agreements (excluding distributors and resellers)
which have been validly granted by You or any distributor hereunder
prior to termination shall survive termination.
9. LIMITATION OF LIABILITY.
UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT
(INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE INITIAL
DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE,
OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO YOU OR ANY OTHER
PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF
GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND
ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE
BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF
LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY
RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW
PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE
EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO
THAT EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.
10. U.S. GOVERNMENT END USERS.
The Covered Code is a ``commercial item,'' as that term is defined in
48 C.F.R. 2.101 (Oct. 1995), consisting of ``commercial computer
software'' and ``commercial computer software documentation,'' as such
terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48
C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995),
all U.S. Government End Users acquire Covered Code with only those
rights set forth herein.
11. MISCELLANEOUS.
This section was intentionally left blank. The contents of this
section are found in the corresponding addendum described above.
12. RESPONSIBILITY FOR CLAIMS.
Except in cases where another Contributor has failed to comply with
Section 3.4, You are responsible for damages arising, directly or
indirectly, out of Your utilization of rights under this License,
based on the number of copies of Covered Code you made available, the
revenues you received from utilizing such rights, and other relevant
factors. You agree to work with affected parties to distribute with
Initial Developer responsibility on an equitable basis.
EXHIBIT A.
Text for this Exhibit A is found in the corresponding addendum,
described in section 6.4 above, text file provided by the Initial
Developer. This license is not valid or complete with out that
file.
EXHIBIT B.
Text for this Exhibit B is found in the corresponding addendum,
described in section 6.4 above, text file provided by the Initial
Developer. This license is not valid or complete with out that
file.
OPEN PUBLIC LICENSE
Version 1.0
1. Definitions.
1.1. "Contributor" means each entity that creates or contributes to
the creation of Modifications.
1.2. "Contributor Version" means the combination of the Original
Code, prior Modifications used by a Contributor, and the
Modifications made by that particular Contributor.
1.3. "Covered Code" means the Original Code or Modifications or the
combination of the Original Code and Modifications, in each case
including portions thereof.
1.4. "Electronic Distribution Mechanism" means a mechanism
generally accepted in the software development community for the
electronic transfer of data.
1.5. "Executable" means Covered Code in any form other than Source
Code.
1.6. "Initial Developer" means the individual or entity identified
as the Initial Developer in the Source Code notice required by
Exhibit A.
1.7. "Larger Work" means a work, which combines Covered Code or
portions thereof with code not governed by the terms of this
License.
1.8. "License" means this document and the corresponding addendum
described in section 6.4 below.
1.9. "Modifications" means any addition to or deletion from the
substance or structure of either the Original Code or any previous
Modifications. When Covered Code is released as a series of files,
a Modification is:
A. Any addition to or deletion from the contents of a file
containing Original Code or previous Modifications.
B. Any new file that contains any part of the Original Code
or previous Modifications.
1.10. "Original Code" means Source Code of computer software code
which is described in the Source Code notice required by Exhibit A
as Original Code, and which, at the time of its release under this
License is not already Covered Code governed by this License.
1.11. "Source Code" means the preferred form of the Covered Code
for making modifications to it, including all modules it contains,
plus any associated interface definition files, scripts used to
control compilation and installation of an Executable, or a list of
source code differential comparisons against either the Original
Code or another well known, available Covered Code of the
Contributor's choice. The Source Code can be in a compressed or
archival form, provided the appropriate decompression or
de-archiving software is widely available for no charge.
1.12. "You" means an individual or a legal entity exercising rights
under, and complying with all of the terms of, this License or a
future version of this License issued under Section 6.1. For legal
entities, "You'' includes any entity which controls, is controlled
by, or is under common control with You. For purposes of this
definition, "control'' means (a) the power, direct or indirect, to
cause the direction or management of such entity, whether by
contract or otherwise, or (b) ownership of fifty percent (50%) or
more of the outstanding shares or beneficial ownership of such
entity.
1.13 "License Author" means Lutris Technologies, Inc.
2. Source Code License.
2.1. The Initial Developer Grant.
The Initial Developer hereby grants You a worldwide, royalty-free,
non-exclusive license, subject to third party intellectual property
claims:
(a) under intellectual property rights (other than patent or
trademark) to use, reproduce, modify, display, perform,
sublicense and distribute the Original Code (or portions
thereof) with or without Modifications, or as part of a
Larger Work; and
(b) under patents now or hereafter owned or controlled by
Initial Developer, to make, have made, use and sell (``offer
to sell and import'') the Original Code (or portions
thereof), but solely to the extent that any such patent is
reasonably necessary to enable You to Utilize the Original
Code (or portions thereof) and not to any greater extent
that may be necessary to Utilize further Modifications or
combinations.
2.2. Contributor Grant.
Each Contributor hereby grants You a worldwide, royalty-free,
non-exclusive license, subject to third party intellectual property
claims:
(a) under intellectual property rights (other than patent or
trademark) to use, reproduce, modify, display, perform,
sublicense and distribute the Modifications created by such
Contributor (or portions thereof) either on an unmodified
basis, with other Modifications, as Covered Code or as part
of a Larger Work; and
(b) under patents now or hereafter owned or controlled by
Contributor, to to make, have made, use and sell (``offer to
sell and import'') the Contributor Version (or portions
thereof), but solely to the extent that any such patent is
reasonably necessary to enable You to Utilize the
Contributor Version (or portions thereof), and not to any
greater extent that may be necessary to Utilize further
Modifications or combinations
3. Distribution Obligations.
3.1. Application of License.
The Modifications which You create or to which You contribute are
governed by the terms of this License, including without limitation
Section 2.2. The Source Code version of Covered Code may be
distributed only under the terms of this License or a future
version of this License released under Section 6.1, and You must
include a copy of this License with every copy of the Source Code
You distribute. You may not offer or impose any terms on any Source
Code version that alters or restricts the applicable version of
this License or the recipients' rights hereunder. However, You may
include an additional document offering the additional rights
described in Section 3.5.
3.2. Availability of Source Code.
Any Modification which You create or to which You contribute must
be made available, prior to any use, except for internal
development and practice, in Source Code form under the terms of
this License either on the same media as an Executable version or
via an accepted Electronic Distribution Mechanism to anyone to whom
you made an Executable version available; and if made available via
Electronic Distribution Mechanism, must remain available for at
least twelve (12) months after the date it initially became
available, or at least six (6) months after a subsequent version of
that particular Modification has been made available to such
recipients. You shall notify the Initial Developer of the
Modification and the location of the Source Code via the contact
means provided for in the Developer Specific license. Initial
Developer will be acting as maintainer of the Source Code and may
provide an Electronic Distribution mechanism for the Modification
to be made available.
3.3. Description of Modifications.
You must cause all Covered Code to which you contribute to contain
a file documenting the changes You made to create that Covered Code
and the date of any change. You must include a prominent statement
that the Modification is derived, directly or indirectly, from
Original Code provided by the Initial Developer and including the
name of the Initial Developer in (a) the Source Code, and (b) in
any notice in an Executable version or related documentation in
which You describe the origin or ownership of the Covered Code.
3.4. Intellectual Property Matters
(a) Third Party Claims.
If You have knowledge that a party claims an intellectual
property right in particular functionality or code (or its
utilization under this License), you must include a text
file with the source code distribution titled "LEGAL" which
describes the claim and the party making the claim in
sufficient detail that a recipient will know whom to
contact. If you obtain such knowledge after You make Your
Modification available as described in Section 3.2, You
shall promptly modify the LEGAL file in all copies You make
available thereafter and shall take other steps (such as
notifying appropriate mailing lists or newsgroups)
reasonably calculated to inform those who received the
Covered Code that new knowledge has been obtained.
(b) Representations.
Contributor represents that, except as disclosed pursuant to
Section 3.4(a) above, Contributor believes that
Contributor's Modifications are Contributor's original
creation(s) and/or Contributor has sufficient rights to
grant the rights conveyed by this License.
3.5. Required Notices.
You must duplicate the notice in Exhibit A in each file of the
Source Code, and this License in any documentation for the Source
Code, where You describe recipients' rights relating to Covered
Code. If You created one or more Modification(s), You may add your
name as a Contributor to the notice described in Exhibit A. If it
is not possible to put such notice in a particular Source Code file
due to its structure, then you must include such notice in a
location (such as a relevant directory file) where a user would be
likely to look for such a notice. You may choose to offer, and to
charge a fee for, warranty, support, indemnity or liability
obligations to one or more recipients of Covered Code. However, You
may do so only on Your own behalf, and not on behalf of the Initial
Developer or any Contributor. You must make it absolutely clear
that any such warranty, support, indemnity or liability obligation
is offered by You alone, and You hereby agree to indemnify the
Initial Developer and every Contributor for any liability incurred
by the Initial Developer or such Contributor as a result of
warranty, support, indemnity or liability terms You offer.
3.6. Distribution of Executable Versions.
You may distribute Covered Code in Executable form only if the
requirements of Section 3.1-3.5 have been met for that Covered
Code, and if You include a notice stating that the Source Code
version of the Covered Code is available under the terms of this
License, including a description of how and where You have
fulfilled the obligations of Section 3.2. The notice must be
conspicuously included in any notice in an Executable version,
related documentation or collateral in which You describe
recipients' rights relating to the Covered Code. You may distribute
the Executable version of Covered Code under a license of Your
choice, which may contain terms different from this License,
provided that You are in compliance with the terms of this License
and that the license for the Executable version does not attempt to
limit or alter the recipient's rights in the Source Code version
from the rights set forth in this License. If You distribute the
Executable version under a different license You must make it
absolutely clear that any terms which differ from this License are
offered by You alone, not by the Initial Developer or any
Contributor. You hereby agree to indemnify the Initial Developer
and every Contributor for any liability incurred by the Initial
Developer or such Contributor as a result of any such terms You
offer. If you distribute executable versions containing Covered
Code, you must reproduce the notice in Exhibit B in the
documentation and/or other materials provided with the product.
3.7. Larger Works.
You may create a Larger Work by combining Covered Code with other
code not governed by the terms of this License and distribute the
Larger Work as a single product. In such a case, You must make sure
the requirements of this License are fulfilled for the Covered
Code.
4. Inability to Comply Due to Statute or Regulation.
If it is impossible for You to comply with any of the terms of this
License with respect to some or all of the Covered Code due to
statute or regulation then You must: (a) comply with the terms of
this License to the maximum extent possible; and (b) Cite all of
the statutes or regulations that prohibit you from complying fully
with this license. (c) describe the limitations and the code they
affect. Such description must be included in the LEGAL file
described in Section 3.4 and must be included with all
distributions of the Source Code. Except to the extent prohibited
by statute or regulation, such description must be sufficiently
detailed for a recipient of ordinary skill to be able to understand
it.
5. Application of this License.
This License applies to code to which the Initial Developer has
attached the notice in Exhibit A, and to related Covered Code.
6. Versions of the License.
6.1. New Versions.
License Author may publish revised and/or new versions of the
License from time to time. Each version will be given a
distinguishing version number and shall be submitted to
opensource.org for certification.
6.2. Effect of New Versions.
Once Covered Code has been published under a particular version of
the License, You may always continue to use it under the terms of
that version. You may also choose to use such Covered Code under
the terms of any subsequent version of the License published by
Initial Developer. No one other than Initial Developer has the
right to modify the terms applicable to Covered Code created under
this License.
6.3. Derivative Works.
If you create or use a modified version of this License, except in
association with the required Developer Specific License described
in section 6.4, (which you may only do in order to apply it to code
which is not already Covered Code governed by this License), you
must (a) rename Your license so that the phrases ``Open'',
``OpenPL'', ``OPL'' or any confusingly similar phrase do not appear
anywhere in your license and (b) otherwise make it clear that your
version of the license contains terms which differ from the Open
Public License. (Filling in the name of the Initial Developer,
Original Code or Contributor in the notice described in Exhibit A
shall not of themselves be deemed to be modifications of this
License.)
6.4. Required Additional Developer Specific License
This license is a union of the following two parts that should be
found as text files in the same place (directory), in the order of
preeminence:
[1] A Developer specific license.
[2] The contents of this file OPL_1_0.TXT, stating the general
licensing policy of the software.
In case of conflicting dispositions in the parts of this license,
the terms of the lower-numbered part will always be superseded by
the terms of the higher numbered part.
7. DISCLAIMER OF WARRANTY.
COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS,
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING,
WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF
DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR
NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF
THE COVERED CODE IS WITH YOU. SHOULD ANY COVERED CODE PROVE
DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER
CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR
CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART
OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER
EXCEPT UNDER THIS DISCLAIMER.
8. TERMINATION.
8.1 Termination upon Breach
This License and the rights granted hereunder will terminate
automatically if You fail to comply with terms herein and fail to cure
such breach within 30 days of becoming aware of the breach. All
sublicenses to the Covered Code, which are properly granted, shall
survive any termination of this License. Provisions that, by their
nature, must remain in effect beyond the termination of this License
shall survive.
8.2. Termination Upon Litigation. If You initiate litigation by
asserting a patent infringement claim (excluding declatory judgment
actions) against Initial Developer or a Contributor (the Initial
Developer or Contributor against whom You file such action is referred
to as "Participant") alleging that:
(a) such Participant's Contributor Version directly or
indirectly infringes any patent, then any and all rights
granted by such Participant to You under Sections 2.1 and/or
2.2 of this License shall, upon 60 days notice from Participant
terminate prospectively, unless if within 60 days after receipt
of notice You either: (i) agree in writing to pay Participant a
mutually agreeable reasonable royalty for Your past and future
use of Modifications made by such Participant, or (ii) withdraw
Your litigation claim with respect to the Contributor Version
against such Participant. If within 60 days of notice, a
reasonable royalty and payment arrangement are not mutually
agreed upon in writing by the parties or the litigation claim
is not withdrawn, the rights granted by Participant to You
under Sections 2.1 and/or 2.2 automatically terminate at the
expiration of the 60 day notice period specified above.
(b) any software, hardware, or device, other than such
Participant's Contributor Version, directly or indirectly
infringes any patent, then any rights granted to You by such
Participant under Sections 2.1(b) and 2.2(b) are revoked
effective as of the date You first made, used, sold,
distributed, or had made, Modifications made by that
Participant.
8.3. If You assert a patent infringement claim against Participant
alleging that such Participant's Contributor Version directly or
indirectly infringes any patent where such claim is resolved (such as
by license or settlement) prior to the initiation of patent
infringement litigation, then the reasonable value of the licenses
granted by such Participant under Sections 2.1 or 2.2 shall be taken
into account in determining the amount or value of any payment or
license.
8.4. In the event of termination under Sections 8.1 or 8.2 above, all
end user license agreements (excluding distributors and resellers)
which have been validly granted by You or any distributor hereunder
prior to termination shall survive termination.
9. LIMITATION OF LIABILITY.
UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT
(INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE INITIAL
DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE,
OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO YOU OR ANY OTHER
PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF
GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND
ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE
BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF
LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY
RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW
PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE
EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO
THAT EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.
10. U.S. GOVERNMENT END USERS.
The Covered Code is a ``commercial item,'' as that term is defined in
48 C.F.R. 2.101 (Oct. 1995), consisting of ``commercial computer
software'' and ``commercial computer software documentation,'' as such
terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48
C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995),
all U.S. Government End Users acquire Covered Code with only those
rights set forth herein.
11. MISCELLANEOUS.
This section was intentionally left blank. The contents of this
section are found in the corresponding addendum described above.
12. RESPONSIBILITY FOR CLAIMS.
Except in cases where another Contributor has failed to comply with
Section 3.4, You are responsible for damages arising, directly or
indirectly, out of Your utilization of rights under this License,
based on the number of copies of Covered Code you made available, the
revenues you received from utilizing such rights, and other relevant
factors. You agree to work with affected parties to distribute with
Initial Developer responsibility on an equitable basis.
EXHIBIT A.
Text for this Exhibit A is found in the corresponding addendum,
described in section 6.4 above, text file provided by the Initial
Developer. This license is not valid or complete with out that
file.
EXHIBIT B.
Text for this Exhibit B is found in the corresponding addendum,
described in section 6.4 above, text file provided by the Initial
Developer. This license is not valid or complete with out that
file.

@ -1,46 +1,46 @@
THDL Open Community License Version 1.0
1. Definitions
This license is a union of the following two parts that should be found as
text files in the same place (directory), in the order of preeminence:
[1] This file itself, named thdl_license.txt
[2] The contents of the file opl_license.txt, stating the general licensing
policy of the software.
2. Precedence of the license parts
In case of conflicting dispositions in the parts of this license, the terms of
the lower-numbered part will always be superseded by the terms of the higher
numbered part.
3. Exhibit A
The contents of this file are subject to the THDL Open Community License
Version 1.0 (the "License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License on the THDL web site
(http://www.thdl.org/).
Software distributed under the License is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied. See the
License for the specific terms governing rights and limitations under the
License.
The Initial Developer of this software is the Tibetan and Himalayan Digital
Library (THDL). Portions created by the THDL are Copyright 2001 THDL.
All Rights Reserved.
Contributor(s): ______________________________________.
4. Exhibit B
This product includes software created by the
Tibetan and Himalayan Digital Library (http://www.thdl.org/).
5. Section 3.2 of OPL 1.0
As used in section 3.2 of the OPL "Contact Means" shall mean
the email address thdltoolbox@virginia.edu
THDL Open Community License Version 1.0
1. Definitions
This license is a union of the following two parts that should be found as
text files in the same place (directory), in the order of preeminence:
[1] This file itself, named thdl_license.txt
[2] The contents of the file opl_license.txt, stating the general licensing
policy of the software.
2. Precedence of the license parts
In case of conflicting dispositions in the parts of this license, the terms of
the lower-numbered part will always be superseded by the terms of the higher
numbered part.
3. Exhibit A
The contents of this file are subject to the THDL Open Community License
Version 1.0 (the "License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License on the THDL web site
(http://www.thdl.org/).
Software distributed under the License is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied. See the
License for the specific terms governing rights and limitations under the
License.
The Initial Developer of this software is the Tibetan and Himalayan Digital
Library (THDL). Portions created by the THDL are Copyright 2001 THDL.
All Rights Reserved.
Contributor(s): ______________________________________.
4. Exhibit B
This product includes software created by the
Tibetan and Himalayan Digital Library (http://www.thdl.org/).
5. Section 3.2 of OPL 1.0
As used in section 3.2 of the OPL "Contact Means" shall mean
the email address thdltoolbox@virginia.edu

@ -1,72 +1,72 @@
<html>
<header>
<font size="+1">Our License</font>
</header>
<p>
<body>
The <a href="thdl_license.txt">THDL Open Community License</a>
is a free software license. The source code for our
software is completely open and public. We hope that others will contribute and build
upon what we've done, resulting in better, more useful products. The core of our license
is the <a href="opl_license.txt">Open Public License</a> (OPL), which is also used by <a href="http://www.enhydra.com/">Enhydra</a>.
The OPL is a slightly modified version of the popular <a href="http://www.opensource.org/licenses/mozilla1.0.html">
Mozilla Public License</a>.
<p>
With this license, you can:
<ol type="a">
<p><li>Modify our software, provided the source code for these modifications remains open,
and your changes are fully documented.
<p><li>Use our software in proprietary projects, or build proprietary extensions to the
software.
</ol><p>
Further, you must:
<ol type="a">
<p><li>Notify the THDL of your modifications.
<p><li>Acknowledge our initial contribution, as well as others' later contributions.
</ol>
<p>
As the creators of the software, our role is to keep track of developments and maintain
the source code. In fact, however, our goals are much broader than this. In particular, we
want to push the use standard technologies. Both Wylie Edit and Jskad take advantage of
two technologies that have significant potential to bring those in Tibetan computing
together.
<p>
On the one hand, our software uses Tony Duff's new cross-platform Tibetan Machine
Web fonts. These are high-quality TrueType fonts, which are freely available and have
been tested and run identically on Windows, Macintosh, and Linux platforms. Documents
created on one platform will transfer unproblematically to any other platform. We hope
that by encouraging the use of and building infrastructure around these fonts, we can help
to promote a dominant and well-supported encoding format, which means less
information lost in the long run.
<p>
On the other hand, our software implements the THDL Extended Wylie Transliteration
Standard, our version of Extended Wylie. THDL Extended Wylie provides simple ASCII
correspondences for all Tibetan characters, including ways to represent Sanskrit stacks as
well as punctuation and many special characters. Until Unicode is a viable solution for
Tibetan computing, Extended Wylie is the best standard, logical, and platform-
independent solution for Tibetan data storage.
<p>
Combining these two technologies, we have created a Microsoft Word add-in and a Java
application for typing and editing Tibetan, as well as converting back and forth between
Extended Wylie and Tibetan Machine Web. Together, this software represents a uniform
and consistent solution to Tibetan text input, which is available on any platform and also
over the web. Many projects could benefit from this work, as well as customize it to meet
their specific needs.
<p>
Although our software is open, we want to promote the standards it employs. We don't
want our Extended Wylie keyboard to become "just another keyboard". Rather, we hope
it will become the Wylie keyboard, one that will become familiar to everyone in Tibetan
computing.
<p>
This is not to say that we at the THDL are allowed to fix the details of the Extended
Wylie transliteration system. What we have arrived at represents a carefully thought out
system, but certainly not the final answer. It remains a work in progress, and we hope that
everyone in Tibetan computing will play a role in shaping the system. We want to hear
your feedback, and thus to shape the standard together. What we don't want is a
profileration of multiple, differing implementations.
<p>
We hope that you will find this software useful. If you are a software developer, we hope
that this license is to your liking, and that you will join us in trying to create a community
of standards for Tibetan computing.
</body>
</html>
<html>
<header>
<font size="+1">Our License</font>
</header>
<p>
<body>
The <a href="thdl_license.txt">THDL Open Community License</a>
is a free software license. The source code for our
software is completely open and public. We hope that others will contribute and build
upon what we've done, resulting in better, more useful products. The core of our license
is the <a href="opl_license.txt">Open Public License</a> (OPL), which is also used by <a href="http://www.enhydra.com/">Enhydra</a>.
The OPL is a slightly modified version of the popular <a href="http://www.opensource.org/licenses/mozilla1.0.html">
Mozilla Public License</a>.
<p>
With this license, you can:
<ol type="a">
<p><li>Modify our software, provided the source code for these modifications remains open,
and your changes are fully documented.
<p><li>Use our software in proprietary projects, or build proprietary extensions to the
software.
</ol><p>
Further, you must:
<ol type="a">
<p><li>Notify the THDL of your modifications.
<p><li>Acknowledge our initial contribution, as well as others' later contributions.
</ol>
<p>
As the creators of the software, our role is to keep track of developments and maintain
the source code. In fact, however, our goals are much broader than this. In particular, we
want to push the use standard technologies. Both Wylie Edit and Jskad take advantage of
two technologies that have significant potential to bring those in Tibetan computing
together.
<p>
On the one hand, our software uses Tony Duff's new cross-platform Tibetan Machine
Web fonts. These are high-quality TrueType fonts, which are freely available and have
been tested and run identically on Windows, Macintosh, and Linux platforms. Documents
created on one platform will transfer unproblematically to any other platform. We hope
that by encouraging the use of and building infrastructure around these fonts, we can help
to promote a dominant and well-supported encoding format, which means less
information lost in the long run.
<p>
On the other hand, our software implements the THDL Extended Wylie Transliteration
Standard, our version of Extended Wylie. THDL Extended Wylie provides simple ASCII
correspondences for all Tibetan characters, including ways to represent Sanskrit stacks as
well as punctuation and many special characters. Until Unicode is a viable solution for
Tibetan computing, Extended Wylie is the best standard, logical, and platform-
independent solution for Tibetan data storage.
<p>
Combining these two technologies, we have created a Microsoft Word add-in and a Java
application for typing and editing Tibetan, as well as converting back and forth between
Extended Wylie and Tibetan Machine Web. Together, this software represents a uniform
and consistent solution to Tibetan text input, which is available on any platform and also
over the web. Many projects could benefit from this work, as well as customize it to meet
their specific needs.
<p>
Although our software is open, we want to promote the standards it employs. We don't
want our Extended Wylie keyboard to become "just another keyboard". Rather, we hope
it will become the Wylie keyboard, one that will become familiar to everyone in Tibetan
computing.
<p>
This is not to say that we at the THDL are allowed to fix the details of the Extended
Wylie transliteration system. What we have arrived at represents a carefully thought out
system, but certainly not the final answer. It remains a work in progress, and we hope that
everyone in Tibetan computing will play a role in shaping the system. We want to hear
your feedback, and thus to shape the standard together. What we don't want is a
profileration of multiple, differing implementations.
<p>
We hope that you will find this software useful. If you are a software developer, we hope
that this license is to your liking, and that you will join us in trying to create a community
of standards for Tibetan computing.
</body>
</html>

File diff suppressed because it is too large Load Diff
Loading…
Cancel
Save