diff options
author | Norbert Preining <preining@logic.at> | 2010-03-28 00:10:19 +0000 |
---|---|---|
committer | Norbert Preining <preining@logic.at> | 2010-03-28 00:10:19 +0000 |
commit | 811acfb0da04fa1b5c9d600f949364bba6b89afb (patch) | |
tree | ebf5199441da41a8674f4b7b1046feb3cc8279b7 /Master/texmf-dist/doc | |
parent | 266576ec33839420ae8e2efed319ada6cea885ba (diff) |
hyph-utf8 update (2010-03-21)
git-svn-id: svn://tug.org/texlive/trunk@17577 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/doc')
-rw-r--r-- | Master/texmf-dist/doc/generic/hyph-utf8/sa/hyphenmin.txt | 11 | ||||
-rw-r--r-- | Master/texmf-dist/doc/latex/hyph-utf8/README | 75 |
2 files changed, 86 insertions, 0 deletions
diff --git a/Master/texmf-dist/doc/generic/hyph-utf8/sa/hyphenmin.txt b/Master/texmf-dist/doc/generic/hyph-utf8/sa/hyphenmin.txt new file mode 100644 index 00000000000..5fbd790b657 --- /dev/null +++ b/Master/texmf-dist/doc/generic/hyph-utf8/sa/hyphenmin.txt @@ -0,0 +1,11 @@ +This is the explanation of the values of hyphenmin used in Sanskrit (and possibly Indic languages) as given by Yves Codet in a private mail on March 19, 2010: + +For lefthyphenmin I think 1 is correct: in Sanskrit, if we allow breaks such as "tu-dati" ("tu" = 2 characters) we must allow "pa-tati" ("pa" = 1 character). + +For righthyphenmin I first suggested 5, as François wrote, which should be forgotten (and forgiven :). Then I thought 3 could be good; my idea was to prohibit a break before a consonant at the end of a word, such as "apata-t" (final "t" = 2 characters). But if hyphenation patterns have precedence over hyphenmins, since patterns contain rules prohibiting such breaks, that precaution is useless, and it has a drawback: it forbids breaks such as "pata-ti" ("ti" = 2 characters) or "pata-ta" ("ta" = 1 character). If patterns do have precedence, it now seems to me that the best choice is 1 for both hyphenmins (I'm sorry, François, about my hesitations :). + +But if my reasoning is sound, this would be for Sanskrit and Prakrit, in whatever script they are written. Maybe there would be reasons to choose other values for some other Indian languages, which I don't know. + +Kind regards, + +Yves diff --git a/Master/texmf-dist/doc/latex/hyph-utf8/README b/Master/texmf-dist/doc/latex/hyph-utf8/README new file mode 100644 index 00000000000..4b753902921 --- /dev/null +++ b/Master/texmf-dist/doc/latex/hyph-utf8/README @@ -0,0 +1,75 @@ +This is HYPH-UTF8 package which contains: + +- hyphenation patterns hyph-foo.tex, semi-manually converted into UTF-8 + from different sources by different authors +- pattern loaders loadhyph-foo.tex that recognise the engine + and load pattern accordingly +- converters from UTF-8 into EC/T1, QX, part of ISO Latin 3, T2A & LMC +- some scripts to assist with auto-generating the files + +Modificatios were needed in order to support native UTF-8 engines, +but functionality (hopefully) didn't change in any way, at least not intentionally. +The patterns themselves are no longer stand-alone; at least for 8-bit engines +you need to use loadhyph-foo.tex (which will load the patterns) instead. + +Modifications were done by Jonathan Kew, Mojca Miklavec & Arthur Reutenauer +with help & support from: + +- Karl Berry, who gave us free hands and all resources +- Taco Hoekwater, with useful macros +- Hans Hagen, who did the unicodifisation of patterns already long before + and helped with testing, suggestions and bug reports +- Norbert Preining, who tested & integrated patterns into TeX Live + +However, the "copyright/copyleft" owner of patterns remains the original author. + +The original patterns should eventually become obsolete, +and the author of the original file should preferraby modify +these files instead (feel free to remove credits added by TUG from those files). + +If you want to change the patterns, rather than uploading directly to CTAN, +we would be grateful if you could send it to us (http://tug.org/tex-hyphen) +or ask for credentials for SVN repository and commit it yourself; +we will then upload the whole "package" to CTAN. + +Before a new "pattern-revolution" starts, +please try to follow some guidelines if possible: + +- \lccode is *forbidden*, and I really mean it +- all the patterns should be in UTF-8 +- the only "allowed" TeX commands in patterns are: \patterns, \hyphenation, + and if you really cannot do without, also \input and \message +- in particular, please no \catcode or \lccode changes, + they belong to loadhyph-foo.tex, + and no \lefthyphenmin and \righthyphenmin, + they have no influence here and belong elsewhere +- \begingroup and/or \endinput is not needed +- feel free to do whatever you want inside comments + +We know that TeX is extremely powerful, but give a stupid parser +at least a chance to read your patterns. + +For more information see + + http://tug.org/tex-hyphen + + +Copyright 2008 by TUG + +The licence for hyph-foo.tex: Respect licences of original authors. +The licence for the rest: Use common sense when modifying and coordinate your work. + +Hyphenation patterns are essential to TeX; +whatever changes you make to these files - +make sure to coordinate your work with everyone involved. +(TeX Live, MikTeX, CTAN, patter authors, mailing list, ...) + +People come and go, TeX evolves. We are aware of that. +If we disapear one day and there is a need to change files, +do whatever needs to be done to make TeX behave in a proper +(backward compatible) way. And keep things clean & consistent. + +Things that might change in near future: +- support for multiple versions of patterns +- support for runtime loading of patterns +- support for preferred hyphenation points and discretionaries (ck -> k-k) |