Fop-devs,
In spite of the huffing and puffing, my original implementation of
text-decoration was wrong. Such hubris. Currently being corrected in Defoe.
Peter
I looked at the code and I can't see anything wrong
with your suggestion. Unfortunately I'm far from an
expert in this area of the code.
Glen
--- Jeremias Maerki [EMAIL PROTECTED] wrote:
I'm currently looking at implementing
text-decoration. ATM it's
specified as an EnumProperty but should
I'm currently looking at implementing text-decoration. ATM it's
specified as an EnumProperty but should be more like a set of enums with
certain validation rules applied. I'm unsure about the approach. If
anyone already has an idea how it should look like I'd appreciate any
insight.
My first idea
Jeremias Maerki wrote:
I'm currently looking at implementing text-decoration. ATM
it's specified as an EnumProperty but should be more like a
set of enums with certain validation rules applied. I'm
unsure about the approach. If anyone already has an idea how
it should look like I'd
Victor Mote wrote:
Jeremias Maerki wrote:
I'm currently looking at implementing text-decoration. ATM
it's specified as an EnumProperty but should be more like a
set of enums with certain validation rules applied. I'm
unsure about the approach. If anyone already has an idea how
it should look
/show_bug.cgi?id=25275
fo:page-number ignores text-decoration=underline attribute
Summary: fo:page-number ignores text-decoration=underline
attribute
Product: Fop
Version: 0.20.5
Platform: Other
OS/Version: Other
Status: NEW
Jeremias Maerki wrote:
Can we sketch that on the Wiki in some simple way? Defining some Java
interfaces and things like that? Anyway, as you mentioned we should sort
out things like Session and Document on another page first.
OK, I just put a proposal out there in the section discussing
On 13.01.2003 19:18:18 Victor Mote wrote:
Jeremias Maerki wrote:
Can we sketch that on the Wiki in some simple way? Defining some Java
interfaces and things like that? Anyway, as you mentioned we should sort
out things like Session and Document on another page first.
OK, I just put a
On 11.01.2003 18:35:37 Victor Mote wrote:
Keiron Liddle wrote:
If I understand it correctly we could have:
- multiple output targets for one rendering run
- targets with the same font metrics can layout to a common area tree
- targets with similar or substitute metrics could force
Victor Mote wrote:
Jeremias Maerki wrote:
It is very possible that I am missing something, but our memory-lean
event-based model would seem to dictate either 1) parsing the document
twice, or 2) not allowing multiple output formats in the same document.
I think my approach could work in this
Keiron Liddle wrote:
If I understand it correctly we could have:
- multiple output targets for one rendering run
- targets with the same font metrics can layout to a common area tree
- targets with similar or substitute metrics could force layout
to one area tree
- other targets can have
Keiron Liddle wrote:
Have you managed to work out how the underline/overline should work, for
example when there are embedded inline areas that contain a different font,
colour or baseline.
Well, not really. I just wanted to make something simple done :)
afaiu different font/colour/etc
Victor Mote wrote:
There are some big picture things that we should probably address:
1. (Biggest of all) Do we have users that need to be able to do this? Are
the performance gains that they might get worth the pain on our end?
Apart from this is the fact that our processing model for any
Hi Victor
On 09.01.2003 19:09:17 Victor Mote wrote:
snip/
Let me say up front that I am going to follow your lead here.
I'm not taking the lead. We'll work together on this. I see that you
have some ideas yourself, so let's see what we can come up with together.
As far as I can see from your
properly discuss things like Session, Document, Rendering run, FOP
instances etc. Where to cache what? What objects/services hold/provide
In my mind Document and Rendering run (as defined in the glossary) are
probably the same thing (??). I added something called Rendering instance to
Hi Keiron
If I understand it correctly we could have:
- multiple output targets for one rendering run
- targets with the same font metrics can layout to a common area tree
- targets with similar or substitute metrics could force layout to one area tree
- other targets can have different area
I've added my current thoughts to a Wiki page for those interested in
this discussion:
http://nagoya.apache.org/wiki/apachewiki.cgi?FOPFontSubsystemDesign
You're all welcome to participate.
Jeremias Maerki
-
To unsubscribe,
Jeremias Maerki wrote:
A Wiki is probably easier to work with in this case. CVS update, edit,
CVS commit, Website update is a lot of work. I'll start a Wiki page and
add my thoughts to it. We can always transfer the contents back to XML
later.
Good. I don't think I knew what a wiki was when
- we've got unused TextState class along with
TextInfo that includes text-decoration info already. Lets get rid of TextState ?
And what about rendering, does pdf support text-decoration directly or we have
to draw lines as in the branch?
Jeremias Maerki
Jeremias Maerki wrote:
Wait a minute! I'm just about to commit a huge bunch of changes which
includes TextInfo/FontState stuff. Not that I changed a lot. I've just
got rid of stuff that wasn't used and I don't want you to have to change
a lot again after my commit.
That's fine.
--
Oleg
Hello!
How are we going to process underline/overline etc stuff?
It's a little bit confusing - we've got unused TextState class along with
TextInfo that includes text-decoration info already. Lets get rid of TextState ?
And what about rendering, does pdf support text-decoration directly
Hi Oleg
On 08.01.2003 13:11:34 Oleg Tkachenko wrote:
How are we going to process underline/overline etc stuff?
It's a little bit confusing - we've got unused TextState class along with
TextInfo that includes text-decoration info already. Lets get rid of TextState ?
And what about rendering
Jeremias Maerki wrote:
TextInfo looks better but could IMO be merged with FontState which only
hold the font name and size and a link to the FontMetrics. Anyway, I
think this merged class will be a candidate for the Flyweight pattern so
we don't generate so many TextInfo/FontState objects
/show_bug.cgi?id=5655
text-decoration cannot take multiple values
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Additional
/show_bug.cgi?id=1923
text-decoration does not work
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
The editors,
7.16.5 text-shadow has offsets defined in terms of horizontal
distance to the right and vertical distance below the text.
The section also specifies:
Inherited: no, see prose
There is no mention of inheritance in the prose of section 7.16.5.
7.16.4 text-decoration, likewise
/show_bug.cgi?id=4492
text-decoration=underline on fo:block ignored
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
Tore Engvig wrote:
Christian Geisert wrote:
Hi,
this patch adds text-decoration support for blocks. There still
some things
I want to do (like inherit text-decoration from a parent inline,
problems with
hyphenation and nbsp).
Actually I think fop supports nbsp (more or less
Hi,
this patch adds text-decoration support for blocks. There still some things
I want to do (like inherit text-decoration from a parent inline, problems with
hyphenation and nbsp).
Christian
Index: docs/examples/fo/textdeko.fo
/show_bug.cgi?id=4492
text-decoration=underline on fo:block ignored
--- Additional Comments From [EMAIL PROTECTED] 2001-11-28
05:04 ---
Christian Geisert [EMAIL PROTECTED] sent this to fop-dev:
But to underline one must use fo:inline, right??
At the moment: yes!
I have started coding
/show_bug.cgi?id=4492
text-decoration=underline on fo:block ignored
Summary: text-decoration=underline on fo:block ignored
Product: Fop
Version: 0.15
Platform: Sun
OS/Version: Solaris
Status: NEW
Severity: Minor
Priority
Title: Message
It appears as if
between .12 and the current cvs the last parameter for fontstate which was
textdecoration in .12 is now only supporting text-variant and the
text-decoration is lost as it is not passed through. Was this picked up
somewhere else and I'm missing it ?
John
numbers.
fo:block
break-before="auto" space-before.optimum="12pt"fo:inline
text-decoration="underline"fo:tablefo:table-column
column-width="155.708mm" column-number="1"/fo:table-column
column-width="2.324mm" column-number=&q
John Wyman wrote:
This used to work in .12 doesn't work in ,18 and up, I think it should, could
someone look into it, please.
I'm quite sure it did not work in 0.12 !!
(And as I have done the code for text-decoration I should know ;-)
Underline isn't done and I can't move the underline
34 matches
Mail list logo
