On Nov 13, 2006, at 11:06, Andrejus Chaliapinas wrote:
I've tested Andreas approach with tables and column numbers/spans
but later
found it as very particular font specific (correct chars per tab
calculation
having in mind possible different text styles is almost equal to
the task of
spac
Jeremias Maerki wrote:
Just be prepared that they may wrinkle their noses.
I'd expect them to do exactly this. How should tabs mix with, say,
centered text, or BIDI stuff? I'm not convinced it's worth the
additional complexity of the spec.
J.Pietschmann
Jeremias,
> You can also
> place your wish/requirement for tabs there so it can be considered for
> XSL-FO 2.0. Just be prepared that they may wrinkle their noses.
> [1] http://lists.w3.org/Archives/Public/xsl-editors/
Thank you for pointing there. I'll try to post my feature request.
> Is it? I
On 13.11.2006 11:06:51 Andrejus Chaliapinas wrote:
> Jeremias,
>
> > In this case, if the XML format is fixed and cannot be changed at the
> > source, I don't think that XSL-FO is capable of rendering this content.
> > I'd check if you can't change the XML format to process in the first
> > place
Jeremias,
> In this case, if the XML format is fixed and cannot be changed at the
> source, I don't think that XSL-FO is capable of rendering this content.
> I'd check if you can't change the XML format to process in the first
> place. If not, I wouldn't use XSL-FO but another format which support
Andreas,
Thanks a lot for your XSL sample. I'll try to play around it during upcoming
week. Quick test on it so far showed me that line 3 from my original sample:
++++
blabla: text3 after 2 tabs
and this XML corresponding to it:
blabla:
t
On Nov 12, 2006, at 13:25, Jeremias Maerki wrote:
Ok, so you don't just have a simple list of name/value pairs that
happen
to be separated by a tab element. You rather have arbitrary
type-writer-style text. That makes it a lot more complicated, at least
for XSL-FO.
Well, I've already been pl
Ok, so you don't just have a simple list of name/value pairs that happen
to be separated by a tab element. You rather have arbitrary
type-writer-style text. That makes it a lot more complicated, at least
for XSL-FO.
In this case, if the XML format is fixed and cannot be changed at the
source, I do
Andreas,
> Can you show us the non-transformed source nodes for those lines?
> The tab-stops, I presume, correspond to some marker in the source XML
> (a tab character?).
Here is how that corresponding to my sample XML looks like:
blabla:
text1 after one tab
b
On Nov 10, 2006, at 20:18, Andrejus Chaliapinas wrote:
That would be the
case if you needed different tab-stops for different lines. In the
example the tab-stops are all the same
My sample was just the easiest one to get your thoughts on it. But in
general case I really need to have different
Andreas,
> That would be the
> case if you needed different tab-stops for different lines. In the
> example the tab-stops are all the same
My sample was just the easiest one to get your thoughts on it. But in
general case I really need to have different tab-stops for different
lines/blocks.
In g
On Nov 9, 2006, at 10:31, Jeremias Maerki wrote:
Hi Andrejus / Jeremias,
Besides that I think it would be rather difficult to implement. I'd
rather not introduce tab stops in FOP. But I don't know what the
others
think.
Seems quite awkward to me as well, and only really feasible in case
Jeremias,
> I'd set the
> provisional-distance-between-starts property depending on the number of
> characters. You won't get the exact same effect but I think it should be
> near enough with little effort in XSLT and no hacking into FOP,
> introducing a feature that's difficult to implement and c
> Ok, I can see why you would want tabs here. Tables are probably a little
> overkill here. What I would do in this case is to use list-block and
> count characters in the title column. I'd set the
> provisional-distance-between-starts property depending on the number of
> characters.
Yes, list-bl
Ok, I can see why you would want tabs here. Tables are probably a little
overkill here. What I would do in this case is to use list-block and
count characters in the title column. I'd set the
provisional-distance-between-starts property depending on the number of
characters. You won't get the exact
> Maybe if you illustrated your problem with some visuals we could give a
> few suggestions. I'm pretty sure your problem can be solved without tabs.
Ok, here is my very simple visualization (+ sign is used to mark default tab
stop position).
+++++++
blabla: text1 a
At any rate, this FO could not be called fo:tab because it's
non-standard and must not be in the fo namespace. ODF uses text:tab-stop
(Namespace URI: urn:oasis:names:tc:opendocument:xmlns:text:1.0).
Something like that could make sense for RTF output in certain
situations (as output element) but d
17 matches
Mail list logo
