+2006-10-12 Graham Percival <gpermus@gmail.com>
+
+ * Documentation/user/ {some}: minor edits that were lost somehow.
+
2006-10-12 Han-Wen Nienhuys <hanwen@lilypond.org>
* VERSION (PACKAGE_NAME): bump version.
* Documentation/user/basic-notation.itely: document volta brackets
not aligning (bug 63).
+ * Documentation/user/ global.itely invoking.itely: ignore or
+ add warnings about texstr.
+
2006-10-08 John Mandereau <john.mandereau@free.fr>
* po/fr.po: update translation.
popular modern editors have utf-8 support, for example, vim, Emacs,
jEdit, and GEdit do.
+@c Currently not working
+@ignore
Depending on the fonts installed, the following fragment shows Hebrew
and Cyrillic lyrics,
@cindex Hebrew
@cindex ASCII, non
-@lilypondfile[fontload]{utf-8.ly}
+@li lypondfile[fontload]{utf-8.ly}
The @TeX{} backend does not handle encoding specially at all. Strings
in the input are put in the output as-is. Extents of text items in the
suitable LaTeX wrappers to load appropriate La@TeX{} packages for
interpreting non-ASCII strings.
+@end ignore
+
To use a Unicode escape sequence, use
@example
@item texstr
dump text strings to @file{.texstr} file, which can be run through
(La)@TeX{}, resulting in a @code{.textmetrics} file, which contains the
-extents of strings of text.
+extents of strings of text. @strong{Warning:} this functionality is
+currently missing due to heavy restructuring of the source code.
@item ps
for PostScript.
@cindex PostScript output
"extra vertical extent, same format as @var{minimumVerticalExtent}")
- (figuredBassCenterContinuations ,boolean? "Whether to vertically center pairs of extender lines.")
+ (figuredBassCenterContinuations ,boolean? "Whether to vertically center pairs of extender lines. This does not work with three or more lines")
(figuredBassPlusDirection ,ly:dir? "Where to put plus signs relative to the the main figure.")
(figuredBassAlterationDirection ,ly:dir? "Where to put