Re: FOP DTD attached (updated)

2002-03-06 Thread david

I opened the attached DTD in XML Spy, and the validation failed at:

...
!ATTLIST character
%Aural_Properties_List;
...

element 'character' is undefined.  Is this important?

--

David B. Bitton
[EMAIL PROTECTED]
www.codenoevil.com

Diversa ab illis virtute valemus.
- Original Message -
From: Chuck Paussa [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, March 06, 2002 2:05 PM
Subject: FOP DTD attached (updated)


 DTD lovers

 I've created the attached DTD from the XSL FO W3C documents. I updated the
DTD to allow you to exclude those elements that are not handled by
 FOP. These are fairly clean documents with some additions like enumerated
types for lengths and percentages. The enumerated types do not exclude
values not implemenetd in FOP. The DTD should work well with PSGML. Post any
comments and I'll include them in the next update. [Even the cranky comments
I've gotten so far are useful];-)

 Chuck Paussa





?xml version=1.0 encoding=iso-8859-1?
!--
 This DTD has been developed in order to validate XSL FO documents
 The namespace prefix is xmlns:fo=http://www.w3.org/1999/XSL/Format;.

 In addition, the functionality implemented or not in FOP has been
segregated
 To create an FOP only validating DTD, remove the references marked
%\([a-zA-Z_]+\)_Not;
 I certainly have not exhaustively removed all of the properties not
implemented in FOP.
 If you notice an item that is incorrectly included or excluded, please send
me a note

 The FOP only DTD will not guard against the entering of attribute values
not implemented by FOP
 (Such as fo:leader-pattern=use-content)
 See http://xml.apache.org/fop/implemented.html for more detailed
restrictions

 It has not been well tested.
 For instance, the length attribute is able to be negative for some elements
like margins.
 I have not represented that here.
 I have not added values for the Aural properties
 There are several instances where I've entered %integer_Type; and it should
be positive-integer or number
 The DTD trys to handle the text based rules re: fo:markers, fo:float,
footer and fo:initial-property-set
 But, allows you to do illegal things if you want because I couldn't figure
out how to constrain against the illegal actions.

 Please e-mail your comments to [EMAIL PROTECTED]

--
!-- *** --
!-- Entity definitions for groups of formatting objects --
!-- *** --
!ENTITY % speak_Type
normal|none|spell-out|inherit
!ENTITY % relative_align_Typebefore|baseline|inherit
!ENTITY % empty_cells_Type   show|hide|inherit
!ENTITY % ends_row_Type  true|false
!ENTITY % starts_row_Typetrue|false
!ENTITY % score_spaces_Type  true|false|inherit
!ENTITY % use_font_metrics_Type  use-font-metrics
!ENTITY % position_Type
static|relative|absolute|fixed|inherit
!ENTITY % conditionality_Typeretain|discard
!ENTITY % keep_integer_Type  0|1|2|3|4|5|6|7|8|9|10
!ENTITY % keep_Type
%auto_Type;|%always_Type;|%keep_integer_Type;
!ENTITY % margin_width_Type
%auto_Type;|%length_Type;|%percentage_Type;
!ENTITY % letter_value_Type  auto|alphabetic|traditional
!ENTITY % alignment_Type
baseline|before-edge|text-before-edge|middle|central|after-edge|text-after-
edge|ideographic|alphabetic|hanging|mathematical
!ENTITY % box_alignment_Type
top|text-top|bottom|text-bottom
!ENTITY % alignment_adjust_Type
%auto_Type;|%alignment_Type;|%percentage_Type;|%length_Type;|%inherit_Type;

!ENTITY % alignment_baseline_Type
%auto_Type;|%alignment_Type;|%box_alignment_Type;|%inherit_Type;
!ENTITY % breaks_Type
auto|column|page|even-page|odd-page
!ENTITY % force_page_count_Type
auto|even|odd|end-on-even|end-on-odd|no-force|inherit
!ENTITY % hyphenation_character_Type -|inherit
!ENTITY % table_layout_Type  auto|fixed|inherit
!ENTITY % scaling_method_Type
auto|integer-pixels|resample-any-method|inherit
!ENTITY % displace_Type  auto|none|line|indent|block
!ENTITY % media_usage_Type
auto|paginate|bounded-in-one-dimension|unbounded
!ENTITY % rendering_intent_Type
auto|perceptual|relative-colorimetric|saturation|absolute-colorimetric|inhe
rit
!ENTITY % hyphenate_Type false|true|inherit
!ENTITY % suppress_at_line_break_Type
auto|suppress|retain|inherit
!ENTITY % treat_as_word_space_Type   auto|true|false|inherit
!ENTITY % dominant_baseline_Type
auto|use-script|no-change|reset-size|ideographic|alphabetic|hanging|mathema
tical|inherit
!ENTITY % percentage_Type
.01|.02|.03|.04|.05|.06|.07|.08|.09|.10|.20|.30|.40|.50|.60|.70|.80|.90|1
!ENTITY % px_length_Type
0px|1px|2px|3px|4px|5px|6px|7px|8px|9px|10px|11px|12px|13px|14px|15px|16px|
17px|18px|19px|20px|21px|22px|23px|24px|25px|26px|27px|28px|29px
!ENTITY % integer_Type
0|1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20

Re: FOP DTD attached (updated)

2002-03-06 Thread Chuck Paussa

David,

If you look at the comments at the top of the DTD, you'll find 
instructions on how to strip out those elements not implemented in FOP

Chuck Paussa



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]