| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Published version is `v1.0'.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
source directory `<groff_src_dir>/contrib/lilypond' and newly
install `<groff_src_dir>/contrib/glilypond', which now has many
files. The new version starts at `v1.0'.
* m4/groff.m4, configure.ac: Add libdir information for
`glilypond'.
* Makefile.in: Add `<groff_src_dir>/contrib/glilypond'.
Run `autoconf'.
`glilypond' can now be installed to the system.
Version will now be v1.*. All former files of versions v0.*
vanished or were renamed.
* ChangeLog.0x: old `ChangeLog' file for the old `groff_lilypond'
versions v0.*. In the future, this file won't be changed any
more.
* ChangeLog: New file. It is this file. It displays the history
of `glilypond' versions v1.* or later.
* glilypond.pl: New main Perl file written from
`groff_lilypond.pl' in a totally different way. It is split now
into 4 Perl files.
* args.pl: New Perl file. It handles the command line options for
a run of `glilypond.pl'.
* oop_fh.pl: New Perl file. OOP handling of file handles.
* perl_test.pl: Test whether the actual Perl program has a
suitable versions. For `Makefile.sub' and `glilypond.pl'.
* subs.pl: New Perl file. Defines the global subs for
`glilypond.pl'.
* Makefile.sub: Newly written `Makefile' for this subdirectory of
`groff'. `glilypond' should be able to be installed by `make'
with this file.
* glilypond.man: Newly written man-page for `glilypond'.
* README.txt: New file about the installation.
|
|
|
|
|
|
| |
(GROFF_FONT_FILES): Avoid installing Makefile.sub.orig when it's
around.
(install): Create $(DESTDIR)$(fontsubdir)/util when missing.
|
| |
|
|
|
|
|
|
| |
New options: -e|--eps_dir, -l|--license, -k|--keep_files, -p|--prefix=...,
-t|--temp_dir=...
Add section SEE ALSO to man-page.
|
| |
|
|
|
|
| |
Reported by Jim Avera <james_avera@yahoo.com>.
|
|
|
|
|
|
|
| |
New code with Perl references.
New options: --usage, -V|--Verbose|--verbose, --file_prefix=...,
-o|--output=..., --temp_dir=...
Perl >=5.10.0 needed.
|
| |
|
|
|
|
| |
allowed.
|
|
|
|
|
|
|
| |
* groff_lilypond_pl: Major rewrite.
New options: --file_prefix, --temp_dir, and --license.
* groff_lilypond.man: documents the new features.
|
| |
|
|
|
|
| |
Reported by Jim Avera <james_avera@yahoo.com>.
|
|
|
|
| |
Reported by Jim Avera <james_avera@yahoo.com>.
|
| |
|
|
|
|
|
|
| |
.lilypond include ...
The argument handling was improved.
New version is groff_lilypond v0.3
|
|
|
|
|
| |
There are now 2 modes for generating EPS files: --ly2eps (the new default)
and --pdf2eps (the old version from v0.1).
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*src/devices/grops/psrm.cpp (resource_table): Add `fontset'.
(resource_manager::read_resource_arg): Do a case insensitive
comparison. The PostScript Reference Manual gives the following
example for a CFF resource (example 5.7):
%!PS-Adobe-3.0 Resource-FontSet
%%DocumentNeedResources: ProcSet (FontSetInit)
%%Title: (FontSet/CFFRoman27)
%%Version: 1.000
%%EndComments
%%IncludeResource: ProcSet (FontSetInit)
%%BeginResource: FontSet (CFFRoman27)
/FontSetInit /ProcSet findresource begin
%%BeginData: 622532 Binary Bytes
/CFFRoman27 622503 StartData
... 622,503 bytes of binary data ...
%%EndData
%%EndResource
%%EOF
Note the `ProcSet' and `FontSet' keywords. While the old DSC
(Document Structure Convention) documentation doesn't cover
`FontSet' at all (the DSC documentation predates the invention of
CFF), it describes only `procset' (all letters downcase), and it
also says that the DSC parser works in a case sensitive manner.
In other words, `ProcSet' is not valid according to the DSC
documentation, only `procset' is. So much about today's validity of
DSC... This patch adapts grops's code to the PostScript reality.
(resource_manager::do_begin_data): Fix typo (present since the
beginning) which prevented correct handling of binary data.
|
| |
|
|
|
|
|
|
|
|
|
| |
`.lilypond start' and `.lilytpond end'.
These parts are tranformed into eps-files that can be displayed with `.PSPIC'.
There is a Perl-program `groff_lilypond.pl' and a corresponding man-page.
Both files are found in `groff/contrib/lilypond'. They will not be installed
so far, but can be used from the sourcei directory.
|
|
|
|
|
|
|
|
|
|
|
|
| |
=======================
* NEWS, REVISION, doc/groff.texinfo, doc/webpage.ms: Updated.
* configure: Regenerated.
* doc/texinfo.tex: Updated from `texinfo' repository.
* src/roff/groff/groff.cpp (main) <'v'>: Update copyright year.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
* src/preproc/html/pushback.cpp (pushBackBuffer::pushBackBuffer,
pushBackBuffer::~pushBackBuffer): Abort if `dup' fails.
|
| |
|
| |
|
|
|
|
| |
From Gilles Espinasse <g.esp@free.fr>.
|
| |
|
| |
|
|
|
|
| |
Problem reported by Omari Norman <omari@smileystation.com>.
|
| |
|
|
|
|
|
|
|
|
|
| |
* Makefile.in: Use $(top_srcdir) where appropriate.
* Makefile.sub (M4MACROS): Add `fcntl-o.m4' and `localcharset.m4'.
* font/devpdf/Makefile.sub (UTILFILES): Removed, unused.
(MOSTLYCLEANADD): Add `BuildFoundries'.
* src/devices/gropdf/Makefile.sub (MOSTLYCLEANADD): Add `pdfmom'.
|
| |
|
| |
|
|
|
|
| |
Trivial fixes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With the old pdfmark there are gaps between two of the lines, but
with the new version they disappear. The use of `.br' and `.in 0'
is arbitrary any request which causes an implicit break could be
used. Two breaks together only produce one line break, but if there
is an intervening `\X' then the second break finds the line buffer
not empty and generates another line break.
Using `\!' does alter the position of the pdfmark lines in the
intermediate file sent to grops (the pdfmark lines are output
immediately rather than being serialised through the output line
processing), but this has no effect since the contents of the
pdfmark line stay the same. It is the contents which determine
where bookmarks jump to not the position of the record in the input
stream to grops.
I initially used `.output', but hit a snag if a pdfbookmark occurs
before the document starts to output (message saying to insert an
explicit `.br'), this is quite likely for things like `.pdfinfo
/Author' which occur at the top of the document. So I'm using the
`\!' escape.
|
|
|
|
| |
files and their section.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
grops driver defaults to round linecaps and linejoins, gropdf
incorrectly used butt caps and miter joins.
(Since the MOM package expects to use butt caps and miter joins
(emitting the necessary postscript code to change the caps and
joins), gropdf now parses the same postscript commands.)
* src/devices/gropdf/gropdf.man: Document the handling of linecaps
and linejoins.
* tmac/pdf.tmac (pdfbookmark): Fix bug where the current
PDFOUTLINE.FOLDLEVEL may not be honoured if warnings of the type
macro warning: adjusted level n bookmark; should be <= n
Added copyright and mention debt owed to Keith Marshall for original
`pdfmark.tmac', upon which `pdf.tmac' is largely based.
* font/devpdf/Foundry.in, font/devpdf/util/BuildFoundries.pl
(LocateFile): The font for EURO had the wrong entry in the
`download' file (it pointed to The font in the build directory,
which is wrong). It has always been permissable to include a path
along with the font name in the Foundry file, but until now the font
had to exist to be valid. It is now permitted to start the path
with an asterisk which tells BuildFoundry to use the path/filename
in the download file without checking if the font exists. This
allows the font to be found in `../devps' even though it is not
there during the build (if source and build are different), but will
be there after the install.
|
| |
|
|
|
|
|
|
|
| |
Problem reported by Andy Spencer <andy753421@gmail.com>.
* src/preproc/eqn/pile.cpp (pile_box::compute_metrics): Fix
rounding.
|
| |
|
| |
|