From 844aa1bb2859867c52f86f383203db56607bd74c Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Sun, 29 Jul 2018 21:15:34 +0000 Subject: fontspec (29jul18) git-svn-id: svn://tug.org/texlive/trunk@48307 c570f23f-e606-0410-a88d-b1316a301751 --- Master/texmf-dist/doc/latex/fontspec/CHANGES.md | 83 ++-- Master/texmf-dist/doc/latex/fontspec/LICENSE | 416 +++++++++++++++++++++ .../doc/latex/fontspec/fontspec-code.pdf | Bin 611647 -> 601734 bytes Master/texmf-dist/doc/latex/fontspec/fontspec.pdf | Bin 686522 -> 691770 bytes 4 files changed, 460 insertions(+), 39 deletions(-) create mode 100644 Master/texmf-dist/doc/latex/fontspec/LICENSE (limited to 'Master/texmf-dist/doc/latex') diff --git a/Master/texmf-dist/doc/latex/fontspec/CHANGES.md b/Master/texmf-dist/doc/latex/fontspec/CHANGES.md index 7a8a0760bcd..9865430d7c3 100644 --- a/Master/texmf-dist/doc/latex/fontspec/CHANGES.md +++ b/Master/texmf-dist/doc/latex/fontspec/CHANGES.md @@ -1,16 +1,21 @@ - Change history ============== -- v2.6g (2017-11-09) +## v2.6h (2018/07/29) + + * `expl3` internals updated so loading `expl3` with the `check-declarations` option will run without error. + * Fix bug with `FontFace` in which spaces weren't being ignored. + + +## v2.6g (2017-11-09) * Bugfix for clash introduced with last version. When loading `babel` before `fontspec` the following error arose: - + ! Control sequence \latinencoding already defined. -- v2.6f (2017-11-05) +## v2.6f (2017-11-05) * Fix loading of Graphite fonts and add a little documentation (a better interface is needed, though) * Correct and simplify some internal code that fixes a bug in the way some fonts are displayed in `\tracingoutput` mode. @@ -19,26 +24,26 @@ Change history * This package now complies with the `expl3` option `check-declarations`. -- v2.6e (2017/09/22) +## v2.6e (2017/09/22) * Re-enable use of `HyphenChar=None` in LuaLaTeX. (Hyphenation and font choice are decoupled in LuaTeX, except for this one setting.) * Some internal changes needed by `unicode-math` to fix some cross-over code. -- v2.6d (2017/08/14) +## v2.6d (2017/08/14) * Update Scripts to Unicode 1.8.2 (thanks Werner) * Remove `HyphenChar` feature when running LuaTeX — use `\prehyphenchar` LuaTeX primitive instead. * Rewrite test suite so that automated testing actually functions correctly and automatically. Thanks to Joseph for introducing me to Travis CI. -- v2.6c (2017/07/23) +## v2.6c (2017/07/23) * Emergency bug-fix. -- v2.6b (2017/07/16) +## v2.6b (2017/07/16) * Fix conflict with Polyglossia and `Scale=MatchLowercase`. * New feature `IgnoreFontspecFile` to avoid loading the `.fontspec` file for a font. @@ -46,12 +51,12 @@ Change history (which broke `realscripts`, oops — must improve my test suite) -- v2.6a (2017/03/31) +## v2.6a (2017/03/31) * Fix crashing bug with `..Reset` and `ResetAll` keys. * Fix crashing bug with `\newfontface`. -- v2.6 (2017/02/12) +## v2.6 (2017/02/12) * Change the new behaviour of `\emph` (and `\emfontdeclare`) to act only on the NFSS font shape; using the series as well was too fragile. * Add `\strong` as the "weight" analogy to `\emph`. This will need some extra syntactic sugar from `fontspec` before it becomes truly useful. @@ -65,12 +70,12 @@ Change history * N.B. There is currently a known issue with TTC fonts and LuaTeX; currently they cannot be loaded through the `fontspec` interface, but this issue should soon be addressed by the `luaotfload` package. -- v2.5d (2017/01/24) "oops" +## v2.5d (2017/01/24) "oops" * Add `\fontspec_if_small_caps:TF` * Fix bug in `\emph` (!!) -- v2.5c (2017/01/20) "Christmas 2016 release" +## v2.5c (2017/01/20) "Christmas 2016 release" * `TU` font encoding now default, with encoding files provided by the kernel. * Experimental interface added for customising encodings. @@ -86,7 +91,7 @@ Change history * Big table of OpenType feature tags to help cross-reference which fontspec feature (if any) corresponds to which OpenType feature. * Bug fixed for `Script` selection. -- v2.5b (2016/05/14) "More bugs" (somehow never released) +## v2.5b (2016/05/14) "More bugs" (somehow never released) * Fixed bug with garbage text printed in certain "verbatim" situations under LuaTeX. * Improve interaction between optical sizes and small caps. @@ -94,7 +99,7 @@ Change history (there are other methods to perform the same thing, but no "easy" user interface that `fontspec` can provide at this stage). * Fix regression causing an error message if `fontspec` loaded before `\documentclass'. -- v2.5a (2016/02/01) "Bugs fixed" +## v2.5a (2016/02/01) "Bugs fixed" * Rather embarrassing bug fix! (`unicode-math` was broken.) * Remember to add the `fontspec.cfg` file to the distribution. @@ -102,7 +107,7 @@ Change history * Add some basic tests using `l3build`; more to come. * Simplify some internal Lua code and package loading code. -- v2.5 (2016/01/30) "TL2016 release" +## v2.5 (2016/01/30) "TL2016 release" * Provide a new Unicode font encoding ("TU") to replace EU1/EU2 and xunicode. * Activate with package option `[tuenc]'; once it becomes the default (later this year), `[euenc]` option will revert to the old behaviour. @@ -116,23 +121,23 @@ Change history * Improvement to some warnings/info messages. * Improve structure of code. -- v2.4e (2015/09/24) +## v2.4e (2015/09/24) * Allow `[Path=...]` to be specified for individual font faces. * Continue to normalise naming with expl3. (Ongoing.) -- v2.4d (2015/07/22) +## v2.4d (2015/07/22) * Rename an internal expl3 function or two. -- v2.4c (2015/03/14) +## v2.4c (2015/03/14) * v2.4b was never released, sorry! * This time *really* fix `\@fnsymbol` and avoid overwriting it if already fixed. * Fix "`Renderer=Graphite`" (off-by-one error). * Fix some edge cases for `\aliasfontfeature`. -- v2.4b (2014/08/23) +## v2.4b (2014/08/23) * Improve backwards compatibility w.r.t. recent argument order change; specifically, if an optional argument is presented before the font name @@ -142,13 +147,13 @@ Change history mixed-case ".fontspec" files. * Fixed some documentation typos/inconsistencies related to recent changes. -- v2.4a (2014/06/21) +## v2.4a (2014/06/21) * No longer load fixltx2e.sty -- this package should really be loaded before \documentclass. * Avoid deprecated l3fp code. * A couple of bugs introduced with v2.4 fixed. -- v2.4 (2014/06/01) +## v2.4 (2014/06/01) * Significant change to the user interface: instead of `\setmainfont[features]{font}`, you now write `\setmainfont{font}[features]`. Backwards compatibility is of course preserved. @@ -190,26 +195,26 @@ Change history * Setting the `SmallCapsFont` using the `*`-replacement notation has been improved/fixed. -- v2.3c (2013/05/20) +## v2.3c (2013/05/20) * Compatbility with luaotfload 2013/05/20 2.2c, support for older version removed. -- v2.3b (2013/05/12) +## v2.3b (2013/05/12) * Compatibility with new (and future) version of luaotfload -- v2.3a (2013/03/16) +## v2.3a (2013/03/16) * Bug fix update to retain compatibility with new expl3 -- v2.3 (2013/02/25) +## v2.3 (2013/02/25) * Add support for per-font options in `\defaultfontfeatures` * Add support for `.fontspec` per-font configuration files * Keep up-to-date with expl3 changes -- v2.2b (2012/05/06) "TL2012 version" +## v2.2b (2012/05/06) "TL2012 version" * Fix error with AutoFakeSlant/Bold (#113) and when used with external fonts (#128) * Add warning when using FakeBold in LuaLaTeX, where it's not supported @@ -219,12 +224,12 @@ Change history * Avoid using the calc package now that it's no longer loaded by expl3 * Allow multiple values to StylisticSet and Alternate font options -- v2.2a (2011/09/14) +## v2.2a (2011/09/14) * Bug fix: improve backwards compatibility for packages that use old fontspec internals such as mathspec. -- v2.2 (2011/09/13) +## v2.2 (2011/09/13) * Support alternate selections in CharacterVariant (cvxx in OpenType) using new syntax `[CharacterVariant=5:2]`. @@ -251,11 +256,11 @@ Change history same information - Update `expl3` support to latest CTAN version. -- v2.1g (2011/08/02) +## v2.1g (2011/08/02) * No longer uses the binhex package, avoiding some name clashes with TIPA -- v2.1f (2011/02/26) +## v2.1f (2011/02/26) * Finally add a real error message when a font cannot be found! * Add "Letters=Random" feature. @@ -263,17 +268,17 @@ Change history were shown in the log file. * Some small documentation improvements. -- v2.1e (2010/11/17) +## v2.1e (2010/11/17) * Internal changes for luatexbase v0.3. -- v2.1d (2010/11/07) +## v2.1d (2010/11/07) * Bug fix when \itdefault is "sl" rather than "it". E.g., when using the "slides" class. * Minor internal changes, including merging some code from unicode-math. -- v2.1c (2010/10/13) +## v2.1c (2010/10/13) * New documentation for defining custom kerning and ligatures when using LuaLaTeX. @@ -282,12 +287,12 @@ Change history that does not contain it. TODO: a suitable fallback script should be chosen; right now we just ignore the script selection. -- v2.1b (2010/09/29) +## v2.1b (2010/09/29) * Fix for bug introduced in the last release: small caps weren't being automatically selected correctly -- v2.1a (2010/09/27) +## v2.1a (2010/09/27) * Fix for colours bug introduced in the last update * Fix for for bad interaction with LuaLaTeX and fallback fonts @@ -306,7 +311,7 @@ Change history * Lots of internal changes to bring the implementation closer to being "native expl3". -- v2.1 (2010/09/19) +## v2.1 (2010/09/19) * Now load xunicode internally for consistent behaviour in XeLaTeX and LuaLaTeX. @@ -318,7 +323,7 @@ Change history in the transition to v2. * Bug fix for a problem triggered after counters got too high. -- v2.0c (2010/08/01) +## v2.0c (2010/08/01) Bug fix and documentation tune-up. * Significant bug fix reported simultaneously by Enrico Gregorio and @@ -326,7 +331,7 @@ Change history * Many documentation improvements and additions due to David Perry. * Documentation typo thanks to John McChesney-Young -- v2.0b (2010/07/14) +## v2.0b (2010/07/14) *Actually* the final release before TeX Live 2010. * Improved examples in the documentation, with fewer proprietary fonts @@ -336,7 +341,7 @@ Change history * New OpenType feature `CharacterVariant` now supported * Minor change: `Ligatures=Historical` is now `Ligatures=Historic` for consistency -- v2.0a (2010/07/11) +## v2.0a (2010/07/11) Final release before TeX Live 2010. * Bug fix for the Language setting being ignored diff --git a/Master/texmf-dist/doc/latex/fontspec/LICENSE b/Master/texmf-dist/doc/latex/fontspec/LICENSE new file mode 100644 index 00000000000..22443139013 --- /dev/null +++ b/Master/texmf-dist/doc/latex/fontspec/LICENSE @@ -0,0 +1,416 @@ +The LaTeX Project Public License +=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- + +LPPL Version 1.3c 2008-05-04 + +Copyright 1999 2002-2008 LaTeX3 Project + Everyone is allowed to distribute verbatim copies of this + license document, but modification of it is not allowed. + + +PREAMBLE +======== + +The LaTeX Project Public License (LPPL) is the primary license under +which the LaTeX kernel and the base LaTeX packages are distributed. + +You may use this license for any work of which you hold the copyright +and which you wish to distribute. This license may be particularly +suitable if your work is TeX-related (such as a LaTeX package), but +it is written in such a way that you can use it even if your work is +unrelated to TeX. + +The section `WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE', +below, gives instructions, examples, and recommendations for authors +who are considering distributing their works under this license. + +This license gives conditions under which a work may be distributed +and modified, as well as conditions under which modified versions of +that work may be distributed. + +We, the LaTeX3 Project, believe that the conditions below give you +the freedom to make and distribute modified versions of your work +that conform with whatever technical specifications you wish while +maintaining the availability, integrity, and reliability of +that work. If you do not see how to achieve your goal while +meeting these conditions, then read the document `cfgguide.tex' +and `modguide.tex' in the base LaTeX distribution for suggestions. + + +DEFINITIONS +=========== + +In this license document the following terms are used: + + `Work' + Any work being distributed under this License. + + `Derived Work' + Any work that under any applicable law is derived from the Work. + + `Modification' + Any procedure that produces a Derived Work under any applicable + law -- for example, the production of a file containing an + original file associated with the Work or a significant portion of + such a file, either verbatim or with modifications and/or + translated into another language. + + `Modify' + To apply any procedure that produces a Derived Work under any + applicable law. + + `Distribution' + Making copies of the Work available from one person to another, in + whole or in part. Distribution includes (but is not limited to) + making any electronic components of the Work accessible by + file transfer protocols such as FTP or HTTP or by shared file + systems such as Sun's Network File System (NFS). + + `Compiled Work' + A version of the Work that has been processed into a form where it + is directly usable on a computer system. This processing may + include using installation facilities provided by the Work, + transformations of the Work, copying of components of the Work, or + other activities. Note that modification of any installation + facilities provided by the Work constitutes modification of the Work. + + `Current Maintainer' + A person or persons nominated as such within the Work. If there is + no such explicit nomination then it is the `Copyright Holder' under + any applicable law. + + `Base Interpreter' + A program or process that is normally needed for running or + interpreting a part or the whole of the Work. + + A Base Interpreter may depend on external components but these + are not considered part of the Base Interpreter provided that each + external component clearly identifies itself whenever it is used + interactively. Unless explicitly specified when applying the + license to the Work, the only applicable Base Interpreter is a + `LaTeX-Format' or in the case of files belonging to the + `LaTeX-format' a program implementing the `TeX language'. + + + +CONDITIONS ON DISTRIBUTION AND MODIFICATION +=========================================== + +1. Activities other than distribution and/or modification of the Work +are not covered by this license; they are outside its scope. In +particular, the act of running the Work is not restricted and no +requirements are made concerning any offers of support for the Work. + +2. You may distribute a complete, unmodified copy of the Work as you +received it. Distribution of only part of the Work is considered +modification of the Work, and no right to distribute such a Derived +Work may be assumed under the terms of this clause. + +3. You may distribute a Compiled Work that has been generated from a +complete, unmodified copy of the Work as distributed under Clause 2 +above, as long as that Compiled Work is distributed in such a way that +the recipients may install the Compiled Work on their system exactly +as it would have been installed if they generated a Compiled Work +directly from the Work. + +4. If you are the Current Maintainer of the Work, you may, without +restriction, modify the Work, thus creating a Derived Work. You may +also distribute the Derived Work without restriction, including +Compiled Works generated from the Derived Work. Derived Works +distributed in this manner by the Current Maintainer are considered to +be updated versions of the Work. + +5. If you are not the Current Maintainer of the Work, you may modify +your copy of the Work, thus creating a Derived Work based on the Work, +and compile this Derived Work, thus creating a Compiled Work based on +the Derived Work. + +6. If you are not the Current Maintainer of the Work, you may +distribute a Derived Work provided the following conditions are met +for every component of the Work unless that component clearly states +in the copyright notice that it is exempt from that condition. Only +the Current Maintainer is allowed to add such statements of exemption +to a component of the Work. + + a. If a component of this Derived Work can be a direct replacement + for a component of the Work when that component is used with the + Base Interpreter, then, wherever this component of the Work + identifies itself to the user when used interactively with that + Base Interpreter, the replacement component of this Derived Work + clearly and unambiguously identifies itself as a modified version + of this component to the user when used interactively with that + Base Interpreter. + + b. Every component of the Derived Work contains prominent notices + detailing the nature of the changes to that component, or a + prominent reference to another file that is distributed as part + of the Derived Work and that contains a complete and accurate log + of the changes. + + c. No information in the Derived Work implies that any persons, + including (but not limited to) the authors of the original version + of the Work, provide any support, including (but not limited to) + the reporting and handling of errors, to recipients of the + Derived Work unless those persons have stated explicitly that + they do provide such support for the Derived Work. + + d. You distribute at least one of the following with the Derived Work: + + 1. A complete, unmodified copy of the Work; + if your distribution of a modified component is made by + offering access to copy the modified component from a + designated place, then offering equivalent access to copy + the Work from the same or some similar place meets this + condition, even though third parties are not compelled to + copy the Work along with the modified component; + + 2. Information that is sufficient to obtain a complete, + unmodified copy of the Work. + +7. If you are not the Current Maintainer of the Work, you may +distribute a Compiled Work generated from a Derived Work, as long as +the Derived Work is distributed to all recipients of the Compiled +Work, and as long as the conditions of Clause 6, above, are met with +regard to the Derived Work. + +8. The conditions above are not intended to prohibit, and hence do not +apply to, the modification, by any method, of any component so that it +becomes identical to an updated version of that component of the Work as +it is distributed by the Current Maintainer under Clause 4, above. + +9. Distribution of the Work or any Derived Work in an alternative +format, where the Work or that Derived Work (in whole or in part) is +then produced by applying some process to that format, does not relax or +nullify any sections of this license as they pertain to the results of +applying that process. + +10. a. A Derived Work may be distributed under a different license + provided that license itself honors the conditions listed in + Clause 6 above, in regard to the Work, though it does not have + to honor the rest of the conditions in this license. + + b. If a Derived Work is distributed under a different license, that + Derived Work must provide sufficient documentation as part of + itself to allow each recipient of that Derived Work to honor the + restrictions in Clause 6 above, concerning changes from the Work. + +11. This license places no restrictions on works that are unrelated to +the Work, nor does this license place any restrictions on aggregating +such works with the Work by any means. + +12. Nothing in this license is intended to, or may be used to, prevent +complete compliance by all parties with all applicable laws. + + +NO WARRANTY +=========== + +There is no warranty for the Work. Except when otherwise stated in +writing, the Copyright Holder provides the Work `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 Work is with you. Should the Work prove defective, you assume +the cost of all necessary servicing, repair, or correction. + +In no event unless required by applicable law or agreed to in writing +will The Copyright Holder, or any author named in the components of the +Work, or any other party who may distribute and/or modify the Work as +permitted above, be liable to you for damages, including any general, +special, incidental or consequential damages arising out of any use of +the Work or out of inability to use the Work (including, but not limited +to, loss of data, data being rendered inaccurate, or losses sustained by +anyone as a result of any failure of the Work to operate with any other +programs), even if the Copyright Holder or said author or said other +party has been advised of the possibility of such damages. + + +MAINTENANCE OF THE WORK +======================= + +The Work has the status `author-maintained' if the Copyright Holder +explicitly and prominently states near the primary copyright notice in +the Work that the Work can only be maintained by the Copyright Holder +or simply that it is `author-maintained'. + +The Work has the status `maintained' if there is a Current Maintainer +who has indicated in the Work that they are willing to receive error +reports for the Work (for example, by supplying a valid e-mail +address). It is not required for the Current Maintainer to acknowledge +or act upon these error reports. + +The Work changes from status `maintained' to `unmaintained' if there +is no Current Maintainer, or the person stated to be Current +Maintainer of the work cannot be reached through the indicated means +of communication for a period of six months, and there are no other +significant signs of active maintenance. + +You can become the Current Maintainer of the Work by agreement with +any existing Current Maintainer to take over this role. + +If the Work is unmaintained, you can become the Current Maintainer of +the Work through the following steps: + + 1. Make a reasonable attempt to trace the Current Maintainer (and + the Copyright Holder, if the two differ) through the means of + an Internet or similar search. + + 2. If this search is successful, then enquire whether the Work + is still maintained. + + a. If it is being maintained, then ask the Current Maintainer + to update their communication data within one month. + + b. If the search is unsuccessful or no action to resume active + maintenance is taken by the Current Maintainer, then announce + within the pertinent community your intention to take over + maintenance. (If the Work is a LaTeX work, this could be + done, for example, by posting to comp.text.tex.) + + 3a. If the Current Maintainer is reachable and agrees to pass + maintenance of the Work to you, then this takes effect + immediately upon announcement. + + b. If the Current Maintainer is not reachable and the Copyright + Holder agrees that maintenance of the Work be passed to you, + then this takes effect immediately upon announcement. + + 4. If you make an `intention announcement' as described in 2b. above + and after three months your intention is challenged neither by + the Current Maintainer nor by the Copyright Holder nor by other + people, then you may arrange for the Work to be changed so as + to name you as the (new) Current Maintainer. + + 5. If the previously unreachable Current Maintainer becomes + reachable once more within three months of a change completed + under the terms of 3b) or 4), then that Current Maintainer must + become or remain the Current Maintainer upon request provided + they then update their communication data within one month. + +A change in the Current Maintainer does not, of itself, alter the fact +that the Work is distributed under the LPPL license. + +If you become the Current Maintainer of the Work, you should +immediately provide, within the Work, a prominent and unambiguous +statement of your status as Current Maintainer. You should also +announce your new status to the same pertinent community as +in 2b) above. + + +WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE +====================================================== + +This section contains important instructions, examples, and +recommendations for authors who are considering distributing their +works under this license. These authors are addressed as `you' in +this section. + +Choosing This License or Another License +---------------------------------------- + +If for any part of your work you want or need to use *distribution* +conditions that differ significantly from those in this license, then +do not refer to this license anywhere in your work but, instead, +distribute your work under a different license. You may use the text +of this license as a model for your own license, but your license +should not refer to the LPPL or otherwise give the impression that +your work is distributed under the LPPL. + +The document `modguide.tex' in the base LaTeX distribution explains +the motivation behind the conditions of this license. It explains, +for example, why distributing LaTeX under the GNU General Public +License (GPL) was considered inappropriate. Even if your work is +unrelated to LaTeX, the discussion in `modguide.tex' may still be +relevant, and authors intending to distribute their works under any +license are encouraged to read it. + +A Recommendation on Modification Without Distribution +----------------------------------------------------- + +It is wise never to modify a component of the Work, even for your own +personal use, without also meeting the above conditions for +distributing the modified component. While you might intend that such +modifications will never be distributed, often this will happen by +accident -- you may forget that you have modified that component; or +it may not occur to you when allowing others to access the modified +version that you are thus distributing it and violating the conditions +of this license in ways that could have legal implications and, worse, +cause problems for the community. It is therefore usually in your +best interest to keep your copy of the Work identical with the public +one. Many works provide ways to control the behavior of that work +without altering any of its licensed components. + +How to Use This License +----------------------- + +To use this license, place in each of the components of your work both +an explicit copyright notice including your name and the year the work +was authored and/or last substantially modified. Include also a +statement that the distribution and/or modification of that +component is constrained by the conditions in this license. + +Here is an example of such a notice and statement: + + %% pig.dtx + %% Copyright 2005 M. Y. Name + % + % This work may be distributed and/or modified under the + % conditions of the LaTeX Project Public License, either version 1.3 + % of this license or (at your option) any later version. + % The latest version of this license is in + % http://www.latex-project.org/lppl.txt + % and version 1.3 or later is part of all distributions of LaTeX + % version 2005/12/01 or later. + % + % This work has the LPPL maintenance status `maintained'. + % + % The Current Maintainer of this work is M. Y. Name. + % + % This work consists of the files pig.dtx and pig.ins + % and the derived file pig.sty. + +Given such a notice and statement in a file, the conditions +given in this license document would apply, with the `Work' referring +to the three files `pig.dtx', `pig.ins', and `pig.sty' (the last being +generated from `pig.dtx' using `pig.ins'), the `Base Interpreter' +referring to any `LaTeX-Format', and both `Copyright Holder' and +`Current Maintainer' referring to the person `M. Y. Name'. + +If you do not want the Maintenance section of LPPL to apply to your +Work, change `maintained' above into `author-maintained'. +However, we recommend that you use `maintained', as the Maintenance +section was added in order to ensure that your Work remains useful to +the community even when you can no longer maintain and support it +yourself. + +Derived Works That Are Not Replacements +--------------------------------------- + +Several clauses of the LPPL specify means to provide reliability and +stability for the user community. They therefore concern themselves +with the case that a Derived Work is intended to be used as a +(compatible or incompatible) replacement of the original Work. If +this is not the case (e.g., if a few lines of code are reused for a +completely different task), then clauses 6b and 6d shall not apply. + + +Important Recommendations +------------------------- + + Defining What Constitutes the Work + + The LPPL requires that distributions of the Work contain all the + files of the Work. It is therefore important that you provide a + way for the licensee to determine which files constitute the Work. + This could, for example, be achieved by explicitly listing all the + files of the Work near the copyright notice of each file or by + using a line such as: + + % This work consists of all files listed in manifest.txt. + + in that place. In the absence of an unequivocal list it might be + impossible for the licensee to determine what is considered by you + to comprise the Work and, in such a case, the licensee would be + entitled to make reasonable conjectures as to which files comprise + the Work. + diff --git a/Master/texmf-dist/doc/latex/fontspec/fontspec-code.pdf b/Master/texmf-dist/doc/latex/fontspec/fontspec-code.pdf index fe889558f00..362b0286bed 100644 Binary files a/Master/texmf-dist/doc/latex/fontspec/fontspec-code.pdf and b/Master/texmf-dist/doc/latex/fontspec/fontspec-code.pdf differ diff --git a/Master/texmf-dist/doc/latex/fontspec/fontspec.pdf b/Master/texmf-dist/doc/latex/fontspec/fontspec.pdf index 5e9584724d4..a844bcb7db6 100644 Binary files a/Master/texmf-dist/doc/latex/fontspec/fontspec.pdf and b/Master/texmf-dist/doc/latex/fontspec/fontspec.pdf differ -- cgit v1.2.3