Re: [SPAM] font-family=Arial Unicode MS in rtf doesn't work
József Németh wrote: snip/ Andreas, I don't doubt that you, the FOP developers, are a group of good software professionals and a bunch of nice peaple. But the way you handle FOP as a product development project and relate to the user's of FOP is downright amateurish. And for me irritating, too. I know its easy to get the wrong end of the stick over e-mail, but the above statement is unfair. Yes, the approach may well be amateurish. But that is because the development team are not paid. The definition of a professional is someone who is paid for their work. So when they are not paid IMO you have: a) no right to expect a professional service b) no right to complain about the level of service. This is open source. If you don't like the way something is done. Fix it yourself. Chris snip/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SPAM] font-family=Arial Unicode MS in rtf doesn't work
I don't doubt that you, the FOP developers, are a group of good software professionals and a bunch of nice peaple. But the way you handle FOP as a product development project and relate to the user's of FOP is downright amateurish. And for me irritating, too. It seems most of the misunderstanding about the Apache FOP project can be illustrated from your first paragraph. First, this is the FOP users list, not the FOP developers list. If you want to know how the daily development proceeds, join the correct list. Second, the project is open source, which means that by definition it is neither professional nor amateur. It is a volunteer group. Undoubtedly, some developers are professionals and some are amateur, but that is irrelevant. If someone would like to see more progress in an area, then you've got SVN and may even have knowledge of java...get crackin! Third, we're not nice people; or rather, it's irrelevant whether we are. We are FOP users who have questions about, or are interested in, the product. I don't doubt that you're irritated. But expressing your irritation - which seems based on a misunderstanding of open source software - is not appropriate. If you have questions, or wish to encourage the group to make certain decisions or changes, then please ask. I've only been reading for about a month now, and I find this group to be very reasonable and dedicated. Jeff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SPAM] font-family=Arial Unicode MS in rtf doesn't work
Anderas, Chris, Well Gentlemen, why should I say? Maybe this. What I have said was not unfair not even impolite, maybe a little coarse and certainly true. The fact is that I had been acting on the false assumption that the goal of the FOP project was to develop a product. Now from what you say I know that yours is a hobbyist project that probably would never yield a product. It is not to say that it is not interesting, not complex or not valuable. Just that one should not wait for a product that you start and there you go. What is not fair is that this is not evident from the FOP site! On the contrary ... Also, you both are grossly mistaken in your view on Open Source. It is not a do-it-yourself movement. If you take the trouble you will find ample material in the Internet on the philosophy and driving considerations behind it. I got your take-it-or-leave-it message. Bye-bye FOP, I am leaving. No offence taken, simply does not worth the effort. Bye JN -- View this message in context: http://www.nabble.com/font-family%3D%22Arial-Unicode-MS%22-in-rtf-doesn%27t-work-tf3177039.html#a9085089 Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SPAM] font-family=Arial Unicode MS in rtf doesn't work
Jeff, I've just took leave of FOP for good (see somewhere up in the thread), but what you say preserves a quick answer. There is no mistake, I am on the proper list: regarding FOP I wanted to be a user. Besides you have probably saw up in this thread what led to this exchange. There is, however, a prelude to all this. Because, you know, I took the trouble to submit a number of bug reports. What drove my blood pressure up were the reactions they elicited. (You may see it for yourself if you want to.) As a professional I found this remark (from the lead developer himself) the most vexing Frankly, I'm surprised to see b-p-d and i-p-d applicable to inline at all. After all it's the only FO which generates normal areas, not viewport or reference areas that i-p-d and b-p-d applies to. That's weird IMO! IMO it would sufficed to let inline-container handle this case. Too bad, we haven't implemented that one, yet. (I checked and found that the actual state is worse: i-p-d of fo:inline at least preserves the content, with i-p-d on fo:inline-container the content simply dissapears!) Finally the ignition was this comment from Andreas L. Delmell If you really, really need this feature, then you're welcome to checkout the source w/ Subversion and build-it-yourself. Now, English is not my native tongue, but surely there is a fine sneer in this. I am not considering showing irritation inappropriate only bad tactics. But I do think that the way my bug reprorts were handled bordered on bad manners. Finally what you say about Open Source is more realistic that the definition your collegues tried to thrust on me but still far from the complete picture. Thanks anyway for your trouble Bye JN -- View this message in context: http://www.nabble.com/font-family%3D%22Arial-Unicode-MS%22-in-rtf-doesn%27t-work-tf3177039.html#a9086656 Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SPAM] font-family=Arial Unicode MS in rtf doesn't work
On Feb 21, 2007, at 14:37, Jeff Vannest wrote: Hi Jeff, I promised myself to ignore whatever spawned from the remainders of this thread, but decided to peek anyway, and I'm glad to have stumbled on this one: snip / ... we're not nice people; or rather, it's irrelevant whether we are. That's certainly a /nice/ way to put it! I agree. :) snip / I've only been reading for about a month now, and I find this group to be very reasonable and dedicated. Let's conclude with(*): one simply reaps what one sows here. Ask a straightforward question, and you will get a straightforward answer. Be smart, and you will get smart answers. Start off by irritating us, and... Well, from time to time, one of us will bite and irritate you back. That is: if you're lucky. ;) Mostly, irritating non-questions are simply ignored. What I find so peculiar in this case is that, on the one hand we are complimented on our website for giving the impression of 'FOP as a product' --All hail Web Maestro Clay, here--, which I take to be a good thing in Joe's eyes, unless we misunderstood each other there as well. On the other hand, it raises the question: Is our 'Getting Help' page really that hard to find, then? Here we have a user, who submits Bugzilla reports. OK, so he gets the usual treatment: a simple concise statement that a certain bug was fixed in the trunk in one case. A polite question to please attach a small FO that demonstrates the bug in the other. In yet a third there is even an intent to gather the information necessary to implement the missing feature. Oh well, I could go on for pages... As a tribute to Joe, I think I'm going to have a crack at implementing fo:inline-container very soon ;) Later Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [SPAM] font-family=Arial Unicode MS in rtf doesn't work
-Message d'origine- De : Daniel Noll [mailto:[EMAIL PROTECTED] Envoyé : mardi 20 février 2007 01:23 József Németh wrote: Excuse the buttler butting in but what the spec says is: Font family names containing whitespace should be quoted. If quoting is omitted, any whitespace characters before and after the font name are ignored and any sequence of whitespace characters inside the font name is converted to a single space. To me it means that even if not quoted font-family=Arial Unicode MS still ferers to a single font not to the sequece Arial, Unicode, MS. You're right, but didn't someone say very recently that they had a fix for this bug? Daniel Yes, it was on TRUNK by Andrea D. Pascal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: font-family=Arial Unicode MS in rtf doesn't work
No, they didn't! My error report was cosed with the remark that
in FOP the workaround is quoting. Yeah, but that's not the
answer I would expect (ord accept) for such a
(technically) minor bug.
I've changed my opinion on this issue. The CSS spec on 'font-family' gives
this example in section 5.2.2 of the Level 1 spec, 11-JAN-1999:
Font names containing whitespace should be quoted:
BODY { font-family: new century schoolbook, serif }
BODY STYLE=font-family: 'My own font', fantasy
To me, this cannot be labeled a workaround in FOP, it is compliance with
the spec. Frankly, I've never seen single quotes within an attribute, and I
would have bet money otherwise, but it's clear as can be in the CSS spec.
The level 2 spec contains the same example of single quoting font names that
contain spaces.
As an aside, Altova StyleVision currently ships with FOP .25, and it does
not single quote fonts containing spaces, which causes the integrated FO
support to fail when identifying fonts by font-family. It's unfortunate, but
it looks to me like this is a bug in StyleVision that should be corrected by
Altova. Although, I have to admit that it would be nice if FOP were
forgiving of this, since I plan to roll out StyleVision to several
developers as our primary FO GUI to use with the latest Apache FOP version.
Jeff
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SPAM] font-family=Arial Unicode MS in rtf doesn't work
On Feb 20, 2007, at 12:01, József Németh wrote: No, they didn't! Yes, we did! :) It was fixed in FOP /Trunk/ (= fix will be in the next release) 0.93 won't be patched, that much is true... If you really, really need this feature, then you're welcome to checkout the source w/ Subversion and build-it-yourself. Later, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SPAM] font-family=Arial Unicode MS in rtf doesn't work
Yes, we did! :) It was fixed in FOP /Trunk/ (= fix will be in the next release) Excellent! This means that my Altova StyleVision should work either way with the new rev. Is there a way to know when the next rev will be released? Jeff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SPAM] font-family=Arial Unicode MS in rtf doesn't work
On Feb 20, 2007, at 19:49, Jeff Vannest wrote:
Yes, we did! :)
It was fixed in FOP /Trunk/ (= fix will be in the next release)
Excellent! This means that my Altova StyleVision should work either
way with
the new rev.
Indeed.
Is there a way to know when the next rev will be released?
Unfortunately, we don't have a timeline for this :(
(read: we're all volunteers, so it depends on whether any of us have
the time and motivation)
OTOH, if you have Subversion and Ant at your disposal, then it is a
piece of cake to build, though...
1) checkout the trunk from the repository
2) navigate to FOP's root directory, and type 'ant' ('ant package' to
save some time and only build the fop.jar).
That's all there is to it.
Cheers,
Andreas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: font-family=Arial Unicode MS in rtf doesn't work
On Feb 20, 2007, at 14:20, Jeff Vannest wrote:
Hi Jeff,
I've changed my opinion on this issue. The CSS spec on 'font-
family' gives
this example in section 5.2.2 of the Level 1 spec, 11-JAN-1999:
Font names containing whitespace should be quoted:
BODY { font-family: new century schoolbook, serif }
BODY STYLE=font-family: 'My own font', fantasy
To me, this cannot be labeled a workaround in FOP, it is
compliance with
the spec. Frankly, I've never seen single quotes within an
attribute, and I
would have bet money otherwise, but it's clear as can be in the CSS
spec.
Interesting info! Thanks for looking this up and sharing.
OTOH, now I'm wondering...
If you've never seen single quotes within an attribute, I bet you
haven't looked too closely, or you just missed them --or you've never
written stylesheets...? ;P
In XSLT these could turn out to appear far more often than you think:
xsl:if test=contains(., 'literal')
I've even seen double quotes inside single quoted attributes, because
that is equally valid XML
xsl:if test='contains(., literal)'
Cheers,
Andreas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SPAM] font-family=Arial Unicode MS in rtf doesn't work
Yes, we did! :) It was fixed in FOP /Trunk/ (= fix will be in the next release) 0.93 won't be patched, that much is true... If you really, really need this feature, then you're welcome to checkout the source w/ Subversion and build-it-yourself. Later, Andreas Andreas, I don't doubt that you, the FOP developers, are a group of good software professionals and a bunch of nice peaple. But the way you handle FOP as a product development project and relate to the user's of FOP is downright amateurish. And for me irritating, too. Let me take your answer: I wonder, how should I have known about the fix. I specifically looked a the answers to my error report before I sent my reply and had not found any indication of it there. As a user I am equiped with the necessary environment to keep the softwares I am routinely using current. In this case using toroiseSVN I have checked out the complete FOP trunk just to find that, just as you suggest, if I want to use it I should build it myself. I didn't. (To state it slightly I wasn't in the right mood.) [In fact I had already installed a different workaround before I submitted the bug report.] On the FOP Download page I found this: Fixme (jeremias) Reenable the link to the SVN snapshots once they are available. Now, what the heck it's supposed to mean?!. Can you tell me a valid reason why there are no daily (or at least weekly) snapshot builds of the trunk available at least on the main FOP server? Anyway, why should I be at the bleeding edge with FOP Trunk if I only need a small, safe and fully tested fix in the 0.93 branch that I can easily update if there is a new build available. And finally knowing the history of FOP your mentioning of a new release is not too promising either. Please, do no take all this as an offence I have not meant it to be. Joe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/font-family%3D%22Arial-Unicode-MS%22-in-rtf-doesn%27t-work-tf3177039.html#a9070526 Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SPAM] font-family=Arial Unicode MS in rtf doesn't work
On Feb 20, 2007, at 22:16, József Németh wrote: Hey Joe, Let me start off by saying that I was very tempted to let your posting pass and not give you any more attention, but I just couldn't help myself, so here we go... I don't doubt that you, the FOP developers, are a group of good software professionals and a bunch of nice peaple. But the way you handle FOP as a product development project and relate to the user's of FOP is downright amateurish. And for me irritating, too. Apologies if it irritates you. That is certainly the opposite of what is intended. Yes, the style may be 'downright amateurish', as you call it, because Open Source --as I understand it-- is not governed by the same laws as your everyday professional commercial software development company. There is no such thing as a 'strict deadline' here. No contracts, no customers... Keep in mind that all FOP devs started out where you are right now: a FOP user. We too saw features missing, and tried to help out where we could, up to the point of diving into the code and implementing them ourselves. Let me take your answer: I wonder, how should I have known about the fix. It would have sufficed to read the first line of the message you got from Bugzilla, although I do realize now I forgot to paste the link to the revision that fixed the bug. Sorry. I specifically looked at the answers to my error report before I sent my reply and had not found any indication of it there. As a user I am equiped with the necessary environment to keep the softwares I am routinely using current. In this case using toroiseSVN I have checked out the complete FOP trunk just to find that, just as you suggest, if I want to use it I should build it myself. I didn't. (To state it slightly I wasn't in the right mood.) [In fact I had already installed a different workaround before I submitted the bug report.] OK, so that means that you can easily synchronize the fop.jar in your project with a scheduled Subversion checkout, followed by a build and deployment... What are you complaining about? On the FOP Download page I found this: Fixme (jeremias) Reenable the link to the SVN snapshots once they are available. Now, what the heck it's supposed to mean?!. Can you tell me a valid reason why there are no daily (or at least weekly) snapshot builds of the trunk available at least on the main FOP server? Because someone needs to allocate time to set that up, and the demand is not nearly high enough to make this a pressing matter. I follow both fop-dev@ and fop-users@ almost on a daily basis, and I can't even remember how long ago it was that someone asked for these nightly builds. Probably those that thought they needed it, finally came upon a brilliant idea: Why don't I do the build myself, and synchronize my local sandbox with the repository? As I indicated, this is Open Source. We are not professionals when we are here. We all monitor this list, respond to postings (even when they're strictly speaking off-topic), take a shot at fixing long- standing but annoying bugs... Why? All /because we like to/ Whether, if or when new features get implemented, bugs fixed, releases done... this all depends on small human factors, such as a fop-dev working for a customer: if that customer absolutely needs features implemented, there you will suddenly see some things improved in a short time. Anyway, why should I be at the bleeding edge with FOP Trunk if I only need a small, safe and fully tested fix in the 0.93 branch that I can easily update if there is a new build available. Indeed, why should you even have a complete build? If you could download only the altered class, and replace that in your fop.jar... Again, schedule an 'svn up' of your local sandbox, rebuild and deploy. Why waste Apache's bandwidth on downloading much larger precompiled binaries? And finally knowing the history of FOP your mentioning of a new release is not too promising either. Please, do no take all this as an offence I have not meant it to be. Undoubtedly. You were just having a bit of fun, weren't you? ;P Cheers, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SPAM] font-family=Arial Unicode MS in rtf doesn't work
But at the same time, the spec does say it SHOULD be quoted, so you should quote it. Excuse the buttler butting in but what the spec says is: Font family names containing whitespace should be quoted. If quoting is omitted, any whitespace characters before and after the font name are ignored and any sequence of whitespace characters inside the font name is converted to a single space. To me it means that even if not quoted font-family=Arial Unicode MS still ferers to a single font not to the sequece Arial, Unicode, MS. JN -- View this message in context: http://www.nabble.com/font-family%3D%22Arial-Unicode-MS%22-in-rtf-doesn%27t-work-tf3177039.html#a9048364 Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SPAM] font-family=Arial Unicode MS in rtf doesn't work
József Németh wrote: Excuse the buttler butting in but what the spec says is: Font family names containing whitespace should be quoted. If quoting is omitted, any whitespace characters before and after the font name are ignored and any sequence of whitespace characters inside the font name is converted to a single space. To me it means that even if not quoted font-family=Arial Unicode MS still ferers to a single font not to the sequece Arial, Unicode, MS. You're right, but didn't someone say very recently that they had a fix for this bug? Daniel -- Daniel Noll Nuix Pty Ltd Suite 79, 89 Jones St, Ultimo NSW 2007, AustraliaPh: +61 2 9280 0699 Web: http://nuix.com/ Fax: +61 2 9212 6902 This message is intended only for the named recipient. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this message or attachment is strictly prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: font-family=Arial Unicode MS in rtf doesn't work
Thanks Jeremias it's work! If we want to use font name with whitespaces like Arial Unicode MS, we must put it in quotes. If I understand well, I think we can even do this font-family='Arial Unicode MS', 'Lucida Sans Unicode', sans-serif Dominic Subject: Re: font-family=Arial Unicode MS in rtf doesn't work From: Jeremias Maerki [EMAIL PROTECTED] Date: Mon, 05 Feb 2007 23:03:04 +0100 To: fop-users@xmlgraphics.apache.org To: fop-users@xmlgraphics.apache.org Try font-family='Arial Unicode MS' http://www.w3.org/TR/xsl11/#font-family says: Font family names containing whitespace should be quoted. On 05.02.2007 22:36:32 Dominic Marcotte wrote: Hello, Font-family Arial Unicode MS in FO become Arial in RTF. Like if font-family can't have a space in their name. fo:inline font-family=Arial Unicode MS font-style=normal font-size=9.5pt⇓/fo:inline If I try with font-family ArialUnicodeMS, I get ArialUnicodeMS in RTF but I Word or WordPad doesn't konw this font. I must change it manualy to Arial Unicode MS. I use FOP Trunk revision 499827. Any suggestion? Dominic Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: font-family=Arial Unicode MS in rtf doesn't work
On Feb 6, 2007, at 07:22, Andreas L Delmelle wrote: snip / All that needs to be done, IIC, is to override Maker.make (PropertyList, String, FObj) in FontFamilyProperty. Note that this is about the only property that can contain spaces, where these spaces do /not/ signify boundaries between multiple values, as a list of font-families will be separated by commas. Should be simple enough for someone who wants to get his feet wet... Might even take it on myself, if no one beats me to it. FWIW: already did this locally (incl. normalization of sequences of more than one space). It all boils down to an added 35-40 lines of code... As soon as I'm 100% sure that the testcases that now fail, are failing as a result of the previous patch being applied, I'll commit the changes to the Trunk. Cheers, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: font-family=Arial Unicode MS in rtf doesn't work
Should be simple enough for someone who wants to get his feet wet... snip FWIW: already did this locally (incl. normalization of sequences of more than one space). It all boils down to an added 35-40 lines of code... As soon as I'm 100% sure that the testcases that now fail, are failing as a result of the previous patch being applied, I'll commit the changes to the Trunk. You almost had me convinced to take a stab at this one! Yeah, I'm not sure why anyone would want multiple spaces between words as previously quoted. I can't see how that would be desirable. In my case, I'm using Altova StyleVision to generate XSL-FO files, and obviously that product writes font families as they are declared locally, i.e., with single spaces between words. Jeff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: font-family=Arial Unicode MS in rtf doesn't work
Jeff Vannest wrote: font-family=Arial Unicode MS is already quoted, right? Eh, not from the view point of the FO processor. The quotes are for the XML parser, which passes the string Arial Unicode MS (without the angle brackets) on to the FO processor, which has its own rules about strings and quotations. Check the FO property grammar for details. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: font-family=Arial Unicode MS in rtf doesn't work
Jeff Vannest wrote: Yeah, I'm not sure why anyone would want multiple spaces between words as previously quoted. I can't see how that would be desirable. Line wrapping with indentation done by tools which take every space as a line break opportunity. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: font-family=Arial Unicode MS in rtf doesn't work
I understand; it may be necessary to collapse multiple white space into a single space before evaluation. Not that it is recommended as a solution to something. lightbulb/ Jeff -Original Message- From: J.Pietschmann [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 06, 2007 4:29 PM To: fop-users@xmlgraphics.apache.org Subject: Re: font-family=Arial Unicode MS in rtf doesn't work Jeff Vannest wrote: Yeah, I'm not sure why anyone would want multiple spaces between words as previously quoted. I can't see how that would be desirable. Line wrapping with indentation done by tools which take every space as a line break opportunity. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
font-family=Arial Unicode MS in rtf doesn't work
Hello, Font-family Arial Unicode MS in FO become Arial in RTF. Like if font-family can't have a space in their name. fo:inline font-family=Arial Unicode MS font-style=normal font-size=9.5pt⇓/fo:inline If I try with font-family ArialUnicodeMS, I get ArialUnicodeMS in RTF but I Word or WordPad doesn't konw this font. I must change it manualy to Arial Unicode MS. I use FOP Trunk revision 499827. Any suggestion? Dominic - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: font-family=Arial Unicode MS in rtf doesn't work
I've noticed the same going to PDF. For some reason specifying Arial Unicode MS is not honored. I worked around it by using the Arial font-family and mapping the Arial triplets to the ARIALUNI.TTF in the userconfig.xml. Jeff -Original Message- From: Dominic Marcotte [mailto:[EMAIL PROTECTED] Sent: Monday, February 05, 2007 4:37 PM To: fop-users@xmlgraphics.apache.org Subject: font-family=Arial Unicode MS in rtf doesn't work Hello, Font-family Arial Unicode MS in FO become Arial in RTF. Like if font-family can't have a space in their name. fo:inline font-family=Arial Unicode MS font-style=normal font-size=9.5pt?/fo:inline If I try with font-family ArialUnicodeMS, I get ArialUnicodeMS in RTF but I Word or WordPad doesn't konw this font. I must change it manualy to Arial Unicode MS. I use FOP Trunk revision 499827. Any suggestion? Dominic - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: font-family=Arial Unicode MS in rtf doesn't work
Try font-family='Arial Unicode MS' http://www.w3.org/TR/xsl11/#font-family says: Font family names containing whitespace should be quoted. On 05.02.2007 22:36:32 Dominic Marcotte wrote: Hello, Font-family Arial Unicode MS in FO become Arial in RTF. Like if font-family can't have a space in their name. fo:inline font-family=Arial Unicode MS font-style=normal font-size=9.5pt⇓/fo:inline If I try with font-family ArialUnicodeMS, I get ArialUnicodeMS in RTF but I Word or WordPad doesn't konw this font. I must change it manualy to Arial Unicode MS. I use FOP Trunk revision 499827. Any suggestion? Dominic Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: font-family=Arial Unicode MS in rtf doesn't work
Jeremias Maerki wrote: Try font-family='Arial Unicode MS' http://www.w3.org/TR/xsl11/#font-family says: Font family names containing whitespace should be quoted. ...but not must ;-) Still, this all sounds awfully familiar. Interestingly, 0.20.5 did support it without spaces... at least as far as I remember. Daniel -- Daniel Noll Nuix Pty Ltd Suite 79, 89 Jones St, Ultimo NSW 2007, AustraliaPh: +61 2 9280 0699 Web: http://nuix.com/ Fax: +61 2 9212 6902 This message is intended only for the named recipient. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this message or attachment is strictly prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: font-family=Arial Unicode MS in rtf doesn't work
Jeremias Maerki wrote: Try font-family='Arial Unicode MS' http://www.w3.org/TR/xsl11/#font-family says: Font family names containing whitespace should be quoted. font-family=Arial Unicode MS is already quoted, right? To my knowledge, all attribute values must be quoted in order to meet most SGML-based specifications. I am not familiar with any cases where double-quoting values should be recommended. Jeremias, are you referring to a known bug? Jeff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: font-family=Arial Unicode MS in rtf doesn't work
Jeff Vannest wrote: Jeremias Maerki wrote: Try font-family='Arial Unicode MS' http://www.w3.org/TR/xsl11/#font-family says: Font family names containing whitespace should be quoted. font-family=Arial Unicode MS is already quoted, right? To my knowledge, all attribute values must be quoted in order to meet most SGML-based specifications. I am not familiar with any cases where double-quoting values should be recommended. The reason is that the CSS specification (which XSL-FO happens to borrow from in this instance) recommends the quotes. To make matters more interesting, the spec also says that a font family like Arial Unicode MS (no quotes, and note the double spaces) should also resolve back to Arial Unicode MS (single spaces). FOP doesn't do any of this of course, it splits at the spaces, which is a spec violation the way I see it. But at the same time, the spec does say it SHOULD be quoted, so you should quote it. Daniel -- Daniel Noll Nuix Pty Ltd Suite 79, 89 Jones St, Ultimo NSW 2007, AustraliaPh: +61 2 9280 0699 Web: http://nuix.com/ Fax: +61 2 9212 6902 This message is intended only for the named recipient. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this message or attachment is strictly prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: font-family=Arial Unicode MS in rtf doesn't work
On Feb 6, 2007, at 03:59, Daniel Noll wrote: Jeff Vannest wrote: Jeremias Maerki wrote: Try font-family='Arial Unicode MS' http://www.w3.org/TR/xsl11/#font-family says: Font family names containing whitespace should be quoted. font-family=Arial Unicode MS is already quoted, right? To my knowledge, all attribute values must be quoted in order to meet most SGML-based specifications. I am not familiar with any cases where double- quoting values should be recommended. The reason is that the CSS specification (which XSL-FO happens to borrow from in this instance) recommends the quotes. To make matters more interesting, the spec also says that a font family like Arial Unicode MS (no quotes, and note the double spaces) should also resolve back to Arial Unicode MS (single spaces). FOP doesn't do any of this of course, it splits at the spaces, which is a spec violation the way I see it. If anyone feels like fixing it, the problem is roughly: the standard PropertyParser parses the property Arial Unicode MS as a ListProperty containing three StringProperties All that needs to be done, IIC, is to override Maker.make (PropertyList, String, FObj) in FontFamilyProperty. Note that this is about the only property that can contain spaces, where these spaces do /not/ signify boundaries between multiple values, as a list of font-families will be separated by commas. Should be simple enough for someone who wants to get his feet wet... Might even take it on myself, if no one beats me to it. Cheers, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
