I have only 20 lines of text in the test document.
Still haven't setup my PC for using xsltproc/saxon will do it tomorrow and
get back...
~spr
Bob Stayton wrote:
>
> Hmm, I cut and pasted your attribute-set into a simple customization layer
> based on 1.73.2 fo/docbook.xsl, processed a short b
George,
Thanks. Your suggestions worked just right. The particular
fragment I was working with had a root element of chapter,
which didn't match, so I added a rule to match on any fragment
with the docbook 5.0 namespace. That took care of things.
In fact, I had looked at the document type assoc
On 27 sept. 07, at 19:45, Mauritz Jeanson wrote:
...
Yes, it works. Thanks a lot for your help, and sorry to answer so late
but I was out of my office and home for the last three weeks.
I will try to redefine calloutlist in my custom stylesheet to make the
change for all the callout
Bob,
Thanks so much for your reply.
Here is how the include is being done:
http://www.w3.org/1999/XSL/Transform";
xmlns:fo="http://www.w3.org/1999/XSL/Format";
version="1.0">
I see that you mention a line in your book - "process the spec file with the
special styleshe
Hmm, I cut and pasted your attribute-set into a simple customization layer
based on 1.73.2 fo/docbook.xsl, processed a short book with xsltproc and
fop 0.94, and it worked. I also processed it with the fop shell script,
and that worked as well. That is, the legalnotice title was rendered in
r
> -Original Message-
> From: spr
>
> This didn;t work either:
>name= "header.table.properties">
>name = "table-layout">fixed
>name = "width">100%
>name = "background-color">yellow
>name = "alignment-adjust">alphabetic
>
Elliotte Harold wrote:
[...]
I do expect that real semantic markup may not fit in a toolbar. Menus or
palettes may be a better option than buttons. I do like the compromise
that was suggested where the i button drops down to a menu, and the user
has to choose the *reason* they're italicizing so
This didn;t work either:
fixed
100%
yellow
alphabetic
after
Added attribute alignment-adjust in addition to display-align as well...
:( spr
There is no "vertical-align" property in XSL-FO. You are looking for
display-align, whose enumerated values are:
auto | befor
Dear Dick,
The document type is determined automatically based on a set of mapping
rules. The rules are specified in the definition of the document type, see
Options->Preferences -- Document Type Association
select user role to Developer
click on a document type, DocBook 5 for instance
click on
Did not work :(
red
black
Did try to go thru the fo/titlepage.xsl -> formal.object.heading ->
formal.title.properties.
I believe that it should have workerd, but like some other issues that I
have posted, i am loosing faith the the 'fop'. Will setup and use standa
Scott Hudson wrote:
I think we're splitting hairs over 1 element in DocBook, 3 in DITA, and
however many equivalents in infinite DTD/RNG/XSD schemas. There is,
obviously, limited space in the UI. Why are you so opposed to having
maps to 3 very familiar, commonly used buttons? And again, this i
Hi
Yes, sorry that is what I meant - convert the files to
Windows 1254. The same applies to other languages.
Bob Stayton wrote:
>
> Converting the text in the HHC and HHK to Windows 1252 would not be
> possible, because the Turkish in the examples I am using contain a small
> dotless i charac
12 matches
Mail list logo
