entrouvert
/
expression
Archived
17
0
Fork 0
Code Issues Pull Requests Releases Activity
1,054 Commits 1 Branch 0 Tags 3.7 MiB
Commit Graph

20 Commits

Author SHA1 Message Date
sebd 3ee673c273 preliminary support for SVG (used with XQuery in supplied example) 2005-05-17 15:07:45 +00:00
sebd ee2b28615e Added URL for DB XML 2 debian packages. 
Simplified installation steps.
 2005-05-09 15:09:08 +00:00
sebd 17614641a6 libxml2 version fixed in sarge 2005-02-17 09:22:43 +00:00
sebd 76c18b110a Recent libxml2 required, and now in Sid. 2005-02-08 13:22:20 +00:00
sebd f236ed7e2f Expression currently requires libxml2 packages from experimental. 2005-01-23 20:10:58 +00:00
sebd 62653ebb54 new path to dbxml packages 2004-07-27 08:48:11 +00:00
sebd c309273f3e Documentation pointers for new users 
Removed outdated doc, now replaced by online doc
 2004-07-15 08:02:47 +00:00
sebd ac8cc4527e added the missing config file argument 2004-07-12 10:49:34 +00:00
eraviart b7de752211 OOo now uses uTidyLib <http://utidylib.berlios.de/> to produce a valid XHTML 
document instead of an invalid one (that Fred's improved xslt couldn't
handle anymore).
 2004-06-20 15:30:45 +00:00
sebd 89e99ed79d reflecting latest changes in setup.py 2004-06-15 15:58:36 +00:00
sebd ec0b25b71e setup.py now installs index.xml files under share/expression/* 2004-05-27 09:47:19 +00:00
aducou f89baba807 Completed the "Installing" part of the readme. 2004-05-26 16:21:02 +00:00
sebd 6a0e03d1d3 The recipe to make Expression work for me 2004-05-25 07:24:49 +00:00
sebd d77b0d62a3 Adding index.xml files in installation 
This is a temporary fix that does not fix everything
 2004-05-24 13:32:30 +00:00
sebd bde385c9a8 updated in a failed attempt to make things work on my machine 2004-05-24 13:17:40 +00:00
eraviart 42a4a98f59 Added XHTML DTDs & entities as XML catalogs. These catalogs are handled the 
Debian way <http://debian-xml-sgml.alioth.debian.org/>.


Q: Why do you use manage XML catalogs the standard way instead of libxml2 way?
A: Because the Debian way is the standard (Oasis) way and it is partially
incompatible with libxml2 way.

Q: Why do you use XML catalogs?
A: Because I needed to store XHTML entities definitions in the local
filesystem.

Q: Why do you need to store XHTML DTDs & entities definitions in the local
filesystem?
A: For speed reasons. Otherwise calls to libxml2 function xmlReadDoc with
option XML_PARSE_DTDLOAD require HTTP calls to get the DTD and its entities.

Q: Why do you need to use xmlReadDoc function with option XML_PARSE_DTDLOAD?
A: Otherwise, the parsing of XHTML files fails when the files contain
entities like &eacute;, etc.

Q: Why are entities definitions needed? You don't need entities substitution
when parsing XML & XHTML files.
A: Because after spending several hours testing and reading libxml2
documentation, I discovered that even when not substituting entities,
libxml2 needs to know their definitions (the reason is it stores both
entities declarations and substitutions inside XML tree. See
http://xmlsoft.org/entities.html).

Q: Why do you use xmlReadDoc instead of xmlParseDoc?
A: Because after spending several hours testing and reading libxml2
documentation, I discovered that xmlParse functions are deprecated.

Q: Why don't you use htmlParseDoc (or htmlReadDoc) anymore to read XHTML
files? They worked well with entities without requiring DTDs.
A: Because html(Parse|Read)Doc ignore namespace declarations.

Q: Why don't you ignore namespace declarations when parsing XHTML files?
A: Because XHTML files are XML files. And we need to differentiate XML tags
with and without namespaces.

Q: Why did you repair XHTML namespaces handling today.
A: Because Fred asked for it yesterday: "je crée un fichier xml, je ne
spécifie pas de namespace, pq l'attribution à l'holder et à l'élément
du namespace xhtml ?".

Q: Did you spent the whole day programming this small feature request?
A: No, I also wrote this FAQ.
 2004-05-23 23:13:05 +00:00
sebd 63bafff737 Proudly added a link to my brand new lintian-friendly dbxml package 2004-05-21 08:39:04 +00:00
sebd 2882a54f05 Corrected to support current situation 2004-05-19 09:23:45 +00:00
fpeters a81856e24e minor formatting issues; links to W3C specs 2004-02-11 19:14:13 +00:00
sebd 6d7933215d Initial version 2004-02-11 18:42:14 +00:00