Commit 33af03fd authored by Andreas Tille's avatar Andreas Tille

New upstream version 12-248

parent 5f39515d
Aephea AUTHORS file
Aephea was written by Stijn van Dongen.
Aephea's build environment was derived from zoem's, which was written by Joost van Baal.
Contributions are welcome.
This diff is collapsed.
Sep, Wed 5 2012
* aephea-12-248 released.
* The changes for this release can be accessed by loading simpledocument2.zmm
and using http://micans.org/aephea or alternatively the file
mac/doc/webindex.azm as an example.
* Document-level lay-out logic was *removed* from aephea and simpledocument2
and should be supplied externally. Example CSS code is shipped in
contrib/reaper2.css.
Element-level lay-out rules such as used for styling lists are still very
much part of simpledocument2.
* A div with id selector asd_document now spans the entire document,
and a few more css hooks were introduced:
#asd_leftcolumn
#asd_document_outer
#asd_document
#asd_toc
* paragraph macros were updated to be fully CSS-controlled, with classes
p.asd_par
p.asd_cpar
span.asd_cpar_caption
p.asd_car
p.asd_ccar
span.asd_ccar_caption
now available.
Fri, Jan 8 2010
* aephea-10-008 released.
* Aephea is a HTML document framework. The name stands, grandiosely, for
Adaptable Exo-skeleton for Practical HTML Extension and Abstraction.
Aephea documents are written in a language called zoem, which is
a macro/programming language with a strict, compact and elegant syntax.
Aephea provides support for a single output device, HTML. It uses CSS to
a great extent to make document styling easily customized and controlled.
* PUD (Portable Unix Documentation) used to be shipped with zoem itself
but is now part of Aephea. PUD provides limited support for two mini
languages (manuals and FAQs) for two output devices, troff and HTML. The
troff device provides full-fledged UNIX manual pages.
* Backwards incompatible changes in PUD require modification of existing
documents.
- The import has changed. It is now \import{pud/man.zmm} rather than
\import{man.zmm}, similarly \import{pud/faq.zmm}.
- \par and \car with no arguments have been removed, and so
are \cpar#1 and \ccar#1.
- The itemize controls have changed.
NEW | OLD | Behaviour
----------------+-----------------+-----------------------------
{flow}{cascade} | {compact}{0} | Description below item
{flow}{compact} | {compact}{1} | Description follows item
----------------+-----------------+-----------------------------
{interitem}{1} | {contiguous}{0} | Skip between item sections
----------------------------------------------------------------
- The document is now itself encoded as an environment. The pre-amble
and post-ambles have gone (\"man::preamble" and \"man::postamble").
The pre-amble now becomes e.g.
\begin{pud::man}{
{name}{apparix}
{html_title}{apparix, augmenting the shell with directory bookmarks}
{keywords}{cd, change directory, bookmarks, command line, cdpath, subdirectory, tab completion}
{author}{Stijn van Dongen}
{section}{1}
{synstyle}{long}
{defstyle}{long}
{year}{2009}
{day}{18}
{month}{Jan}
{stamp}{09-018}
{tag}{Groovy Gazelle}
}
with post-amble
\end{pud::man}
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
Basic Installation
==================
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring. (Caching is
disabled by default to prevent problems with accidental use of stale
cache files.)
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.
The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'. You only need
`configure.ac' if you want to change it or regenerate `configure' using
a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
documentation.
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. Run `./configure --help'
for details on some of the pertinent environment variables.
You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here
is an example:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
*Note Defining Variables::, for more details.
Compiling For Multiple Architectures
====================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not support the `VPATH'
variable, you have to compile the package for one architecture at a
time in the source code directory. After you have installed the
package for one architecture, use `make distclean' before reconfiguring
for another architecture.
Installation Names
==================
By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
=================
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
==========================
There may be some features `configure' cannot figure out
automatically, but needs to determine by the type of machine the package
will run on. Usually, assuming the package is built to be run on the
_same_ architectures, `configure' can figure that out, but if it prints
a message saying it cannot guess the machine type, give it the
`--build=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:
CPU-COMPANY-SYSTEM
where SYSTEM can have one of these forms:
OS KERNEL-OS
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
use the `--target=TYPE' option to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.
Sharing Defaults
================
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Defining Variables
==================
Variables not defined in a site shell script can be set in the
environment passed to `configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'. For example:
./configure CC=/usr/local2/bin/gcc
will cause the specified gcc to be used as the C compiler (unless it is
overridden in the site shell script).
`configure' Invocation
======================
`configure' recognizes the following options to control how it
operates.
`--help'
`-h'
Print a summary of the options to `configure', and exit.
`--version'
`-V'
Print the version of Autoconf used to generate the `configure'
script, and exit.
`--cache-file=FILE'
Enable the cache: use and save the results of the tests in FILE,
traditionally `config.cache'. FILE defaults to `/dev/null' to
disable caching.
`--config-cache'
`-C'
Alias for `--cache-file=config.cache'.
`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`configure' also accepts some other, not widely useful, options. Run
`configure --help' for more details.
This directory contains source code for the Aephea documentation framework,
in the form of macro packages written in the zoem language. All zoem source
files (with '.azm' and '.zmm' extensions) in the subdirectories of this
directory are copyright (c) 2001-2011 Stijn van Dongen, stijn <at> micans
<stop> org, as are the documentation files derived from the zoem source
files.
This documentation framework is free software; you can redistribute it
and/or modify it under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 3 of the License,
or (at your option) any later version.
This documentation framework is distributed in the hope that it will be
useful, but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General
Public License for more details.
You should have received a copy of the GNU General Public License along with
this program; if not, write to the Free Software Foundation, Inc., 51
Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
## Process this file with automake to produce Makefile.in
## $Id: Makefile.am,v 1.20 2004/06/24 11:43:11 flux Exp $
## all-local: stamp-util
## stamp-util:
## ## do some magic to fiddle with util. util is in cvs in ../util/ ,
## ## not in the zoem tree itself.
## for i in $(top_srcdir)/../util/*.h $(top_srcdir)/../util/*.c; do \
## $(INSTALL_DATA) $$i $(top_srcdir)/util; \
## done
## touch stamp-util
SUBDIRS = . mac
VERSION = @VERSION@
configure.ac: configure.ac.in VERSION
./setversion
EXTRA_DIST = configure.ac.in bootstrap setversion VERSION LICENSE
This diff is collapsed.
no news. read README
Aephea is an HTML authoring framework. It enforces HTML well-formedness
with a simpler and stricter syntax, provides useful extensions and
abstractions as well as facilities for adding new ones, all in a single
unified approach that stays close to HTML itself.
PUD (Portable Unix Documentation) is shipped with Aephea. It provides
mini-languages for authoring Unix manual pages and FAQ documents with output
both in HTML and troff.
Both Aephea and PUD are written in zoem, a high-level macro/programming
language with character filtering capabilities. It is recommended to install
Aephea with
./configure --prefix=$PREFIX.
Files will be installed in $PREFIX/share/aephea, e.g.
$PREFIX/share/aephea/aephea/simpledocument.zmm
$PREFIX/share/aephea/aephea/simpledocument.css
$PREFIX/share/aephea/pud/man.zmm
$PREFIX/share/aephea/pud/faq.zmm
Files with suffix zmm are loaded in Aephea documents like this:
\import{aephea/simpledocument.zmm} \: for HTML document.
\import{pud/man.zmm} \: for (Unix) manual page.
\import{pud/faq.zmm} \: for FAQ.
In order to have zoem find the Aephea definition and CSS files
automatically, install it (from the unpacked zoem sources) with
./configure --with-includepath=$PREFIX/share/aephea --prefix=$OTHERPREFIX
Thanks to:
Joost van Baal. The aephea build environment was derived from zoem's
build environment, created by Joost.
James Clark for writing a free troff implementation -- now GNU's groff.
! when {$hut}{} is used, all widths and lengths are affected, but user should not
have to specify them all.
- once more go over positioning.
absolute requires 'relative or absolute' parent.
- can itemize framework be simplified?
- several classes
- several layers of divs
-> are classes and layers logically and consistenly combined?
- check html positioning for compact item with right align.
:( the fact that new item or \end{itemize} closes the previous item continues to irk.
- itemize:
* nested itemize, control over offsets et cetera. (reaper.azm)
* mcl web page intrinsic,fast etc fast is mis-aligned.
-> itemize left/right alignment classes look weird.
$ \begin{itemize}{
{$flow}{cascade}
{$interitem}{1}
{$textindent}{4}
{$itemmargin}{25}
{$align}{right}
{$class_item}{config_entry}
}
itemmargin does not seem to be working.
/ all classes should have asd_ prefix?
- application: small and flexible frameworks, a bunch of HTML documents
that share certain styling components, terminology.
- magicality: levels of.
two goals aephea: not 'tied to'.
tutorial: e-mail to Duke.
- zpresenter package
12-248
This diff is collapsed.
This diff is collapsed.
#!/bin/sh -e
# $Id: bootstrap,v 1.9 2003/07/17 08:45:50 flux Exp $
#
# bootstrap - script to bootstrap the distribution rolling engine
#
# to build a tarball, ready for distribution, from fresh checked out
# cvs sources, do
#
# automake --add-missing && ./bootstrap && ./configure && make distcheck
#
# this will yield a tarball, e.g. zoem-20020109.tar.gz . Once this has been
# run, one can, after e.g. editing sources, run just
#
# make distcheck
#
# to generate a new tarball. (No need to run ./bootstrap again in this case.)
# After downloading, users do
#
# tar zxf mcl-20020109.tar.gz
# cd mcl-20020109
# ./configure && make
# make install
#
set -x
if test ! -f VERSION
then
./setversion
fi
aclocal \
&& autoheader \
&& automake --verbose --gnu --add-missing \
&& autoconf
This diff is collapsed.
# configure.ac - generated from configure.ac.in by setversion. do not edit
# configure.ac, but edit the master.
# $Id: configure.ac.in,v 1.15 2004/06/09 16:42:58 flux Exp $
# Process this file with autoconf to produce a configure script.
AC_PREREQ(2.50)
AC_INIT(aephea, 12-248, stijn@micans.org)
PACKAGE=$PACKAGE_NAME
VERSION=$PACKAGE_VERSION
AM_INIT_AUTOMAKE($PACKAGE, $VERSION)
# add a `--enable-maintainer-mode' option to `configure'; `maintainer-only' rules turned off by
# default in Makefile.in's
AM_MAINTAINER_MODE
AC_SUBST(PACKAGE)
AC_SUBST(VERSION)
# AC_CONFIG_FILES([])
AC_OUTPUT([
Makefile
mac/Makefile
mac/aephea/Makefile
mac/pud/Makefile
mac/doc/Makefile
mac/contrib/Makefile
])
# $Id: configure.ac.in,v 1.15 2004/06/09 16:42:58 flux Exp $
# Process this file with autoconf to produce a configure script.
AC_PREREQ(2.50)
AC_INIT(aephea, setversion_VERSION, stijn@micans.org)
PACKAGE=$PACKAGE_NAME
VERSION=$PACKAGE_VERSION
AM_INIT_AUTOMAKE($PACKAGE, $VERSION)
# add a `--enable-maintainer-mode' option to `configure'; `maintainer-only' rules turned off by
# default in Makefile.in's
AM_MAINTAINER_MODE
AC_SUBST(PACKAGE)
AC_SUBST(VERSION)
# AC_CONFIG_FILES([])
AC_OUTPUT([
Makefile
mac/Makefile
mac/aephea/Makefile
mac/pud/Makefile
mac/doc/Makefile
mac/contrib/Makefile
])
aephea (12-248-3) UNRELEASED; urgency=low
* NOT RELEASED YET
* FIXME: 12-248 upstream has new files
mac/aephea/{base2,simledocument2}.{zmm,css}, mac/contrib/reaper2.css: check
copyright. Files mac/doc/webindex.{azm,html} have: "Copyright (c) 2012
Stijn van Dongen and Moniek Hopman". update copyright.
-- Joost van Baal-Ilić <joostvb@debian.org> Sun, 25 Nov 2012 23:40:09 +0100
aephea (12-248-2) unstable; urgency=low
* debian/control: fix vcs tags
* debian/control: add missing Breaks+Replaces: zoem-doc, to enable upgrades
from squeeze to wheezy. Thanks Andreas Beckmann. (Closes: #694365)
-- Joost van Baal-Ilić <joostvb@debian.org> Sun, 25 Nov 2012 23:29:07 +0100
aephea (12-248-1) unstable; urgency=low
* New upstream release 12-248.
* No longer mangle upstream version number.
* debian/copyright: fix typo. Thanks lintian.
* debian/control: we honor policy 3.9.3 (no changes needed).
* debian/watch: stricter, no longer match aephea-latest.tar.gz symlink.
* debian/control: update my name.
-- Joost van Baal-Ilić <joostvb@debian.org> Wed, 05 Sep 2012 13:20:12 +0200
aephea (10.008-2) testing-proposed-updates; urgency=low
* debian/control: add missing Breaks+Replaces: zoem-doc, to enable upgrades
from squeeze to wheezy. Thanks Andreas Beckmann. (Closes: #694365)
-- Joost van Baal-Ilić <joostvb@debian.org> Mon, 26 Nov 2012 10:13:51 +0100
aephea (10.008-1) unstable; urgency=low
* First upload (Closes: #620479).
* debian/control: add Recommends: zoem. The package zoem <= 08-248-1 ships
base.zmm, man.zmm, faq.zmm, doc.zmm, ref.zmm and ctr.zmm. Later zoem's
do not. We ship these files in /usr/share/aephea/{aephea,pud}/. You
might need to set ZOEMSEARCHPATH=/usr/share/aephea/pud:/usr/share/aephea
to use this aephea with zoem 10-265-1.
* debian/README.Debian, debian/{pre,post}{inst,rm}: removed (empty template).
* debian/doc-base.pud-faq: fix typo.
-- Joost van Baal <joostvb@debian.org> Thu, 12 May 2011 01:49:18 +0200
aephea (10.008-0.3) unstable; urgency=low
* Non-public release.
* debian/control: fix tags vcs-*.
* debian/control: we honor policy 3.9.1 (was 3.8.4, no changes needed).
* debian/doc-base.*: fix syntax.
-- Joost van Baal <joostvb@debian.org> Sat, 23 Apr 2011 02:14:35 +0200
aephea (10.008-0.2) unstable; urgency=low
* Non-public release.
* debian/control: architecture: s/any/all/.
* debian/{rules,docs}: moved usr/share/aephea/{doc,examples} to u/s/doc/aephea
(reported upstream).
* debian/aephea.doc-base: first shot at adding some content.
-- Joost van Baal <joostvb@debian.org> Sun, 03 Apr 2011 08:37:56 +0200
aephea (10.008-0.1) unstable; urgency=low
* Initial non-public release.
-- Joost van Baal <joostvb@debian.org> Sun, 03 Apr 2011 08:37:56 +0200
Source: aephea
Section: text
Priority: extra
Maintainer: Joost van Baal-Ilić <joostvb@debian.org>
Build-Depends: cdbs, debhelper (>= 7.0.50~), autotools-dev
Standards-Version: 3.9.3
Homepage: http://micans.org/aephea
Vcs-Browser: http://svn.debian.org/wsvn/collab-maint/deb-maint/aephea
Vcs-Svn: svn://svn.debian.org/svn/collab-maint/deb-maint/aephea
Package: aephea
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}
Breaks: zoem-doc
Replaces: zoem-doc
Recommends: zoem
Description: text-based authoring tool for HTML
Aephea is an HTML authoring framework. It enforces HTML well-formedness
with a simpler and stricter syntax, provides useful extensions and
abstractions as well as facilities for adding new ones, all in a single
unified approach that stays close to HTML itself. Some of Aephea's
characteristics are a TeX-like syntax, dictionary stacks, iteration and a
focus on styling via CSS.
.
PUD (Portable Unix Documentation) is shipped with Aephea. It provides
mini-languages for authoring Unix manual pages and FAQ documents with output
both in HTML and troff.
.
Both Aephea and PUD are written in zoem, a high-level macro/programming
language with character filtering capabilities.
.
If you'd like to generate manpages, but don't like troff syntax, and find
Perl's POD too limited, Aephea's PUD is likely useful for you. If you like
your documents to be available in both PDF and HTML, but find Docbook XML
too heavyweight (and aren't really happy with Docbook XML's baroque default
tagnames), you'll like PUD.
This work was packaged for Debian by:
Joost van Baal <joostvb@debian.org> on Sun, 03 Apr 2011 08:37:56 +0200
It was downloaded from:
http://micans.org/aephea/src/
Upstream Author:
Stijn van Dongen <stijn <at> micans <stop> org>
Copyright:
Copyright © 2010 Stijn van Dongen
License:
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 3 of the License, or (at
your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.