Re: [PATCH] doc validation fix

2003-01-13 Thread Jeremias Maerki

On 12.01.2003 11:40:57 Bernd Brandstetter wrote:
 After having tried to understand how fop works by just reading the code for 
 a couple of hours now, FOrtress inevitably comes to my mind ;-)
 (in the sense of: Not easy to get in, at least for a newbie)

:-) Unfortunately, Fortress is already taken by the Apache Avalon
project for one their new containers. I bet they wouldn't be happy to
hear your association with the name.

Let's be serious again: What do you think could be improved to make FOP
easier to get in?


Jeremias Maerki


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




Re: [PATCH] doc validation fix

2003-01-13 Thread Jeremias Maerki

On 12.01.2003 04:59:36 Jeff Turner wrote:
 On Sat, Jan 11, 2003 at 05:43:37PM +0100, Jeremias Maerki wrote:
  Hi Jeff
  
  I've applied your patches locally. Thanks. Everything's ok with the
  first one, but with the second one I'm having problems (not your fault!):
  - I had to add adjust the inline DTD of skinconf.xml to include the role
attribute:
!ELEMENT credit (name, url, image, width?, height?)
!ATTLIST credit role CDATA #IMPLIED
 
 Oops yes, sorry.  Attached is a fix with DTD mods.

Applied, thanks.

  - The credit element produces a rather ugly FOP logo.
 
 If you upgrade your Forrest, the logo won't appear[1].  The @role=pdf
 in skinconf.xml means the credit only applies to PDFs.  Earlier versions
 of Forrest didn't know about this, so rather than display a broken image,
 I threw in the current FOP logo.

Ok, I've upgraded Forrest again and the logo disappeared.


Jeremias Maerki


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




RE: [PATCH] doc validation fix

2003-01-13 Thread Victor Mote
Oleg Tkachenko wrote:

 I like it. First of all FOP is well-known among the whole xml
 community for ages (what costs much) and secondly fop word has a

Yes, this is the primary consideration. The only reason why I mention it now
at all is that changing such things is always better done sooner rather than
later.

 Entry Word: fop
 Function: noun
 Text: a man who is conspicuously fashionable or elegant in dress or
 appearance felt contempt for the mincing overdressed fop
 Synonyms Beau Brummel, blood, buck, coxcomb, dandy, dude, exquisite,
 gallant, lounge lizard, macaroni, petit-maƮtre, popinjay
 Related Word fashion plate, silk stocking; blade, cavalier,
 man-about-town, spark, sport, swell; ladies' man, lady-killer, masher
 Idioms man of the world

   I never have a problem writing it, but when
  speaking it, I cannot make my mouth say fop, but invariably say
  eff-oh-pee instead.
 May I ask why? (Sorry, after spending the whole day in the beach I'm a
 liitle bit stupid :)

It must be a cultural thing. The dictionary definition you gave should tell
the story well enough -- see the example felt contempt for the mincing
 The word is a pejorative, but perhaps more so in my part of the world,
where calling someone a fop or a dandy might be fighting words. In my
mind it connotes sissy on one end of the scale and big hat, no cattle on
the other. This is all partially mitigated by the fact that the word is
pretty much in disuse, so maybe nobody else knows what it means.

Finding myself in the minority, I withdraw the question. I intended no
offence. As a workaround, please don't be offended if I continue to treat
the name as an acronym instead of a word.

Victor Mote



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




Re: [PATCH] doc validation fix

2003-01-13 Thread Bernd Brandstetter
On Monday 13 January 2003 11:05, Jeremias Maerki wrote:
 On 12.01.2003 11:40:57 Bernd Brandstetter wrote:
  After having tried to understand how fop works by just reading the
  code for a couple of hours now, FOrtress inevitably comes to my mind
  ;-) (in the sense of: Not easy to get in, at least for a newbie)
 
 :-) Unfortunately, Fortress is already taken by the Apache Avalon

 project for one their new containers. I bet they wouldn't be happy to
 hear your association with the name.

 Let's be serious again: What do you think could be improved to make FOP
 easier to get in?

Design documentation :-)
When I clicked on the Architecture and Design links, I had expected a 
bit more than 20 to 30 lines of text. But I must admit that I have totally 
overlooked the Understanding the design section which is a bit more 
verbose.
Still, it would be nice to have something in the style of the Alt design 
description - which I think is really great - for the standard design 
too.

Regards,
Bernd



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




Re: [PATCH] doc validation fix

2003-01-13 Thread Peter B. West
Victor Mote wrote:


It must be a cultural thing. The dictionary definition you gave should tell
the story well enough -- see the example felt contempt for the mincing
 The word is a pejorative, but perhaps more so in my part of the world,
where calling someone a fop or a dandy might be fighting words. In my
mind it connotes sissy on one end of the scale and big hat, no cattle on
the other. This is all partially mitigated by the fact that the word is
pretty much in disuse, so maybe nobody else knows what it means.

Finding myself in the minority, I withdraw the question. I intended no
offence. As a workaround, please don't be offended if I continue to treat
the name as an acronym instead of a word.


Victor,

Re my comment on this, I thought I should warn you that I am addicted to 
ironical jokes, which can be a dangerous habit with email.  I dislike 
emoticons, probably because I am more of a snob than I like to admit, 
but also because they seem to me to discourage any attempt either to 
write or to read the subtle - or the ironical! - from email.  An 
advantage of the longevity of a forum like this is that we get to know 
each other's style, so I hope that my un-emoticoned attempts at humour 
are read as such.  I'll see if I can squeeze one out.

,; :) ;,

Peter
--
Peter B. West  [EMAIL PROTECTED]  http://www.powerup.com.au/~pbwest/
Lord, to whom shall we go?


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



RE: [PATCH] doc validation fix

2003-01-13 Thread Victor Mote
Peter B. West wrote:

 Re my comment on this, I thought I should warn you that I am addicted to
 ironical jokes, which can be a dangerous habit with email.  I dislike
 emoticons, probably because I am more of a snob than I like to admit,
 but also because they seem to me to discourage any attempt either to
 write or to read the subtle - or the ironical! - from email.  An
 advantage of the longevity of a forum like this is that we get to know
 each other's style, so I hope that my un-emoticoned attempts at humour
 are read as such.  I'll see if I can squeeze one out.

 ,; :) ;,

We're OK. I caught your irony. My response was really entirely to Oleg's
question. However, I really was concerned about offending someone -- things
like names and logos carry a certain emotional weight.

In other words, I might worry about offending some on this list, but it
really wouldn't bother me to offend you at all, Peter. VVBG :-)

Victor Mote


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




Re: [PATCH] doc validation fix

2003-01-13 Thread Peter B. West
Victor Mote wrote:


We're OK. I caught your irony. My response was really entirely to Oleg's
question. However, I really was concerned about offending someone -- things
like names and logos carry a certain emotional weight.

In other words, I might worry about offending some on this list, but it
really wouldn't bother me to offend you at all, Peter. VVBG :-)


Touche'.

Peter
--
Peter B. West  [EMAIL PROTECTED]  http://www.powerup.com.au/~pbwest/
Lord, to whom shall we go?


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




Re: [PATCH] doc validation fix

2003-01-12 Thread Bernd Brandstetter
On Saturday 11 January 2003 20:13, Victor Mote wrote:
 Jeremias Maerki wrote:
  - Do we like our current logo? :-)

 I hope I am not out of line to ask an even more fundamental question --
 do we like our current name? I never have a problem writing it, but when
 speaking it, I cannot make my mouth say fop, but invariably say
 eff-oh-pee instead. Our root FO is a FOrtunate or perhaps FOrtuitous
 one, as there are many English words that start with these letters, and
 probably many more that contain them. FOr(r)est might have been good
 (since we seem to work with trees a lot), but is taken. FOrward, FOcus,
 or even FOreword might each work, or efFOrtless (). How about
 FOliage (with a leaf logo)? Or perhaps a Latin word to reflect our
 international crew -- FOcus (again), or FOrtis, or FOrum. I also like
 Oleg's idea of throwing it out to the user community.

After having tried to understand how fop works by just reading the code for 
a couple of hours now, FOrtress inevitably comes to my mind ;-)
(in the sense of: Not easy to get in, at least for a newbie)

Bye,
Bernd



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




Re: [PATCH] doc validation fix

2003-01-11 Thread Jeremias Maerki
Hi Jeff

I've applied your patches locally. Thanks. Everything's ok with the
first one, but with the second one I'm having problems (not your fault!):
- I had to add adjust the inline DTD of skinconf.xml to include the role
  attribute:
  !ELEMENT credit (name, url, image, width?, height?)
  !ATTLIST credit role CDATA #IMPLIED
- The credit element produces a rather ugly FOP logo. But that's
  probably more a FOP-internal thing. We probably need a customized
  little image for this. It should probably be something like:
PDFs generated with
logo   F O P

Questions:
- Does anyone have the original logo (AI, CorelDraw, SVG etc.)??? I
  haven't found it anywhere.
- Do we like our current logo? :-)

I've commented out Jeff's credit element for the moment and will commit
the changes in a minute.

On 10.01.2003 15:45:11 Jeff Turner wrote:
 Running 'forrest validate' on CVS head, I get:
 
 validate-xdocs:
 
/home/jeff/apache/xml/xml-fop/src/documentation/content/xdocs/design/alt.design/properties/enumerated-values.xml:211:63:
 Element type code. must be declared.
 
/home/jeff/apache/xml/xml-fop/src/documentation/content/xdocs/design/alt.design/properties/enumerated-values.xml:212:44:
 The element type code. must be terminated by the matching end-tag
 /code..
 
 Attached patch fixes this, and cleans up enumerated-values.xml a bit.
 
 Also, I've just modified Forrest so that the
 xml-fop/src/documentation/forrest.diff patch is no longer necessary.  To
 achieve the same effect, the second attached patch adds this to
 src/documentation/skinconf.xml:
 
 +credit role=pdf
 +  nameCreated by: FOP 1.0dev/name
 +  urlhttp://xml.apache.org/fop/dev/url
 +  imageimages/logo.jpg/image
 +  width138/width
 +  height31/height
 +/credit
 
 The image, width and height fields are unused, but I put them there so
 users with pre-patched Forrests (which don't know about @role) don't get
 a broken link on the HTML front-page.


Jeremias Maerki


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




Re: [PATCH] doc validation fix

2003-01-11 Thread Oleg Tkachenko
Jeremias Maerki wrote:


- Do we like our current logo? :-)

That's a big question actually :) afair Keiron said the current logo 
should be at least brighten to fit forrest-ed site design better or 
suggested to make the logo contest. Should admit I spent a couple of 
hours trying to implement my ideas about the logo (leading motifs were 
medieval typographic dropcaps and a parrot as (imho) the most foppish 
animal) but I'm too bad artist and the results were too ugly :)
My suggestion is to announce the new FOP logo contest in fop-user list 
or broader, like recent Amaya welcome page contest[1] (the winner gets 
bragging rights). Then we can vote among developers or users, how the idea?

[1] http://www.w3.org/Amaya/contest.html
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel


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



Re: [PATCH] doc validation fix

2003-01-11 Thread J.Pietschmann
Oleg Tkachenko wrote:

Jeremias Maerki wrote:

- Do we like our current logo? :-)

Uh!


Should admit I spent a couple of 
hours trying to implement my ideas about the logo (leading motifs were 
medieval typographic dropcaps and a parrot as (imho) the most foppish 
animal) but I'm too bad artist and the results were too ugly :)

What about a TeX-parody?
  +---  +--\
  | |  |
  +-- /--\  +--/
  |  || |
  |  || |
 ||
  \--/

Colored as the current logo, or more in shades like the
Apache feather? (feather - part of a parrot - hmm)

J.Pietschmann


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




the logo (Re: [PATCH] doc validation fix)

2003-01-11 Thread Oleg Tkachenko
J.Pietschmann wrote:


What about a TeX-parody?
  +---  +--\
  | |  |
  +-- /--\  +--/
  |  || |
  |  || |
 ||
  \--/


Not bad, but what does it mean? (And does logo should mean anything?) :)


Colored as the current logo, or more in shades like the
Apache feather? (feather - part of a parrot - hmm)


I've been imagining F and P as fancy dropcaps and/or a little o with a 
parrot sitting on it, colored or just outlined (something like this one 
[1]). Anyway each of us has a great imagination, but we need real logos 
to choose and why not to make a contest? It's kind of PR after all.

[1] http://www.nyc-poly.org/Poly%20parrot.gif
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel


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



Re: [PATCH] doc validation fix

2003-01-11 Thread Peter B. West
Victor Mote wrote:

Jeremias Maerki wrote:



- Do we like our current logo? :-)



I hope I am not out of line to ask an even more fundamental question -- do
we like our current name? I never have a problem writing it, but when
speaking it, I cannot make my mouth say fop, but invariably say
eff-oh-pee instead.


Heresy!  Victor, the stigma that once attached to consulting a speech 
therapist has almost vanished now.  I'm sure something can be done, and 
our best wishes will go with you.

Peter
--
Peter B. West  [EMAIL PROTECTED]  http://www.powerup.com.au/~pbwest/
Lord, to whom shall we go?


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



Re: [PATCH] doc validation fix

2003-01-11 Thread Jeff Turner
On Sat, Jan 11, 2003 at 05:43:37PM +0100, Jeremias Maerki wrote:
 Hi Jeff
 
 I've applied your patches locally. Thanks. Everything's ok with the
 first one, but with the second one I'm having problems (not your fault!):
 - I had to add adjust the inline DTD of skinconf.xml to include the role
   attribute:
   !ELEMENT credit (name, url, image, width?, height?)
   !ATTLIST credit role CDATA #IMPLIED

Oops yes, sorry.  Attached is a fix with DTD mods.

 - The credit element produces a rather ugly FOP logo.

If you upgrade your Forrest, the logo won't appear[1].  The @role=pdf
in skinconf.xml means the credit only applies to PDFs.  Earlier versions
of Forrest didn't know about this, so rather than display a broken image,
I threw in the current FOP logo.

--Jeff


[1] See http://forrestbot.cocoondev.org/sites/xml-fop/ (after applying
the patch)

 But that's probably more a FOP-internal thing. We probably need a
 customized little image for this. It should probably be something like:
 PDFs generated with
 logo   F O P
 
 Questions:
 - Does anyone have the original logo (AI, CorelDraw, SVG etc.)??? I
   haven't found it anywhere.
 - Do we like our current logo? :-)
 
 I've commented out Jeff's credit element for the moment and will commit
 the changes in a minute.
...

Index: src/documentation/skinconf.xml
===
RCS file: /home/cvspublic/xml-fop/src/documentation/skinconf.xml,v
retrieving revision 1.4
diff -u -r1.4 skinconf.xml
--- src/documentation/skinconf.xml  11 Jan 2003 16:49:26 -  1.4
+++ src/documentation/skinconf.xml  12 Jan 2003 03:47:16 -
@@ -11,10 +11,14 @@
 
   !ENTITY % links.att 'name CDATA #REQUIRED'
   !ENTITY % link.att 'name CDATA #REQUIRED href CDATA #REQUIRED'
-  !ELEMENT skinconfig (disable-search?, searchsite-domain?, searchsite-name?, 
project-name, project-url, project-logo, group-name?, group-url?, group-logo?, 
host-logo?, year?, vendor?, trail?, credits?)*
+  !ELEMENT skinconfig (disable-search?, searchsite-domain?, searchsite-name?,
+  project-name, project-url, project-logo, group-name?, group-url?, group-logo?,
+  host-url?, host-logo?, year?, vendor?, trail?, credits?)*
   !ELEMENT credits (credit*)
-  !ELEMENT credit (name, url, image, width?, height?)
-  !ATTLIST credit role CDATA #IMPLIED
+  !ELEMENT credit (name, url, image?, width?, height?)
+  !-- id uniquely identifies the tool, and role indicates its function --
+  !ATTLIST credit id   CDATA #IMPLIED
+   role CDATA #IMPLIED
   !ELEMENT disable-search (#PCDATA)
   !ELEMENT searchsite-domain (#PCDATA)
   !ELEMENT searchsite-name (#PCDATA)
@@ -24,6 +28,7 @@
   !ELEMENT group-name (#PCDATA)
   !ELEMENT group-url (#PCDATA)
   !ELEMENT group-logo (#PCDATA)
+  !ELEMENT host-url (#PCDATA)
   !ELEMENT host-logo (#PCDATA)
   !ELEMENT year (#PCDATA)
   !ELEMENT vendor (#PCDATA)
@@ -90,12 +95,12 @@
   width138/width
   height31/height
 /credit--
-!--credit role=pdf
+credit role=pdf
   nameCreated by: FOP 1.0dev/name
   urlhttp://xml.apache.org/fop/dev/url
   imageimages/logo.jpg/image
   width138/width
   height31/height
-/credit--
+/credit
   /credits
 /skinconfig


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