Re: Hyphenation
Luca Furini wrote: Hi all! I am an italian student of the University of Bologna. I have tried to solve a few problems concerning hyphenation, in particular: - show the '-' at the end of the hyphenated lines - use the fo:hyphenate property to enable hyphenation, instead of the alignment - specify the hyphenation character using the fo:hyphenation-character property Thanks for trying. Unfortunately we need a bit more information for your suggested change to make it to the code base. Most importantly, which version of the code are you trying to fix? Maintenance or HEAD? Secondly, could you please follow the procedure for submitting patches, described here: http://xml.apache.org/fop/dev/index.html#patches Please include sample FO files that demonstrate before and after effects of your changes. Thanks very much, Chris
Re: hyphenation patterns
> Keiron, I assume it was you who wrote two of the mails and put the > notifications on the Wiki page? With only the IP address it's difficult > to tell (you can register your name in "Preferences". Nudge, nudge). Was > it Togan, you contacted or one of the other two? Not that we write to > the same people twice. Thanks Sorry about that, still trying to sort out how this wiki stuff works. Yes, I sent mails to the email for those who submitted the files. Keiron. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Japanese Hyphenation was: Re: hyphenation patterns
Konnichiwa. On Fri, 07 Mar 2003 20:22:36 +0100 , J.Pietschmann wrote: > Hm. I don't read japanese :-/ JIS X 4051 illustrates line-breaking, justification, writing-mode, letter-spacing, ruby, etc. for Japanese text processing. CSS3 module:text is useful to understand these features in English. http://www.w3.org/TR/css3-text/ This document is probably same as JIS X 4051. Following section is espeically useful for line-breaking. 6. Line breaking 11.2. Hanging punctuation: the 'hanging-punctuation' property Another useful document is following book. http://www.oreilly.com/catalog/cjkvinfo/index.html CJKV Information Processing Chinese, Japanese, Korean & Vietnamese Computing By Ken Lunde 1st Edition December 1998 1-56592-224-7, Order Number: 2247 1125 pages > > Certainly, many japanese people wish that FOP will implement it, > > but the Japanese Tex hypenation file does not work with current > > FOP. > > What's the reason for this? I got the impression both the Japanese > and the Chinese TeX versions patched also the TeX source in order > to adapt to their respective line breaking rules. I'm not sure > how relevant this is to hyphenation. Current FOP can not control any line breaking restrictions. The Asian languages line-breaking strategy has different controls from those of western text. In Japanese, this restriction is called 'kinsoku'. A set of kinsoku character is Open Punctuation, Close Punctuation and Ambiguous Quotation defined in UAX#14. For example, you must not layout U+300C (LEFT CORNER BRACKET) categorized in OP at the end of line and U+3002 (IDEOGRAPHIC FULL STOP) categorized in CP at the head of line. These restriction is estimated at each end of line where is same point as the western soft-hyphenate estimation (i.e. break opportunity estimation). Can FOP currently control these restrictions without any modification? If can, it is my misunderstanding and Japanese Tex hypenation file can use it. But if can not, FOP must implements this feature to use Japanese Tex hypenation file. I think that the cost to implement JIS X 4051 line breaking algorithm is almost equivalent to implement TR14. So I suggested to implement TR14. > This is planned for HEAD. The TR14 rules for CJK hyphenation seems > to be easy: in absence of any more complicated requirements, > hyphenate after every full character. Does the above mentioned > standard add such "more complicated rules" which TR14 does not > care too much about? There is no "more complicated rules" for line-breaking. CSS3 module:text says following :-) http://www.w3.org/TR/css3-text/#line-break-prop | The rules described by JIS X-4051 have been superseded by | the Unicode Technical Report #14. JIS X 4051 line-breaking and TR14 is almost equivalent. In addition, TR14 can use for CJKV and any language with single Unicode Line-Break-Properties file! --- Satoshi Ishigami VIC TOKAI CORPORATION - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Japanese Hyphenation was: Re: hyphenation patterns
Satoshi Ishigami wrote: The JIS X 4051 spec is written in Japanese. I don't know whether there is English version spec, or not. Hm. I don't read japanese :-/ Certainly, many japanese people wish that FOP will implement it, but the Japanese Tex hypenation file does not work with current FOP. What's the reason for this? I got the impression both the Japanese and the Chinese TeX versions patched also the TeX source in order to adapt to their respective line breaking rules. I'm not sure how relevant this is to hyphenation. I think that FOP should implements UAX#14(TR14) if possible. For example, AntennaHouse's XSLFormatter implements UAX#14. This is planned for HEAD. The TR14 rules for CJK hyphenation seems to be easy: in absence of any more complicated requirements, hyphenate after every full character. Does the above mentioned standard add such "more complicated rules" which TR14 does not care too much about? J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
On 07.03.2003 14:36:49 Togan Muftuoglu wrote: > Hi, > > * Jeremias Maerki; <[EMAIL PROTECTED]> on 06 Mar, 2003 wrote: > >> Let me know if you need further information , > > > >It would be good if we could find the location where the trhyph.tex in > >the SuSE ditribution comes from. I don't want to download the whole > >thing just for verifying one little file. > > I have asked the maintainer and the reply is a follows > > > In the .spec file it isn't listed separately. Thus I assume it's part > of the regular teTeX distribution. Hope this helps! > > > > So I would asssume all the teTeX distributions have trhypen.tex file and > Debian is also strict with licenses so if it's in Debian then it means > at least it has the TeX licence Too many assumptions for me. :-) > Hope this helps. Do you want me to contact Turgut Uyar or have you done > it already I can do that. I've also found an email address of Pierre MacKay. Keiron, I assume it was you who wrote two of the mails and put the notifications on the Wiki page? With only the IP address it's difficult to tell (you can register your name in "Preferences". Nudge, nudge). Was it Togan, you contacted or one of the other two? Not that we write to the same people twice. Thanks Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
Hi, * Jeremias Maerki; <[EMAIL PROTECTED]> on 06 Mar, 2003 wrote: Let me know if you need further information , It would be good if we could find the location where the trhyph.tex in the SuSE ditribution comes from. I don't want to download the whole thing just for verifying one little file. I have asked the maintainer and the reply is a follows In the .spec file it isn't listed separately. Thus I assume it's part of the regular teTeX distribution. Hope this helps! So I would asssume all the teTeX distributions have trhypen.tex file and Debian is also strict with licenses so if it's in Debian then it means at least it has the TeX licence Hope this helps. Do you want me to contact Turgut Uyar or have you done it already -- Togan Muftuoglu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
* J.Pietschmann; <[EMAIL PROTECTED]> on 06 Mar, 2003 wrote: Togan Muftuoglu wrote: side note why do I have to work the harder way no spellchecker no hyphenation I started wondering am I the only one using these things under Linux :-( Until recently ispell was "good enough". It's a bit dated now but you could check Savannah whether anybody picked it up for further development. SourceForge has a handful of projects for spell checkers, most of which should be cross-platform. Which does not imply they can be already used. Then there is MozSpell, and OpenOffice has some sort of spell checker too. It gets off topic yet for the record there is none for Turkish ( Ok there is hyphenation for Turkish under an unknown licence for TeX) I just did for myself a Turkish dictionary to be used with aspell yet with a language like Turkish the wordlist can be as conjugated to a figure like 100.000.000.000 so it is not realistic and possible to have affixes to be able to create such a big list from a 35.000 root words -- Togan Muftuoglu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Japanese Hyphenation was: Re: hyphenation patterns
Konnichiwa. On Thu, 06 Mar 2003 22:32:10 +0100 , J.Pietschmann wrote: > On a related matter: some time ago someone mentioned the japanese > hyphenation standard. I was not able to find the document, probably > all web sites dealing with this are in japanese. Is there anybody > listening who can help out? I wrote it in the past. http://marc.theaimsgroup.com/?l=fop-dev&m=102992807207069&w=2 The JIS X 4051 spec is written in Japanese. I don't know whether there is English version spec, or not. Certainly, many japanese people wish that FOP will implement it, but the Japanese Tex hypenation file does not work with current FOP. I think that FOP should implements UAX#14(TR14) if possible. For example, AntennaHouse's XSLFormatter implements UAX#14. UAX#14, Line Breaking Properties http://www.unicode.org/reports/tr14/ Old discussion related with TR14 in fop-dev is http://marc.theaimsgroup.com/?l=fop-dev&w=2&r=1&s=tr14&q=b --- Satoshi Ishigami VIC TOKAI CORPORATION - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
Did you see my earlier mail to Marcelo Jaccoud Amaral? I'd like to wait until we get answers from licensing@ (especially because of the grant thing). On 06.03.2003 21:45:58 J.Pietschmann wrote: > Jeremias Maerki wrote: > >>-pt.xml iseems ok and can be put back? > > No, it isn't IMO. It forbids commercial usage which is not forbidden by > > FOP's license. > > This was the old pt.xml. Should I recommit the new one (released > under APL)? I thought I committed it both to HEAD and the maintenance > branch... Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Japanese Hyphenation was: Re: hyphenation patterns
On a related matter: some time ago someone mentioned the japanese hyphenation standard. I was not able to find the document, probably all web sites dealing with this are in japanese. Is there anybody listening who can help out? J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
Togan Muftuoglu wrote: side note why do I have to work the harder way no spellchecker no hyphenation I started wondering am I the only one using these things under Linux :-( Until recently ispell was "good enough". It's a bit dated now but you could check Savannah whether anybody picked it up for further development. SourceForge has a handful of projects for spell checkers, most of which should be cross-platform. Which does not imply they can be already used. Then there is MozSpell, and OpenOffice has some sort of spell checker too. Now the really big thing would be a grammar checker. I've still my old notes from 15 years ago for a grammar checker for german and english, but no time at all to do any real coding... :-/ J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
Jeremias Maerki wrote: Unfortunately, that's not so easy. You've created a derived work, which can't simply claim full copyright for. In the realm of legal battles, wording matters. Claiming copyright is ok as long as there was "substantial work" put into creating the Derived Work. Claiming the right to choose a lincense is quite another matter and depends on the license of the Original Work. It turns out that the file mentions multiple authors. Now the question is: Who is the copyright owner Each one is a copyright owner, and perhaps *all* would have to agree on a license change, depending on the license(s) the file had through its history. It's also a matter of courtesy. that can give us the right to use, modify and redistribute that file? Pierre A. MacKay seems to be the original author. H. Turgut Uyar has modified it. Now, who owns the copyright? It depends. For a start, Mr. MacKay apparently didn't create his stuff for the sole purpose of creating hyphenation files. This means the creator of the TeX file can not only claim copyright but also created an Original Work rather than a Derived Work, so he can also choose a license, as long as the original doesn't have a very restrictive license (which would probably also make creating and using the TeX hyphenation file illegal, so I suppose this isn't the case). There is still the problem that the TeX file is explicitely labeled as "Mechanically generated", which can be interpreted in a way that there wasn't "substantial work" put into creating the TeX file, which means it isn't even a Derived work but basically another representation of the original material and Mr. Uyar can't even claim copyright. The "slight modifications" however should be enough to fix this. Therefore, depending on the interpretation we've either have to ask Mr. Uyar only (interpretation 1) or both (interpretation 2). http://www.ctan.org/tex-archive/language/turkish/hyphen/turk_hyf.c from Pierre A. MacKay which states that in case of commercial distribution the author must be contacted. This is not a real problem as long as the license doens't require that Derived Works must be distributed under a similar condition. that there could be problems with licensing. The whole TeX thing is a legal nightmare if you ask me. Well, the whole Intellectual Property stuff is a nightmare. This is a direct result of assigning substantial value to intangibles... J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
* Jeremias Maerki; <[EMAIL PROTECTED]> on 06 Mar, 2003 wrote: related C source file http://www.ctan.org/tex-archive/language/turkish/hyphen/turk_hyf.c from Pierre A. MacKay which states that in case of commercial distribution the author must be contacted. Which is one more indicator that there could be problems with licensing. The whole TeX thing is a legal nightmare if you ask me. Well, maybe we (or I) are overdoing things here but we (or I) want to do it right. Well shoot I found his papers and the whole thing is about with ottoman turkish ( not the turkish we use today and his original hypenation is tkhyphen.tex ) and now I know why there are some silly suggestions when hyphenating :-) Let me know if you need further information , It would be good if we could find the location where the trhyph.tex in the SuSE ditribution comes from. I don't want to download the whole thing just for verifying one little file. I will ask the tetex maintainer to find I out I'll let you know as soon as I get a reply from him. side note why do I have to work the harder way no spellchecker no hyphenation I started wondering am I the only one using these things under Linux :-( Thanks -- Togan Muftuoglu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
Jeremias Maerki wrote: -pt.xml iseems ok and can be put back? No, it isn't IMO. It forbids commercial usage which is not forbidden by FOP's license. This was the old pt.xml. Should I recommit the new one (released under APL)? I thought I committed it both to HEAD and the maintenance branch... J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
On 06.03.2003 19:41:30 Togan Muftuoglu wrote: > * Jeremias Maerki; <[EMAIL PROTECTED]> on 06 Mar, 2003 wrote: > >Thanks for bringing it up again. It forgot that in the pile of work > >these license problems generate. I'm sorry. I've updated the Wiki page > >accordingly. > > I know you have tons of stuff to be sorted our with these licenses. Just > to make sure that as the submitter of the tr.xml let me know if tehre is > anything I can do to assist Thank you! > * Keiron Liddle; <[EMAIL PROTECTED]> on 05 Mar, 2003 wrote: > >Hello Togan, > > > >In the FOP project we a trying to clear up some license issues. > >You donated a turkish hyphenation patterns file. > > > >What is the license for that? Did you modify the original tex hyphenations and > >what was the license for that file? > > Well I had send an email on Feb 17th 2003 to fop-dev mailinglist about > this issue and Jeremias said he would contact Turgut Uyar as there is no > license on the header. My modification is only to make FOP use the file > and I do not think that is rocket science :-) Nevertheless if you also > need grant for my work FOP project may use it Unfortunately, that's not so easy. You've created a derived work, which can't simply claim full copyright for. It turns out that the file mentions multiple authors. Now the question is: Who is the copyright owner that can give us the right to use, modify and redistribute that file? Pierre A. MacKay seems to be the original author. H. Turgut Uyar has modified it. Now, who owns the copyright? We would probably have to get a permission from both people. So that's three in the end if we count you in. And there's more. I've just found a related C source file http://www.ctan.org/tex-archive/language/turkish/hyphen/turk_hyf.c from Pierre A. MacKay which states that in case of commercial distribution the author must be contacted. Which is one more indicator that there could be problems with licensing. The whole TeX thing is a legal nightmare if you ask me. Well, maybe we (or I) are overdoing things here but we (or I) want to do it right. > Let me know if you need further information , It would be good if we could find the location where the trhyph.tex in the SuSE ditribution comes from. I don't want to download the whole thing just for verifying one little file. > * Jeremias Maerki; <[EMAIL PROTECTED]> on 14 Feb, 2003 wrote: > >tr.xml > >Can't find original file. > >No licence. Check with author. > > Well, since I sent out the Turkish hyphenation file I should know where > it comes right. The trhyphen.tex is installed from the SuSE 8.1 distro > > [EMAIL PROTECTED]:~/hangar> rpm -qf /usr/share/texmf/tex/generic/hyphen/trhyph.tex > tetex-beta.20020207-254 > > the trhyph.tex file has the following header > > % A mechanically generated Turkish Hyphenation table for TeX, > % using the University of Washington diacritical coding > % developed by P. A. MacKay for the Ottoman Texts Project. > % Slightly modified by H. Turgut Uyar. > > Turgut Uyar has the following addres based on "google search" > [EMAIL PROTECTED] > > Would you like to contact him directly or do you want me to do so ? > Although I think you can explain the needs and requirements better than > I can Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
Hi, * Jeremias Maerki; <[EMAIL PROTECTED]> on 06 Mar, 2003 wrote: Thanks for bringing it up again. It forgot that in the pile of work these license problems generate. I'm sorry. I've updated the Wiki page accordingly. I know you have tons of stuff to be sorted our with these licenses. Just to make sure that as the submitter of the tr.xml let me know if tehre is anything I can do to assist * Keiron Liddle; <[EMAIL PROTECTED]> on 05 Mar, 2003 wrote: Hello Togan, In the FOP project we a trying to clear up some license issues. You donated a turkish hyphenation patterns file. What is the license for that? Did you modify the original tex hyphenations and what was the license for that file? Well I had send an email on Feb 17th 2003 to fop-dev mailinglist about this issue and Jeremias said he would contact Turgut Uyar as there is no license on the header. My modification is only to make FOP use the file and I do not think that is rocket science :-) Nevertheless if you also need grant for my work FOP project may use it Let me know if you need further information , * Jeremias Maerki; <[EMAIL PROTECTED]> on 14 Feb, 2003 wrote: tr.xml Can't find original file. No licence. Check with author. Well, since I sent out the Turkish hyphenation file I should know where it comes right. The trhyphen.tex is installed from the SuSE 8.1 distro [EMAIL PROTECTED]:~/hangar> rpm -qf /usr/share/texmf/tex/generic/hyphen/trhyph.tex tetex-beta.20020207-254 the trhyph.tex file has the following header % A mechanically generated Turkish Hyphenation table for TeX, % using the University of Washington diacritical coding % developed by P. A. MacKay for the Ottoman Texts Project. % Slightly modified by H. Turgut Uyar. Turgut Uyar has the following addres based on "google search" [EMAIL PROTECTED] Would you like to contact him directly or do you want me to do so ? Although I think you can explain the needs and requirements better than I can -- Togan Muftuoglu -- Togan Muftuoglu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
Thanks for bringing it up again. It forgot that in the pile of work these license problems generate. I'm sorry. I've updated the Wiki page accordingly. I've submitted some questions today concerning license issues. As soon as I get the answers I'm going to contact you so we can finally readd your file. Thanks for your patience! On 06.03.2003 15:54:08 jaccoud wrote: > > >> other issues: > >> -pt.xml iseems ok and can be put back? > >[Jeremias Maaerki] > >No, it isn't IMO. It forbids commercial usage which is not forbidden by > >FOP's license. We cannot guarantee that the file is indirectly used for > >commercial purposes. I could be wrong. I'll ask on on licensing. > > I already discussed this with Herr Pietschmann and agreed to donate the > file to the ASF, provided the credits and bilingual comments are preserved. > As I said the previous license was there because of my laziness, I just > copied the old one... > However, because no one seemed to agree how to insert the licence in the > file (short or long). It seems it is already in the codebase, and you my > apply the appropriate licence in the way you find appropriate. I can send > another copy if needed. > I am happy to provide Portuguese-parliant users with a appropriate file, > even though this is a very small contribution. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
>> other issues: >> -pt.xml iseems ok and can be put back? >[Jeremias Maaerki] >No, it isn't IMO. It forbids commercial usage which is not forbidden by >FOP's license. We cannot guarantee that the file is indirectly used for >commercial purposes. I could be wrong. I'll ask on on licensing. I already discussed this with Herr Pietschmann and agreed to donate the file to the ASF, provided the credits and bilingual comments are preserved. As I said the previous license was there because of my laziness, I just copied the old one... However, because no one seemed to agree how to insert the licence in the file (short or long). It seems it is already in the codebase, and you my apply the appropriate licence in the way you find appropriate. I can send another copy if needed. I am happy to provide Portuguese-parliant users with a appropriate file, even though this is a very small contribution. By the way, is there a way to turn off the [ERROR] Couldn't find hyphenation pattern pt_br using general language pattern pt instead. message? First, I don't see it as an error, but a warning. Second, it is not relevant to Portuguese: spelling may change from pt-PT to pt-BR, but that does not affect hyphenation. (I know it does for other languages.) Better, is there a way to tell FOP that the same hyphenation rules (file) can be used for any pt[-XX] language values? = Marcelo Jaccoud Amaral Petrobrás (http://www.petrobras.com.br) mailto:[EMAIL PROTECTED] = The way to get things done is not to mind who gets the credit of doing them.--Benjamin Jowett >Sorry, I've been busy last week getting my barcode package a new home. >Almost forgot about the issues here. On 04.03.2003 01:51:27 Christian Geisert wrote: > if I understand it right we are allowed to distribute the LPPL > hyphenation patterns (both source and binary) together with FOP > if we add the LPPL LICENSE for the patterns (for example in the > in the root dir) to the distribution ? > (And to be safe I'll ask this on licensing@) I want to ask at licensing first. I've finally received my confirmation for admission to this mailing list. I'll do that today. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
On 04.03.2003 09:37:51 Jeremias Maerki wrote: > > -has anybody tried to contact the authors of patterns with unclear licence? > > Forgot to do that. Sorry. Will do today. Ok, I wrote to the authors of certain files where I see some probability of success in finding the original author and getting permission for further use. Please see the Wiki page for details: http://nagoya.apache.org/wiki/apachewiki.cgi?FOPAudits/March2003 This was some really unpleasant work today. I'm looking forward to do some coding again. I hope we can resolve the whole thing soon. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
I've added a detailed Wiki page on the licensing audit for FOP where I intend to track the status of all current issues. http://nagoya.apache.org/wiki/apachewiki.cgi?FOPAudits To the XML PMC members listening in: I'll follow up with direct questions to licensing@ especially about the LPPL issue. Any help with sorting out the issues is appreciated. Next on my list is to write to some of the hyphenation pattern authors for clarification of the license. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
Sorry, I've been busy last week getting my barcode package a new home. Almost forgot about the issues here. On 04.03.2003 01:51:27 Christian Geisert wrote: > if I understand it right we are allowed to distribute the LPPL > hyphenation patterns (both source and binary) together with FOP > if we add the LPPL LICENSE for the patterns (for example in the > in the root dir) to the distribution ? > (And to be safe I'll ask this on licensing@) I want to ask at licensing first. I've finally received my confirmation for admission to this mailing list. I'll do that today. > other issues: > -pt.xml iseems ok and can be put back? No, it isn't IMO. It forbids commercial usage which is not forbidden by FOP's license. We cannot guarantee that the file is indirectly used for commercial purposes. I could be wrong. I'll ask on on licensing. > -what about renaming en_GB.xml to en.xml? +1 > -I remember *something* about hu.xml but couldn't find it I wrote a mail to the original author but didn't get an answer. The mail didn't bounce, though. > -has anybody tried to contact the authors of patterns with unclear licence? Forgot to do that. Sorry. Will do today. I'm strongly for investigating the possibility to make use of the hyphenation packages from OpenOffice. Although they are LGPL we could support them and tell our users where they can get them. Not a very nice thing because our users have to do the license evaluations themselves but at least we are on the safe side. Is anyone out there who would like to do that? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Hyphenation patterns included in fop-0.20.5rc2
On 19.02.2003 16:47:30 Clay Leeds wrote: > Thanks for the quick response. Can this information be added to the > release notes and/or readme? I'll put it on my todo list if nobody does it before I do. > I see that en_GB.xml exists but what's the story on what I would assume > would be called en_US.xml (US English hyphenation patterns file)? Does > it exist? Is it missing due to licensing issues? The removal of hyphenation files was exclusively triggered by licence issues. We don't have an en_US.xml that we're confortble with ATM. > Also, I've searched for filenames & "text" contents in my fop > installations (.4 & .5rc2) and I haven't found the hyphenation pattern > files. Where are they stored? In the binary distribution they are in the hyph directory of fop.jar (in "compiled" form). In the source distribution they are under src/hyph as XML files. > Jeremias Maerki wrote: > > FOP version 0.20.5rc2 contains the following hyphenation files: > > > > - en_GB.xml: British English > > - es.xml: Spanish > > - fi.xml: Finnish > > - hu.xml: Hungarian > > - it.xml: Italian > > - pl.xml: Polish > > > > Christian, I'm most uneasy about hu.xml. It's the only one that IMO > > doesn't have an explicit statement that the file is in the public domain. > > The original (?) file I found contained a notice about free distribution, > > but our file doesn't contain a unambiguous reference to the original > > file, so I must assume that the copyrights are not entirely clear. > > Therefore, I am -1 (veto) on keeping that one for the moment. Does > > anyone disagree? > FWIW, I would agree. It should be relatively easy for users to download > the hyphenation files (especially if we provide a list with links! ;-). > I certainly don't think it's worth the risk to include files with > questionable licensing issues. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Hyphenation patterns included in fop-0.20.5rc2
Thanks for the quick response. Can this information be added to the release notes and/or readme? I see that en_GB.xml exists but what's the story on what I would assume would be called en_US.xml (US English hyphenation patterns file)? Does it exist? Is it missing due to licensing issues? Also, I've searched for filenames & "text" contents in my fop installations (.4 & .5rc2) and I haven't found the hyphenation pattern files. Where are they stored? Jeremias Maerki wrote: FOP version 0.20.5rc2 contains the following hyphenation files: - en_GB.xml: British English - es.xml: Spanish - fi.xml: Finnish - hu.xml: Hungarian - it.xml: Italian - pl.xml: Polish Christian, I'm most uneasy about hu.xml. It's the only one that IMO doesn't have an explicit statement that the file is in the public domain. The original (?) file I found contained a notice about free distribution, but our file doesn't contain a unambiguous reference to the original file, so I must assume that the copyrights are not entirely clear. Therefore, I am -1 (veto) on keeping that one for the moment. Does anyone disagree? FWIW, I would agree. It should be relatively easy for users to download the hyphenation files (especially if we provide a list with links! ;-). I certainly don't think it's worth the risk to include files with questionable licensing issues. -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Hyphenation patterns included in fop-0.20.5rc2
FOP version 0.20.5rc2 contains the following hyphenation files: - en_GB.xml: British English - es.xml: Spanish - fi.xml: Finnish - hu.xml: Hungarian - it.xml: Italian - pl.xml: Polish Christian, I'm most uneasy about hu.xml. It's the only one that IMO doesn't have an explicit statement that the file is in the public domain. The original (?) file I found contained a notice about free distribution, but our file doesn't contain a unambiguous reference to the original file, so I must assume that the copyrights are not entirely clear. Therefore, I am -1 (veto) on keeping that one for the moment. Does anyone disagree? On 18.02.2003 17:51:42 Clay Leeds wrote: > Esteemed feathery FOPpers, > > BTW, congrats & stuff on the release! I just ran it, and it didn't give > me an error! ;-) > > Would you let us know which hyphenation files are included with FOP > 0.20.5rc2? I think that would be useful information to include in the > fop-dev & fop-user mailing lists for archival/searching purposes, and > the only reference to what is included is en_GB. It might also be useful > to include in the reply, the status of other hyphenation patterns (and > links if they exist). > > I checked out the current installation, and had a tough time finding > info on Hyphenation. After doing a search on the fop-0.20.5rc2 > directory, I found this file: > >fop-0.20.5rc2\examples\fo\basic\hyphen.fo > > Is that example the sum total of the hyphenation stuff in FOP? Or was > everything removed (Christian indicated "removal of some hyphenation > patterns")? If it's there, then I couldn't find it. If it's not, then > the RelNotes should read "most" hyphenation patterns... > > Thanks for the great effort! It looks *great*! Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Hyphenation patterns for portuguese (with the patterns, this time )
Thanks for the hyph file. I have committed this to cvs. Is it possible for you to supply an example fo file containing some portuguese text that works with the hyphenation. On 2002.04.09 11:48 Paulo Soares wrote: > This hyphenation patterns for portuguese may be of interest for inclusion > in > FOP. > > Best Regards, > Paulo Soares > > > <> - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation file for greek
I browsed the site and it looks like this is the place to submit. I attach the file in this message. Sorry for not being acustomed to Apache-style framework. Regards, Dimitris Kamenopoulos &agr;&Agr; &aacgr;&Aacgr; &bgr;&Bgr; &ggr;&Ggr; &dgr;&Dgr; &egr;&Egr; &eacgr;&Eacgr; &zgr;&Zgr; &eegr;&EEgr; &eeacgr;&EEacgr; &THgr;&thgr; &igr;&Igr; &iacgr;&Iacgr; &idigr;&Idigr; &idiagr; &udigr;&Udigr; &udiagr; &oacgr;&Oacgr; &uacgr;&Uacgr; &kgr;&Kgr; &lgr;&Lgr; &mgr;&Mgr; &ngr;&Ngr; &xgr;&Xgr; &ogr;&Ogr; &pgr;&Pgr; &rgr;&Rgr; &sgr;&Sgr;&sfgr; &tgr;&Tgr; &ugr;&Ugr; &phgr;&PHgr; &khgr;&KHgr; &psgr;&PSgr; &ohacgr;&OHacgr; &ohgr;&OHgr; &dgr;&igr;-&aacgr; &pgr;&ogr;&igr;-&oacgr;&ngr; &pgr;&ogr;&igr;-&ogr;&uacgr; 4&bgr;1&zgr; 4&bgr;1&thgr; 4&bgr;1&ngr; 4&bgr;1&xgr; 4&bgr;1&pgr; 4&bgr;1&sgr; 4&bgr;1&tgr; 3&bgr;1&phgr; 4&bgr;1&khgr; 3&bgr;1&psgr; 4&ggr;1&bgr; 4&ggr;2&zgr; 4&ggr;1&thgr; 4&ggr;1&mgr; 4&rgr;5&ggr;2&mgr; 4&ggr;1&khgr; 4&ggr;1&pgr; 4&ggr;1&tgr; 4&ggr;1&phgr; 4&ggr;1&khgr; 4&ggr;1&psgr; 4&dgr;1&bgr; 4&dgr;1&ggr; 4&dgr;1&zgr; 4&dgr;1&kgr; 4&dgr;1&lgr; 4&dgr;1&xgr; 4&dgr;1&pgr; 4&dgr;1&sgr; 4&dgr;1&tgr; 4&dgr;1&khgr; 4&dgr;1&psgr; 4&zgr;1&bgr; 4&zgr;1&dgr; 4&zgr;1&thgr; 4&zgr;1&kgr; 4&zgr;1&lgr; 4&zgr;1&mgr; &tgr;&zgr;2&mgr; 4&zgr;1&ngr; 4&zgr;1&xgr; 4&zgr;1&pgr; 4&zgr;1&rgr; 4&zgr;1&sgr; 4&zgr;1&tgr; 4&zgr;1&phgr; 4&zgr;1&khgr; 4&zgr;1&psgr; 4&thgr;1&bgr; 4&thgr;1&ggr; 4&thgr;1&dgr; 4&thgr;1&zgr; 4&kgr;1&kgr; 4&kgr;1&pgr; 4&kgr;1&khgr; 4&kgr;1&psgr; 4&lgr;1&bgr; 4&lgr;1&ggr; 4&lgr;1&dgr; 4&lgr;1&zgr; 4&lgr;1&thgr; 4&lgr;1&kgr; 4&lgr;1&mgr; 4&lgr;1&ngr; 4&lgr;1&xgr; 4&lgr;1&pgr; 4&lgr;1&rgr; 4&lgr;1&sgr; 4&lgr;1&tgr; 4&lgr;1&phgr; 4&lgr;1&khgr; 4&lgr;1&psgr; 4&mgr;1&bgr; 4&mgr;1&ggr; 4&mgr;1&dgr; 4&mgr;1&zgr; 4&mgr;1&thgr; 4&mgr;1&kgr; 4&mgr;1&lgr; 4&mgr;1&phgr; 4&mgr;1&khgr; 4&mgr;1&psgr; 4&ngr;1&bgr; 4&ngr;1&ggr; 4&ngr;1&dgr; 4&ngr;1&zgr; 4&ngr;1&thgr; 4&ngr;1&kgr; 4&ngr;1&lgr; 4&ngr;1&mgr; 4&ngr;1&xgr; 4&ngr;1&pgr; 4&ngr;1&rgr; 4&ngr;1&sgr; 4&ngr;1&phgr; 4&ngr;1&khgr; 4&ngr;1&psgr; 4&xgr;1&bgr; 4&xgr;1&ggr; 4&xgr;1&dgr; 4&xgr;1&zgr; 4&xgr;1&thgr; 4&xgr;1&kgr; 4&xgr;1&lgr; 4&xgr;1&mgr; 4&xgr;1&ngr; 4&xgr;1&pgr; 4&xgr;1&rgr; 4&xgr;1&sgr; 4&xgr;1&tgr; 4&ggr;4&xgr;2&tgr; 4&rgr;4&xgr;2&tgr; 4&xgr;1&phgr; 4&xgr;1&khgr; 4&xgr;1&psgr; 4&pgr;1&bgr; 4&pgr;1&ggr; 4&pgr;1&dgr; 4&pgr;1&zgr; 4&pgr;1&thgr; 4&pgr;1&kgr; 4&pgr;1&mgr; 4&pgr;1&xgr; 4&pgr;1&sgr; 4&pgr;1&phgr; 4&pgr;1&khgr; 4&pgr;1&psgr; 4&rgr;1&bgr; 4&rgr;1&ggr; 4&rgr;1&dgr; 4&rgr;1&zgr; 4&rgr;1&thgr; 4&rgr;1&kgr; 4&rgr;1&lgr; 4&rgr;1&mgr; 4&rgr;1&ngr; 4&rgr;1&xgr; 4&rgr;1&pgr; 4&rgr;1&sgr; 4&rgr;1&tgr; 4&rgr;1&phgr; 4&rgr;1&khgr; 4&rgr;1&psgr; 4&sgr;1&dgr; 4&sgr;1&zgr; 4&sgr;1&ngr; 4&sgr;1&xgr; 4&sgr;1&rgr; 4&sgr;1&psgr; 4&tgr;1&bgr; 4&tgr;1&ggr; 4&tgr;1&dgr; 4&tgr;1&thgr; 4&tgr;1&kgr; 4&tgr;1&ngr; 4&tgr;1&xgr; 4&tgr;1&pgr; 4&tgr;1&phgr; &sgr;&tgr;2&phgr; 4&tgr;1&khgr; 4&tgr;1&psgr; 4&phgr;1&bgr; 4&phgr;1&ggr; 4&phgr;1&dgr; 4&phgr;1&zgr; 4&phgr;1&mgr; 4&phgr;1&ngr; 4&phgr;1&xgr; 4&phgr;1&pgr; 4&phgr;1&sgr; 4&phgr;1&khgr; 4&phgr;1&psgr; 4&psgr;1&bgr; 4&psgr;1&ggr; 4&psgr;1&dgr; 4&psgr;1&zgr; 4&psgr;1&thgr; 4&psgr;1&kgr; 4&psgr;1&lgr; 4&psgr;1&mgr; 4&psgr;1&ngr; 4&psgr;1&xgr; 4&psgr;1&pgr; 4&psgr;1&rgr; 4&psgr;1&sgr; 4&psgr;1&tgr; 4&psgr;1&phgr; 4&psgr;1&khgr; &agr;1 &egr;1 &eegr;1 &igr;1 &ogr;1 &ugr;1 &ohgr;1 &ohacgr;1 &agr;2&igr; &agr;2&iacgr; &agr;2&ugr; &agr;2&uacgr; &aacgr;3&ugr; &egr;2&igr; &egr;2&iacgr; &egr;2&ugr; &egr;2&uacgr; &eacgr;3&ugr; &eegr;2&ugr; &eeacgr;3&ugr; &ogr;2&igr; &ogr;2&iacgr; &ogr;2&ugr; &ogr;2&uacgr; &oacgr;3&ugr; &ugr;2&igr; &ugr;2&iacgr; &uacgr;3&igr; &agr;2&eegr; &aacgr;3&eegr; &agr;2&idigr; &agr;2&udigr; &egr;2&idigr; &oacgr;2&egr;&igr; &ogr;2&eegr; &oacgr;3&eegr; &ogr;2&idigr; &oacgr;3&igr; &igr;2&agr; &igr;2&aacgr; &igr;2&egr; &igr;2&eacgr; &igr;2&ogr; &igr;2&oacgr; 4&bgr;. 4&ggr;. 4&ggr;&kgr;. 4&dgr;. 4&zgr;. 4&thgr;. 4&kgr;. 4&lgr;. 4&mgr;. 4&mgr;&pgr;. 4&ngr;. 4&ngr;&tgr;. 4&xgr;. 4&pgr;. 4&rgr;. 4&sgr;. 4&tgr;. 4&tgr;&zgr;. 4&tgr;&sgr;. 4&phgr;. 4&khgr;. 4&psgr;. 4' 4&bgr;' 4&ggr;&kgr;' 4&zgr;' 4&lgr;' 4&mgr;' 4&mgr;&pgr;' 4&ngr;' 4&ngr;&tgr;' 4&xgr;' 4&pgr;' 4&rgr;' 4&sgr;' 4&tgr;' 4&tgr;&zgr;' 4&tgr;&sgr;' 4&phgr;' 4&khgr;' 4&psgr;' .&bgr;4 .&ggr;4 .&dgr;4 .&zgr;4 .&thgr;4 .&kgr;4 .&lgr;4 .&mgr;4 .&ngr;4 .&xgr;4 .&pgr;4 .&rgr;4 .&sgr;4 .&tgr;4 .&phgr;4 .&khgr;4 .&psgr;4 4&bgr;1&bgr; 4&ggr;1&ggr; 4&zgr;1&zgr; 4&thgr;1&thgr; 4&lgr;1&lgr; 4&mgr;1&mgr; 4&ngr;1&ngr; 4&pgr;1&pgr; 4&rgr;1&rgr; 4&sgr;1&sgr; 4&tgr;1&tgr; &tgr;&phgr;1&phgr; 4&khgr;1&khgr; 3&psgr;1&psgr; 4&ggr;5&kgr;2&phgr; 4&ggr;1&kgr;&tgr; 4&mgr;1&pgr;&tgr; 4&ngr;1&tgr;&zgr; 4&ngr;1&tgr;&sgr; 4&bgr;&rgr;. 4&ggr;&lgr;. 4&kgr;&tgr;. 4&ggr;&kgr;&sgr;. 4&kgr;&sgr;. 4&lgr;&sgr;. 4&mgr;&pgr;&lgr;. 4&mgr;&pgr;&ngr;. 4&mgr;&pgr;&rgr;. 4&mgr;&sgr;. 4&ngr;&sgr;. 4&rgr;&sgr;. 4&sgr;&
