summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/latex/hyperref/README
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/latex/hyperref/README')
-rw-r--r--Master/texmf-dist/doc/latex/hyperref/README79
1 files changed, 78 insertions, 1 deletions
diff --git a/Master/texmf-dist/doc/latex/hyperref/README b/Master/texmf-dist/doc/latex/hyperref/README
index b1d11d74bf1..095440a6707 100644
--- a/Master/texmf-dist/doc/latex/hyperref/README
+++ b/Master/texmf-dist/doc/latex/hyperref/README
@@ -1,4 +1,4 @@
-README for hyperref bundle, 2008/08/14
+README for hyperref bundle, 2008/09/11
TABLE OF CONTENTS
@@ -176,6 +176,82 @@ other packages:
5 NEW FEATURES
==============
+\unichar
+--------
+ If a Unicode character is not supported by puenc.def, it can
+ be given by using \unichar. It's name and syntax is inherited
+ from package `ucs'. However it is defined independently for
+ use in hyperref's \pdfstringdef (that converts arbitrary
+ TeX code to PDF strings or tries to do this).
+
+ Macro \unichar takes a TeX number as argument,
+ examples for U+263A (WHITE SMILING FACE):
+ \unichar{"263A}% hexadecimal notation
+ \unichar{9786}% decimal notation
+ `"' must not be a babel shorthand character or otherwise
+ active. Otherwise prefix it with \string:
+ \unichar{\string"263A}% converts `"' to `"' with catcode 12 (other)
+ Users of (n)german packages or babel options may use \dq instead:
+ \unichar{\dq 263A}% \dq is double quote with catcode 12 (other)
+
+\ifpdfstringunicode
+-------------------
+ Some features of the PDF specification needs PDF strings.
+ Examples are bookmarks or the entries in the information dictionary.
+ The PDF specification allows two encodings `PDFDocEncoding'
+ (8-bit encoding) and `Unicode' (UTF-16). The user can help
+ using \texorpdfstring to replace complicate TeX constructs
+ by a representation for the PDF string. However \texorpdfstring
+ does not distinguish the two encodings. This gap closes
+ \ifpdfstringunicode. It is only allowed in the second argument
+ of \texorpdfstring and takes two arguments, the first allows
+ the full range of Unicode. The second is limited to the
+ characters available in PDFDocEncoding.
+
+ As example we take a macro definition for the Vietnamese
+ name of Han The Thanh. Correctly written it needs some
+ accented characters, one character even with a double accent.
+ Class `tugboat.cls' defines a macro for the typesetted name:
+ \def\Thanh{%
+ H\`an~%
+ Th\^e\llap{\raise 0.5ex\hbox{\'{}}}%
+ ~Th\`anh%
+ }
+ It's not entirely correct, the second accent over the `e' is not
+ an acute, but a hook. However standard LaTeX does not provide
+ such an accent.
+ Now we can extend the defintion to support hyperref.
+ The first and the last word are already supported automatically.
+ Characters with two or more accents are a difficult business in
+ LaTeX, because the NFSS2 macros of the LaTeX kernel do not support
+ more than one accent. Therefore also puenc.def misses support for
+ them. But we can provide it using \unichar. The character
+ in question is:
+ % U+1EC3 LATIN SMALL LETTER E WITH CIRCUMFLEX AND HOOK ABOVE
+ Thus we can put this together:
+ \def\Thanh{%
+ H\`an~%
+ \texorpdfstring{Th\^e\llap{\raise 0.5ex\hbox{\'{}}}}%
+ {\ifpdfstringunicode{Th\unichar{"1EC3}}{Th\^e}}%
+ ~Th\`anh%
+ }
+ For PDFDocEncoding (PD1) the variant above has dropped the
+ second accent. Alternatively we could provide a representation
+ without accents instead of wrong accents:
+ \def\Thanh{%
+ \texorpdfstring{%
+ H\`an~%
+ Th\^e\llap{\raise 0.5ex\hbox{\'{}}}}%
+ ~Th\`anh%
+ }{%
+ \ifpdfstringunicode{%
+ H\`an Th\unichar{"1EC3} Th\`anh%
+ }{%
+ Han The Thanh%
+ }%
+ }%
+ }
+
Customizing index style file with \nohyperpage
----------------------------------------------
Since version 2008/08/14 v6.78f.
@@ -1268,6 +1344,7 @@ Responsible for the additions to PU encoding for Arabi is
TeX Live
--------
+* TL 2008: 2008/08/14 v6.78f (at time of first release)
* TL 2007: 2007/02/07 v6.75r
* TL 2005: 2003/11/30 v6.74m
* TL 2004: 2003/11/30 v6.74m