Thank you to all that tested the various release candidates and reported
bugs. As promised, 3.0.0 is officially released today:
Release Notes:
## [3.0.0] - 2015-05-14
### Changed
- [New website](http://gregorio-project.github.io) containing
instructions only for new versions of Gregorio starting with this
release, in English only.
- New clean Mac OSX installer (intel only).
- New incompatible format of space configuration files (`gsp-xxx.tex`).
Values are now scaled to the default staff size (see
[#50](https://github.com/gregorio-project/gregorio/issues/50). You now
need to use `\gresetdim` for setting distances (`\somedistance = 3cm`)
can no longer be used). `\gresetdim` takes three arguments: the name of
the distance, the desired value, and whether the distance should scale
with changes in the staff size or not. See `gsp-default.tex` for an
example.
- All distances can now be set to scale with staff size, as a
consequence `\grechangedim` now takes three arguments: the name of the
distance, value to change the distance to (which now supports em and ex
units), and whether or not this value should be scaled with changes in
the staff size. See GregorioRef for details.
- `\setinitalspacing` , `\setspacebeforeinitial`,
`\setspaceafterinitial`, and `\setaboveinitialseparation` now take an
additional argument. The new argument specifies whether the distance
should scale when the staff size changes.
- Improved `\includescore` capabilities. The `\includescore[f]`
parameter has changed to `\includescore[n]` compared to version 2.4.2.
See doc/UserManual.pdf for full details and UPGRADING.md for
instructions on how to upgrade your score from 2.4.2.
- Clivis stem length now follow Solesmes' books conventions (see
[#31](https://github.com/gregorio-project/gregorio/issues/31)).
- Windows TeXworks configuration script no longer adds deprecated
`greg-book` and `gregorio` engines (see below).
- `build.sh` and `install.sh` scripts are now used to build and install
Gregorio with common options.
- Clarified post installation options for Windows installer. What was
the "Install Fonts" option is now labeled to indicate that this also
adds GregorioTeX files to the texmf tree.
- `\grechangedim` now checks to make sure it only operates on existing
distances and doesn't create a new one.
### Fixed
- `\includescore` not finding files for autocompile under certain
circumstances. (see [this
thread](http://www.mail-archive.com/[email protected]/msg02346.html)).
- Spacing between a syllable and a syllable with text and only a bar was
too short.
- Torculus followed by a non-liquescent note is now parsed correctly
(see [#284](https://github.com/gregorio-project/gregorio/issues/284).
- Spacing after a syllable with an flat, sharp, or natural is now
correct (see
[#246](https://github.com/gregorio-project/gregorio/issues/246).
### Added
- `\setstafflinethickness` controls the thickness of the staff lines.
See GregorioRef.pdf for full details.
- `\gre@debug`. Writes messages to the log file when the debug flag is
set to true (can be done manually via `\debugtrue`, or via the `debug`
option when loading the gregoriotex package in LaTeX).
- New documentation in PDF: GregorioRef. You can find it in the [release
files](https://github.com/gregorio-project/gregorio/releases).
- A migration guide ([UPGRADE.md](UPGRADE.md))
- This CHANGELOG.
- A Windows batch file which will detect the system setup and create a
report which can be useful in diagnosing installation problems.
Instructions for how to use it appear [under the installation
instructions for Windows on the
website.](http://gregorio-project.github.io/installation-windows.html)
### Deprecated
- OpusTeX writing and GregorioXML reading and writing features will
disappear in next minor release
- The [old website](http://home.gna.org/gregorio/) contains instructions
for old versions of Gregorio only, and will not be updated anymore.
- the `-O` option
- `\includetexscore`, supplanted by `\includescore[n]`
- `\greincludetexscore`, supplanted by `\includescore[n]`
- `\includegabcscore`, supplanted by `\includescore[f]`
- `\greincludegabcscore`, supplanted by `\includescore[f]`
- `\GreSetSpaceBeforeInitial`, supplanted by `\setspacebeforeinitial`
- `\GreSetSpaceAfterInitial`, supplanted by `\setspaceafterinitial`
- `\GreSetAboveInitialSeparation`, supplanted by
`\setaboveinitialseparation`
- `\gresetstafflinefactor`, supplanted by `\setstafflinethickness`
- `greg-book` and `greg-lily-book` engines, supplanted by improved
capabilities of `\includescore` for compiling gabc files at time of
document compilation.
Upgrading:
## 3.0
### TeX Live 2013
Because of changes necessary to future-proof the fonts, please upgrade
to at least TeX Live 2013 if you are using an older version. If the
neumes do not appear or look strange in the output, you may also need to
clear your LuaTeX font cache by using `luaotfload-tool --cache=erase`.
### Score inclusion
When migrating to this release, you should start to use the new
`\includescore` system, as other ways of score inclusion are deprecated
and will start disapear soon. See GregorioRef for details.
#### For users of version 2.4.2
In version 2.4.2, an early version of the feature to auto-compile gabc
score was added. Because of the confusion this caused with old users
upgrading to 2.4.2, the `\includescore` command now works in a
backwards-compatible way so scores created using this command for
versions of Gregorio prior than 2.4.2 should work with no change.
However, for users of 2.4.2, the following changes are necessary:
- If you were using `\includescore[f]`, the equivalent command is now
`\includescore[n]`, but due to this change, you should be able to just
use `\includescore` without the optional parameter.
- If you were using the auto-compile feature, you should use
`\autocompilegabc` in your tex file prior to using `\includescore`.
This is only necessary once and **does not need to be used before each
use** of `\includescore`.
### Custom dimension changes
If you use custom space definitions (`gsp-foo.tex`), the format have
changed, and you must rewrite it completely. See the new
`gsp-default.tex` for an example, and GregorioRef for documentation.
### Color definition
If you want to change color in gabc, using the `<c>` markup is the
safest way, and you should migrate to that, as Gregorio introduced
mechanisms that may break badly formatted color changes (e.g.
`\color{red}foo\color{black}`).
--
✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝
Br. Samuel, OSB
(R. Padraic Springuel)
PAX ☧ ΧΡΙΣΤΟΣ
_______________________________________________
Gregorio-users mailing list
[email protected]
https://mail.gna.org/listinfo/gregorio-users
