1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
-*- coding: utf-8 -*-
------------------------------------------------------------------------
Understanding codecs!
All XML files in the Catalogue now identify themselves as utf-8 with:
<?xml version='1.0' encoding='UTF-8'?>
The default for XML is utf-8, however emacs seems to default to
latin-1 (which is an alias for iso-8859-1). All Catalogue code
generates utf-8 HTML encoding using:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Without the utf-8 specification the utf-8 characters may not be displayed
correctly (depending on the settings of the server).
The following is latin-1 and is an example from auth:charpentier
(pst-infixplot)
Jean-Cme
The following is utf-8 and is an example from auth:schoepf (moreverb)
Schöpf
The line at top of this file tells Emacs the apporiate coding to use
for this file.You could change the utf-8 to latin-1 and you will see
the correct characters for the auth:charpentier example above, but
then not for auth:schoepf.
Using utf-8 in forms is detailed in
http://www.w3.org/International/questions/qa-forms-utf-8
------------------------------------------------------------------------
To Do
gencat no longer needs to generate catalogue.xml (in fullcat instead)
move from FromXmlFile (deprecated) to Reader.
New element CATEGORY (main classification): page layout/page margins/...
New element SUBCATEGORY - allow multiple
Generate BYTOPIC via the same code base (gencat) for conformity.
Generate Full version - maybe not - work on a PDF version.
Add license pages for license categories missing: gfdl.
Allowing HTML in the description element seems to mix presentation and
content. This remains an issue to be resolved.
Some old entries have a "No caption." caption! We should replace these
with just no caption!
Would be worth considering versions of the dtd, so the .xml's won't
parse unless the versions agree. That is, it might make sense to name
the file "catalogue-2.00.dtd".
Move to using a doctype. Maybe something like <!DOCTYPE entry PUBLIC
"-//IDN ctan.org//DTD description of TeX packages//EN"
"../catalogue-2.00.dtd"> It gives more freedom about where to put the
files, is all. For instance, we are then not locked into having the
dtd in the directory above where the .xml is at that moment.
Need a place to put my fields like: <status key="companion"
value="chapter 5">, or <status key="primary function" value="LaTeX
> Page layout > Margins">. This conflicts with XML philosophy
to not take advantage of the structure enforcement in the parser, but
it is a way of passing on the kind of extra information some are keen
on. Is there a better way? What is this trying to capture?
|
