Re: Fw: Arabic characters and FOP
- Message d'origine - De : Oleg Tkachenko [EMAIL PROTECTED] So, you right about jdk1.3 - it remains to be seen, another alternatives could be our own TR9 implementation (afaik renderx guys went this way last summer, probably because they have to support jdk1.1 and ms jvm) or some third-party implementation, e.g. ICU4J. They also claim to have only limited (or basic) bidi support, if I recall properly. Did I understand properly Peter that FOP 1.0 should support Jdk 1.3 ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Fw: Arabic characters and FOP
- Message d'origine - De : Peter B. West [EMAIL PROTECTED] Envoyé : 10 oct. 2002 20:40 Patrick, I'm just trying to determine the limits. At the moment 1.3 is needed to compile, because of TrueType font support, although users may continue to run the results in their existing 1.2 environments. There has been vigorous discussion for as long as I have subscribed to this list about migration to later JDK versions. This is perfectly justifiable for me, I just wanted this clarified. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Progress report on FOP 1.0 ?
When last updated, on the 10th of June 2002, it was stated that the development effort is roughly 35% towards a developers release. May I ask, four months later, if the baby is growing well ? P. Andries - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Fw: Arabic characters and FOP
I'm willing to help (slowly) implementing the bidi support (contextualisation and bidi algorithms). Is someone else busy doing it ? Is the time ripe to do so ? - Message d'origine - De : [EMAIL PROTECTED] (See attached file: example.fo) (See attached file: fo.gif) hi pat, i am not using any bidi enabled editor, i just typed the fo using text editor [PA] I see, you are typing character references entities. and view it in IE [PA] Well, IE is bidi-enabled ! [PA] I suspect to print it with FO, bidi needs to be implemented in FO. (I'm still a volunteer to do it ;-)) Patrick Andries o - 0 - 0 Tout Unicode en français Nouveaux textes ! http://hapax.iquebec.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FO WYSIWYG-Editor Project launched @ Sourceforge
- Message d'origine - De : Oleg Tkachenko [EMAIL PROTECTED] À : [EMAIL PROTECTED] Envoyé : 9 oct. 2002 12:53 Objet : Re: FO WYSIWYG-Editor Project launched @ Sourceforge Mark Malone wrote: where do I sign-up!? People, don't take it wrong, but you know, it's *fop*-dev list actually :) Well, where should they go ? Thanks. P. Andries - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Fw: Arabic characters and FOP
Good, no need to help thus. - Message d'origine - De : Oleg Tkachenko [EMAIL PROTECTED] À : [EMAIL PROTECTED] Envoyé : 9 oct. 2002 13:51 Objet : Re: Fw: Arabic characters and FOP patrick andries wrote: I'm willing to help (slowly) implementing the bidi support (contextualisation and bidi algorithms). Is someone else busy doing it ? Is the time ripe to do so ? Implementation of bidi algorithm itself is not a problem as java has already bidi support since jdk1.3 (it's hidden in 1.3 and revealed in 1.4 in form of java.text.Bidi class). So I believe there are no obstacles for redesigned fop to implement bidi support. PS.Actually it's even feasible to produce hebrew pdf using fop right now (well, under certain circumstances). -- Oleg Tkachenko eXperanto team Multiconn International, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Fw: Arabic characters and FOP
- Message d'origine - De : Oleg Tkachenko [EMAIL PROTECTED] patrick andries wrote: Good, no need to help thus. I didn't say that! Volunteers are desperately needed, they are blood of fop project, so if you are willing - you are welcome. Look at today's New Developer Suggestion thread, for example. Okay, okay. I will have a look at it. My own strengths are Unicode, i18n (I still believe you must understand what you are doing and test the different scripts even if Java does most of the job) and fonts (OpenType for instance(*)). I would like to help (not alone...) give the best support in this area, but I'm willing to help (slowly) in other areas in the mean time if the new code is not yet ready to add these features. I will have a look at the todo list and the state of the code and come back (privately) when I have some time. Patrick Andries (member of the Canadian character set committee translator for the ISO JT/SC2/GT2) http://hapax.iquebec.com (*) Does anaybody know how glyphs variants and ligatures (see the substitution feature in Opentype) should be selected from fo ? I believe there is currently no such mechanism. Should we wait until another version of XSL-FO? Extensions ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Fw: Arabic characters and FOP
- Message d'origine - De : J.Pietschmann [EMAIL PROTECTED] À : [EMAIL PROTECTED] Envoyé : 9 oct. 2002 15:30 Objet : Re: Fw: Arabic characters and FOP patrick andries wrote: (*) Does anaybody know how glyphs variants and ligatures (see the substitution feature in Opentype) should be selected from fo ? I believe there is currently no such mechanism. Should we wait until another version of XSL-FO? Extensions ? IIRC the spec mentions it's at the whim of the processor to provide ligatures. There are also various code points assigned to ligatures and presentation forms, for example U+FB01, which could be used in the FO source (at the risk of confusing hyphenation, spell checkers and others). Not a good idea, these code points are deprecated. Ligatures are glyphs not characters, Unicode is about characters (yes, I know there are historical and compatibility exceptions) If such characters are mapped to glyphs by a font, FOP can handle them. The idea with OpenType (the merging of PS1 and TTF fonts) is to do allow to render these ligatures at rendering time (as is necessary with many non-latin based scripts), i.e. within the glyph space. Also, some ligatures are purely discretionary (like the ligated fi you mentioned in U+FB01). This behaviour should be driven by some styling information, I would assume (I want a nice ffl ligature here if present in the font, and here a ct ligature if present). I do not know of any available means to specify this. The same is true for glyph variants (I would like this particular ampersand variant). What are the CSS people doing about this ? Should we follow them ? Also, the discussion whether presentation forms have to be expressed by the characters itself or out of band, for example as fonts, has never ended. Unicode is quite plain about this, I believe it even states somewhere that the Arabic presentations forms were a bad idea . This is at least what the technical director of the Unicode consortium said in an interview I conducted (in French though : http://iquebec.ifrance.com/hapax/pdf/whistler.pdf « Ceci s'est déjà produit : ainsi aucune mise en ouvre Unicode de l'arabe ne se préoccupe du grand nombre de ligatures arabes codées dans Unicode, ligatures dont l'inclusion a constitué une erreur. Les implantations arabes correctes utilisent les caractères arabes de base et étendus et délèguent la formation des ligatures aux polices, comme il se doit.») P. Andries - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Fw: Fw: Arabic characters and FOP
- Message d'origine - De : Victor Mote [EMAIL PROTECTED] À : [EMAIL PROTECTED] Envoyé : 9 oct. 2002 15:39 Objet : RE: Fw: Arabic characters and FOP Patrick Andries wrote: (*) Does anaybody know how glyphs variants and ligatures (see the substitution feature in Opentype) should be selected from fo ? I believe there is currently no such mechanism. Should we wait until another version of XSL-FO? Extensions ? If I understand the OpenType standard properly, it is supposed to do most of this automatically (it seems to in some applications, but I am not sure whether it is the font or the application doing the work). No I do not believe the font or the OS does it automatically, your application does it. Some applications are enabled (make use of the appropriate tables in the font) others not. MS Office tools for instance don't take into account the ligature and substitutions specified for latin scripts...but do it for others script where this is often essential. InDesign does, on the other hand handle the latin ligatures. In the same way, Java supplies you some API to the OpenType tables but does not, I think, interpret them. If you read French see the last part of this article (pp 34-38, 9. Rendu), it is shorter than most of what I've seen written. Sorry for pointing to myself. P. Andries - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Fw: Arabic characters and FOP
- Message d'origine - De : J.Pietschmann [EMAIL PROTECTED] À : [EMAIL PROTECTED] Envoyé : 9 oct. 2002 17:27 Objet : Re: Fw: Arabic characters and FOP patrick andries wrote: There are also various code points assigned to ligatures and presentation forms, for example U+FB01, which could be used in the FO source (at the risk of confusing hyphenation, spell checkers and others). Not a good idea, these code points are deprecated. Ligatures are glyphs not characters, Unicode is about characters (yes, I know there are historical and compatibility exceptions) I should have added drawing the wrath of the Unicode folks to the risks :) Also, some ligatures are purely discretionary (like the ligated fi you mentioned in U+FB01). This behaviour should be driven by some styling information, I would assume (I want a nice ffl ligature here if present in the font, and here a ct ligature if present). I do not know of any available means to specify this. The same is true for glyph variants (I would like this particular ampersand variant). Variants should probably represented by different fonts. I *hope* fonts which have glyph variants for certain characters are rare enough... They will be more and more of them with OpenType. I think ligatures could explicitely prevented by inserting some zero width characters (non-breaking spaces or joiners?). Yes, but this does not allow to select many different behaviours. What are the CSS people doing about this ? It seems there are more pressing problems to solve. I'm not familiar with recent CSS3 developments though. Well, it depends on your constituency : OpenType is very valuable to non-latin scripts and to fine latin typography. Also, the discussion whether presentation forms have to be expressed by the characters itself or out of band, for example as fonts, has never ended. Unicode is quite plain about this, I believe it even states somewhere that the Arabic presentations forms were a bad idea . Yes, Unicode is explicit about this. But there is still a sizeable fraction left which thinks otherwise... Well, as long as they use Unicode ;-) This is also the philosophy adopted by OpenType. But we can leave that to later and follow what other standards will be coming up with for finer controls. P. Andries - o - O - o - Unicode en français : http://hapax.iquebec.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Status on http://xml.apache.org/fop/index.html
- Original Message - From: Keiron Liddle [EMAIL PROTECTED] To: FOP [EMAIL PROTECTED] 3) What does the following paragraph mean ? « Development for 1.0DR1 is addressing the design issues for layout and performance. This is focusing on making it possible to be conformant to the spec and be able to handle large documents. This is roughly 30% towards a developers release that should have: similar functionality to previous FOP releases, a rough API and a suitable design for developers to work on more functionality. » It means we don't know but we are working on it. What is « roughly 30% towards » ? The work already done or the 1.0DR 1 ? Could this sentence please be rewritten ? It is a rough estimate that gives a bit of information without really saying much. Do you want less information so you aren't tempted to make predictions or do you want more information that will end up being wrong? [PA] Don't take my remarks wrong : I don't mind not having much information, I just don't want to be misled. I do simply not understand the sentence. What is « this » in « this is roughly » ? Do you mean that the redesign will end up when it ends (and we have no idea when) with 30% of the current functionality (« this is roughly 30%» ...« similar functionality to the previous FOP releases » ? If this is not what you intend some people to understand, the sentence should be rewritten. 4) What has changed in the last month ? (I.e. could we get at least a monthly update if we must live with «The timing of these events depends on progress made so it is not possible to predict any dates » ?) Are you volunteering to help out with this? [PA] In fact, about two to three months ago I voluntereed (I was between jobs) and no one answered. Now I'm rather taken by my new job, but my employer will be happy to help implement features if there is a least a chance of a release sometimes (I have stated several times that we want line numbering(*), for instance, for our government customers). We could also help implement other features (in the recommendation this time) but again if our investment were to come to fruition relatively quickly, we are too small a company to do otherwise. Patrick Andries (*) Which I **prototyped** on my machine in FOP 0.23 to the customer's satisfaction. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Status on http://xml.apache.org/fop/index.html
I think it was about a month ago, a status section was added to the FOP main page. A good idea. Four questions : 1) Could it be possible to add a date to this status : "[last updated xx-March-2002]" ? 2) Could it be possible to move this section higher ? It is difficult to spot. 3) What does the following paragraph mean ? « Development for 1.0DR1 is addressing the design issues for layout and performance. This is focusing on making it possible to be conformant to the spec and be able to handle large documents. This is roughly 30% towards a developers release that should have: similar functionality to previous FOP releases, a rough API and a suitable design for developers to work on more functionality. » What is « roughly 30% towards » ? The work already done or the 1.0DR 1 ? Could this sentence please be rewritten ? 4) What has changed in the last month ? (I.e. could we get at least a monthly update if we must live with «The timing of these events depends on progress made so it is not possible to predict any dates » ?)
Re: Line breaks and other typographical stuff (was: Re: Latest FOP schema)
J.Pietschmann wrote: Patrick Andries wrote: This begs the question: how should arbitrary non-breaking spaces be expressed in XSLFO, and how often does this issue arise? Well, in fine French typography, this occurs often. Semicolon, question marks and exclanation marks, for instance, should be preceded by a fine non-breaking space while colon and closing guillemet ( ») should be preceded by a larger non-breaking space. I believe Unicode does not distinguish between these two cases, its customary answer would be that this is a higher protocol's duty : Unicode only marks a semantic function (non-breaking space) not its appearance. In other words, it's FO's problem ? This is my understanding. There is already a certain proliferation of spaces, and the Unicoders quite explicitely stated they feel mainly responsible for stuff resulting in glyphs Well, they feel responsible for characters. Glyphs is not Unicode's realm, they will off course turn out as such (most of them in any case: some are invisible, such as language tags). and want to support control characters, separators and spaces only to the extent necessary for compatibility and to deal with the cases which arise most often. I think they would like if there were a fo:word :-) Not sure, we actually discussed this topic on the Unicode internal list (sentence and word boundaries) . Word is a very language-specific thing: even French and English don't use the same typographical conventions to delimit them. Never mind languages like Thai where spaces do not separate words. Also I do not know off hand of any Unicode rendering algorithm that needs to know what a word is (sorting does), determing what is a paragraph (fo:block), however, is essential for bidirectional rendering. Well, arbitrary spaces can be achived in XSLFO by using space-start on a fo:inline. Attaching a keep-with-previous=always should make it non-breaking in my understanding, for example fo:blockMr. fo:inline space-start=0.4en keep-with-previous=alwaysBean/fo:inlinefo:block Seems to be an awful lot to write for a sort of fine tuning effect (most readers wouldn't appreciate it, or even take notice). This insertion should be done at another level (in French the non-breaking width variation is pretty deterministic, an XSLT stylesheet could do it I suppose). Well, current FOP ignores both properties on fo:inline anyway. (Already mentioned on an different list : I would really love to have an idea how things are progressing. It would be good for this to be posted regularly in a succinct fashion on the Web site. http://xml.apache.org/fop/design/status.html is very laconic. Difficult to plan any action on this base.) Ah, again: fo:blockMozifo:inline space-start=0.4enlla/fo:inlinefo:block hopefully never breaks in the middle unless permitted by hyphenation, it's just a word with a gap. Is this correct? Intuitively, yes. P. Andries Tout Unicode en français --- http://hapax.iquebec.com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Drawing a line between two region-body columns
I have divided the region-body in two. I would now like to draw a single line separating the two columns, can this be done ? Is there any way to write something in the column-gap ? Alternatively, since I am having a block flowing from one column to another could I have the right column block's left border to appear but not the left column block's left border to appear. I.e. right column of block ... | ... left column of block and not the usual | right column of block ... | ... left column of block which is easy to get with block border-left=1pt I see no way for this to work, but I would really like it to. Patrick Andries - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: orphan - widow
OK. thanks, although this is not good news. J.Pietschmann wrote: Patrick Andries wrote: What is the status of the orphan and widow control ? It is not implemented in 0.20.3, there is no precise timeline (somewhen this year), it is not all that easy to implement in the current design, and there is no schedule for the redesigned FOP. There may be another maintenance release in the short term, but certainly without orpahns/widows and keeps. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
orphan - widow
What is the status of the orphan and widow control ? If this is not yet implemented, have we got any timeline ? How complex could it be to implement for a seasoned developer (in man days) ? When is the next release of FOP scheduled ? Thanks Patrick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: When a page is not a page
What is the status of the orphan and widow control? If this is not yet implemented, have we got any timeline? How complex could it be to implement for a seasoned developer (in man days)? When is the next release of FOP scheduled? Thanks Patrick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: AWTRenderer L10N issues
Alex V. Alishevskikh wrote: 001101c1d49e$aac011c0$a3cbdcd4@term1"> Hi, Patrick,You wrote: No, it was coded in 8859-5 (Cyrillic) or Windows 1251, AFAIK, ISO8859-5 is not the same that Windows 1251. Well, Microsoft adds to 8859-5 a few Cyrillic characters in the 80-9F range (euro sign for one, and diacritic forms such as k apostrophe on top). My point was rather that it was not 8859-1 as mentioned but 8859-5 or CP 1251 which are hard to distinguish. 001101c1d49e$aac011c0$a3cbdcd4@term1"> I see the extended latinletters (with umlauts etc) instead of cyrillic characters.I've compiled FOP on machine (WinXP, Sun JDK 1.3) with russian locale. ? The only encoding that Properties and PropertyResourceBundleunderstand is ISO 8859-1 with Unicode escapes. This is not UTF-8. But why my Properties encoded as UTF-8 works and I see the readable russiantext? As pointed out in a different message by Satoshi, and I missed this, AWTStarter uses a getResourceBundle which in turns uses a SecourceResourceBundle that reads UTF-8 (I still see 8859-1 in my source). I suppose I should update my tree. 001101c1d49e$aac011c0$a3cbdcd4@term1"> I only regret that using this new getResourceBundle, it looks like the standard getBundle search algorithm is not implemented. I personnaly believe it is usually bad design to hardcode a default language, One should rather use a Locale for setting the language (picked from the argv for instance) or getting the platform's default one and rely on the getBundle algorithm. The default resource language could then become the platform's language (locale) unless no resource exist for it, in which case the resources found in the base resource bundle could be used (this could be a different file for each system according to installation option). P. Andries
Re: FOP vs RenderX
To be frank, although I have the same experience as Matt as far as speed (or lack thereof) of XEP is concerned, XEP is pleasant to work with (more syntax checking) and does support many more features (among which the absolutely essential keep-with-next for any professional looking document). I hear often that this may not be available soon in FOP, what does this mean a month, two months ? Patrick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: AWTRenderer L10N issues
Christian Geisert wrote: Alex V. Alishevskikh wrote: Hi, there, I've found what messages.ru file is missing in the AWT Renderer resources. As a result, AWTStarter crashes with NullPointerException on launching it on russian system. The another issue is wrong encoding in resources.ru file (it looks like 8859-1 ), what makes the cyrillic labels and menus are unreadable. No, it was coded in 8859-5 (Cyrillic) or Windows 1251, I can see File=fail æÁÊÌ. You most probably compiled on a non-Cyrillic machine and did not set -encoding javac compilation option. I believe your change is, however, a good one. I notice you also change some translations.(About, Show, etc.). . I've created the messages.ru and resources.ru files with russian text in UTF-8 (see attached files). It seems what it works well (FOP 0.20.3, Sun JDK 1.3.0). Did you use Unicode escape sequences (with native2ascii) ? If not, I'm not sure it works all the time (might because of BOM). ? The only encoding that Properties and PropertyResourceBundle understand is ISO 8859-1 with Unicode escapes. This is not UTF-8. UTF-8 encodes Unicode characters into sequences of 1 to 4 bytes using a mapping specified in The Unicode Standard, version 2.0 or 3.0. Other encodings need to be converted with the native2ascii tool. This applies to all releases from 1.1 to 1.3. ? http://www.sun.com/developers/gadc/faq/java/files/properties.html#2.0 I wish to propose the solution for case when AWTStarter cannot finds the resource bundle appropriated for user language: then let it to use the english (*.en) resources as default. [..] It should prevent the crashes on machines with language settings are unsupported in AWT renderer resources. Any opinions? I wonder if this is a good idea. Why not use whatever is in the default resourceBundle ? Hardcoding seems useless at best when there is a more flexible built-in mechanism (getBundle search). However, it looks like this mechanism is short-circuited in AWTStarter by using a ResourceBundle name that incorporates the language ( resource = getResourceBundle(TRANSLATION_PATH + resources. + language)) and does not set any Locale. I do not believe this to be wise. This is an i18n issue. P. Andries --- Tout Unicode 3.1 en franc,ais http://hapax.iquebec.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: AWTRenderer L10N issues
Patrick Andries wrote: Christian Geisert wrote: Alex V. Alishevskikh wrote: Hi, there, I've found what messages.ru file is missing in the AWT Renderer resources. As a result, AWTStarter crashes with NullPointerException on launching it on russian system. The another issue is wrong encoding in resources.ru file (it looks like 8859-1 ), what makes the cyrillic labels and menus are unreadable. No, it was coded in 8859-5 (Cyrillic) or Windows 1251, I can see File=fail æÁÊÌ. You most probably compiled on a non-Cyrillic machine and did not set -encoding javac compilation option. I believe your change is, however, a good one. Forget the -encoding javac compilation option, this is for ListResourceBundle. It's getting late. P. Andries - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [Fwd: Numbering lines]
I would like to be able to reset (optionally) the line number at column or page break. I did not find much info on the Layouter... Could someone give me a little pointer (for instance, where page and column break are detected). Thanks Patrick Andries - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [Fwd: Numbering lines]
OK, thanks I don't need help anymore. I found it and coded it. Patrick Andries wrote: I would like to be able to reset (optionally) the line number at column or page break. I did not find much info on the Layouter... Could someone give me a little pointer (for instance, where page and column break are detected). Thanks Patrick Andries - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [Fwd: Numbering lines]
OK, I have hacked (for my own understanding) something that seems to work. Now I would like to be able to reset (optionally) the line number at column or page break. I did not find much info on the Layouter... Could someone give me a little pointer (for instance, where page and column break are detected). Patrick Andries Patrick Andries wrote: OK, how can I help implementing it ? Arved Sandstrom wrote: Hi, Patrick Yes, this would be useful. All you can do now is if you know the lines ahead of time; then you can use XSLT xsl:number if your source XML permits. But for what you are talking about, no, XSL formatting does not have a way of doing it, although one can certainly imagine an extension that extends layout for each LineArea. Regards, AHS -Original Message- From: Patrick Andries [mailto:[EMAIL PROTECTED]] Sent: March 20, 2002 7:47 PM To: [EMAIL PROTECTED] Subject: [Fwd: Numbering lines] I sent the message to fop-user, no one answered. If this is not possible (probable), would the extension be simple (useful in legislative text). Message d'origine Objet: Numbering lines Is it possible to dynamically number lines in FO ? P. Andries - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[Fwd: Numbering lines]
I sent the message to fop-user, no one answered. If this is not possible (probable), would the extension be simple (useful in legislative text). Message d'origine Objet: Numbering lines Is it possible to dynamically number lines in FO ? P. Andries - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [Fwd: Numbering lines]
OK, how can I help implementing it ? Arved Sandstrom wrote: Hi, Patrick Yes, this would be useful. All you can do now is if you know the lines ahead of time; then you can use XSLT xsl:number if your source XML permits. But for what you are talking about, no, XSL formatting does not have a way of doing it, although one can certainly imagine an extension that extends layout for each LineArea. Regards, AHS -Original Message- From: Patrick Andries [mailto:[EMAIL PROTECTED]] Sent: March 20, 2002 7:47 PM To: [EMAIL PROTECTED] Subject: [Fwd: Numbering lines] I sent the message to fop-user, no one answered. If this is not possible (probable), would the extension be simple (useful in legislative text). Message d'origine Objet: Numbering lines Is it possible to dynamically number lines in FO ? P. Andries - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Why do you use FOP instead of ...
Ralph LaChance wrote: At 04:06 PM 2/1/02 -0200, you wrote: I will nail down the weaknesses of the XML-PDF approach: 1. XSL:FO is a very complicated and messy language 2. XSLT is also kinda complicated to use, at least if you have to do complicated formatting... Sometimes it seems folks assume that FO is synomous with pdf, but for some of us, the point of using FO is not to create pdf output but to format and send xml data directly to a printer. ;-) Well, what does it take to develop an XSL-FO interpreter on a printer ? No need to transform to PDF or PS then. I thought of doing it for some time, but got discouraged when an old Xerox guy told me that Adobe actually supplies (for free ?) their PS interpreter and that developing an interpeter and fine-tuning it takes a LOT of time. Patrick Andries - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Choice of a XSL-Fo processor
Matt Savino wrote: Thanks Betty for filling in some of the blanks. (I was mixing up XEP and PassiveTex in a post I made earlier. I forgot XEP is RenderX.) I just had a couple of questions: Antenna House is Windows-only right? Do you think XEP's command line-driven approach would work within a J2EE internet application dynamically generating printable reports? I believe XEP has an embeddable version but only for a fee. Apparently the reason my developer couldn't find an API to XEP is that there is none. There is none freely available, but this is what I read this on their support list some time ago : «The commercial version of XEP comes with a fourth document that describes various programming interfaces available in XEP. The evaluation version does not include the API documentation: it is meant to let people assess formatting quality, memory footprint and performance. In our view, detailed knowledge of API is not necessary for making a purchase decision. Best regards, Nikolai Grigoriev RenderX» - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Euro sign
Tore Engvig wrote: [EMAIL PROTECTED]"> Why do I see a bullet instead of a euro sign (EUR), when I simply"compile" the fonts.fo file found in the Fop-0.20-2 distribution(./docs/examples/fo)?I am on Windows NT 2000 Professional, all my standard fonts have thus aeuro sign (me thinks). If you use embedded fonts, this should not be a problem (unicode value islooked up in cmap), If the font is embedded it should indeed work, but technically I'm not sure the cmap (which is a TTF or an OT table) is looked up for PS fonts. [EMAIL PROTECTED]"> If I remember correctly, a patch was submitted that added the euro sign tothe standard fonts. It exists in the cvs version (in the fop-0.20.2-maintainbranch). Yes I believe I saw this, it dealt with the definition of the entity reference euro; The problem was related to an old Acrobat reader (3.0) being set as default. I changed my default reader to a newer version (4.0) and it worked. Patrick
Re: Euro sign
Patrick Andries wrote: [EMAIL PROTECTED]"> Tore Engvig wrote: [EMAIL PROTECTED]"> Why do I see a bullet instead of a euro sign (EUR), when I simply"compile" the fonts.fo file found in the Fop-0.20-2 distribution(./docs/examples/fo)?I am on Windows NT 2000 Professional, all my standard fonts have thus aeuro sign (me thinks). If you use embedded fonts, this should not be a problem (unicode value islooked up in cmap), If the font is embedded it should indeed work, but technically I'm not sure the cmap (which is a TTF or an OT table) is looked up for PS fonts. I "mispoke" here, there is also one (or more) Cmap in CID-keyed fonts. P. Andries
table-omit-footer-at-break
Does it actually work in FOP ? I had hoped to use it to circumvent the keep-next and orphans bugs This feature in my file behaves properly with Renderx but not FOP 0.20.2... P. Andries P.-S. : Why do I always have to modify master-name to master-reference when transfering a file working with Fop to Renderx.? Is FOP 0.20.2 not implementing the same XSL 1.0 spec as Renderx ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [Fwd: Re: Euro sign]
Martin Stricker wrote: [EMAIL PROTECTED]"> Patrick Andries wrote: I did a simple test: create a text file with just one Euro sign inWin2k, then booted into Red Hat Linux 7.2 (dual boot box) and checkedwhat the text file actually contained. It was one single character #128. Yes, this is because you saved your file in win1252 (default on Western European Windows). [EMAIL PROTECTED]"> How are the characters accessed by FOP, through the cmap? Sorrry, I don't know. I suspect it relies on PDF for all those details, I wonder if this is the best course (for complex languages for instance). When I have time, I'll check. [EMAIL PROTECTED]"> I don't use character 164, I (or better said fonts.fo) use the numericcharacter reference #x20AC;. Hmmm... maybe if you use a real Unicode font with the Euro character inthe right place... Sadly I don't know much about fonts, but I'm tryingto learn... pointers to more information in English or German areappreciated! I have just solved the problem as I tried using Acrobat 4.0 instead of my old Acrobat 3.0 (unfortunately, it was my default). Acrobat version 3.0 does not support the euro (and the font was not embedded). Patrick
[Fwd: Re: Euro sign]
Message d'origine Objet: Re: Euro sign Date: Thu, 17 Jan 2002 00:49:45 +0100 De: Martin Stricker [EMAIL PROTECTED] Patrick Andries wrote: Why do I see a bullet instead of a euro sign (EUR), when I simply "compile" the fonts.fo file found in the Fop-0.20-2 distribution (./docs/examples/fo)? I am on Windows NT 2000 Professional, all my standard fonts have thus a euro sign (me thinks). You are using the wrong OS and fonts. :-( On Win2k the Euro sign is mapped to character code 128 (0x80). This is the number in win1252 (later versions).But aren't the fonts accessed through their Unicode value (in the cmap)?And there, it is 0x20AC...even on Win2k (I just checked Arial in Fontlab).How are thecharacters accessed by FOP, through the cmap?But according to the ANSI / ISO 8559 standard this character is a non-printable control character.Yes, this is true.The standards compliant solution is to use an ISO 8559-15 font (similar with 8559-1 with the single exc eption that the general currency symbol at character code 164 (0x164) is now replaced by the Euro symbol). Ibelieve one should go through the cmap to map the Unicode number to the glyph index. I believe ISO-8859-15 fonts, if they exist, are (or should be) only fonts with Unicode cmap restricted to the ISO-8859-15 subset of characters.BTW the euro, is not the only difference between ISO-LATIN-1 and LATIN-9 (8859-15) : see my page (auf Franzsisch, aber ist das ein Problem?)it also adds some Finish accented forms and one capital that missed in French (Y = , as in L'HA-LES-ROSES a town close to Paris).Sorry, I don't know how to actually solve your problem. Try using an ISO 8559-15 font and use character code 164 instead of 128 and see if thisI don't use character 164, I (or better said fonts.fo) use the numeric character reference #x20AC;.solves your problem. Maybe just switsch ing to character code 164 will...I suppose I could add a new PS font (even Arial) and I try to see whether it works, but I'll do that later when the rest of my form works.Slowly learning.Patrick Andries- - - - - Tour sur Unicode 3.1, texte complet traduit et mis jour (mieux que le site en anglais ;-))Annotations, tous les noms de caractres.http://hapax.iquebec.com
Re: Any real-life business use ?
Thank you very much to all that have answered, the messages as well as support one seems to get from the list are indeed encouraging. I still have one general question and a specific one : 1) Volume and speed I have written a small report: a five-column table, a page footer (simple text), a page header with a largish colour logo. I embedded the FOP generation (XSLT + FOP) in a servlet using the supplied standard code (viz. using XSLTInputHandler as parser). I use Jboss 2.4.4 with Catalina. My development machine is a Pentium 700 Mhz machine with 254 Meg of memory running Windows NT 2000 Professional. And I don't seem to get much more than 1-2 pages generated per second (even when the servlet has already been called). Is this also your experience? I must say that I have attempted no optimisation. Any that you might suggest? How do handle load when several users are requesting reports simultaneously? Only accept patient users? 2) IE Bug Alex Mc Lintock wrote that, due to a bug in IE, he had to save the whole PDF file on disk. I think I have seen this: is this when the PDF file is interpreted as text and displayed as gibberish in the main navigation window? Has this not been resolved in later versions of IE? Has the bug been reported to the MSIE team? Patrick Andries -° - ° - ° - ° Tout sur Unicode 3.1 en français http://hapax.iquebec.com Texte complet de la norme mise à jour, annotations - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: PostScript in pdf
Dariusz Grabowski wrote: Hi Is it possible to insert postscript commands to pdf created from Fop? I use Fop to create document which is printed from 2 trays. Each of page should contains information about tray from which will be printed. With Best Regards This is also of interest to me, since I think it is a crucial point in any sizeable business application. Does someone know if this is being considered for a future version of XSL-FO? How would this be handled in a generic fashion (since direct paper tray number controls are printer-dependent)? Through MediaTypes and Policies as in PostScript? Patrick Andries - - - - Tout sur Unicode 3.1 en franais http://hapax.iquebec.com Texte complet de la norme mise a` jour, annotations - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Any real-life business use ?
Hello everyone, I have busy evaluated the FO technology and I would like to hear from people that are using it for real-life business needs. What kind of documents are they using it with ? What volume ? Embedding it in servlets ? How do they cope with the speed ? How do they justify using FO to their bosses ? Anybody with both 3B2 and FO or Compuset and FO experience ? I would love to hear your story. Patrick Andries - ° - ° - ° - ° Tout sur Unicode 3.1 en français : http://hapax.iquebec.com Traduction complète, mise à jour, texte en ligne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Footer problem : region-body encroaching on region-after
Matt Burke wrote: This is because the region-after sticks up into the region-body by the amount specified in the extent property. See section 6.4.12 of the XSL spec for a couple diagrams and some description. Yes, I realized this later. I foolishly misunderstood a comment in The XSL Companion, where I read (p. 156) : «When some or all the other, optional regions are also needed, they occupy space around the region body (beyond that already created by the page margins)». Only later did I see what was meant (p. 158) : « within the margins of the body, other regions can be defined », I had naively assumed this would have been automatic. Thank you for your help. Patrick Andries -°-°-°-°-°-°-°-°-°-° Tout sur Unicode (3.1) en français http://hapax.iquebec.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Footer problem : region-body encroaching on region-after
This is my first message on the list and I do not know whether what seems to me as a problem has already be reported. If one duplicates a few blocks in docs/examples/corresp.fo so as to generate an additional page, the last lines of the block on the new page overwite the footer instead of being printed on a new page. I'm relatively new to FOP (and FO) and may have thus made a foolish error. Files (.FO, PDF,PS) are available. Patrick Andries - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
