Look what I've just found:
http://linux.org.mt/projects/jtextcheck/jtextcheck-ooohyph-plugin/index.html
It's LGPL (and so are OO's hyphenation patterns if I remember correctly)
but if we provide a plug-in mechanism and host the actual adapter under
the LGPL at http://offo.sour
On Sep 13, 2004, at 11:51 AM, Simon Pepping wrote:
On Mon, Sep 13, 2004 at 08:03:08AM -0700, Clay Leeds wrote:
Thanks for setting this up, Simon. Please let me know if there is
anything I can do to help.
Thanks for the offer. It was some work to set this up, although I
could build mostly on Jeremia
On Sun, Sep 12, 2004 at 11:35:42AM +1000, Peter B. West wrote:
> Moved from fop-user.
>
> Simon,
>
> Under which license have you set up the SourceForge project?
I stated that contributions with any OSI-approved license or in the
Public Domain were acceptable. The discussion to get the idea
expl
On Mon, Sep 13, 2004 at 08:03:08AM -0700, Clay Leeds wrote:
> Thanks for setting this up, Simon. Please let me know if there is
> anything I can do to help.
Thanks for the offer. It was some work to set this up, although I
could build mostly on Jeremias' earlier work. I expect that from now
on th
Thanks for setting this up, Simon. Please let me know if there is
anything I can do to help.
Web Maestro Clay
Simon Pepping wrote:
Dear FOP users,
In February 2004 a large number of hyphenation pattern files were
removed from FOP's CVS repository due to licensing issues. These
hyphen
Moved from fop-user.
Simon,
Under which license have you set up the SourceForge project?
Peter
Simon Pepping wrote:
Dear FOP users,
In February 2004 a large number of hyphenation pattern files were
removed from FOP's CVS repository due to licensing issues. These
hyphenation patterns
gzilla/show_bug.cgi?id=28431
[PATCH] Hyphenation of words with punctuation marks
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RE
gzilla/show_bug.cgi?id=27773
[PATCH] Hyphenation
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
J.Pietschmann wrote:
Glen Mazza wrote:
I believe the same logger reference would just be used with each
thread instead,
es, and this is exactly the problem. It is conceivable that
different loggers might be used for different processors which
run in concurrent threads. A static logger reference
Glen Mazza wrote:
I believe the same logger reference would just be used with each thread
instead,
es, and this is exactly the problem. It is conceivable that
different loggers might be used for different processors which
run in concurrent threads. A static logger reference prohibits
this.
J.Piets
J.Pietschmann wrote:
Mutable static data, like a static logger reference, interferes
severely with using FOP in an MT environment, because this means
"one thread rendering globally" rather than "one thread per FO
processor rendering, perhaps using multiple processors, each one
in a separate thread
Simon Pepping wrote:
I like Joerg's idea of a Global Context object. It seems to have a
wider scope than FOUserAgent. An FOUserAgent object could be part of
it.
From the maintenance code's configuration it would need to have
baseDir, fontBaseDir, hyphenation-dir and strokeSVGText. Font
i
gt; be ideal if we could place all of this in FOUserAgent. (I also suspect
> that much of what will be in FOUserAgent/User configuration will be
> variable over time, which may also suggest we keep this all in one
> class.) BTW, what other things besides hyphenation needs to go into
Glen Mazza wrote:
BTW, what other things besides hyphenation needs to go into
user configuration/fo user agent, say for 1.0?
Various strategy parameters, once they are implemented, like
line breaking strategy; furthermore callbacks for redrawing
pages in a GUI renderer, font management, base URL
Glen Mazza wrote:
Should FOP itself multithread, or would it be better to let whatever
would call FOP do the multithreading?
I don't understand this. Even if the main processing methods
of the FO processing object are synchronizend, which is probaly
what you understand by "FOP isn't MT safe itself
Glen Mazza wrote:
I don't know what Xalan does with their translets, I suspect they just
rely on the caller to implement it.
Oops--my error--the translets just generate Java code. My comment was
in general for the need of XML processors such as Xalan and FOP to
implement MT internally.
Glen
class.) BTW, what other things besides hyphenation needs to go into
user configuration/fo user agent, say for 1.0?
Two more observations:
1.) What does the team think of placing all the FOUserAgent information
into the abstract apps.InputHandler class by either (a) full
incorporation (i.e
J.Pietschmann wrote:
Static objects are bad because of the usual MT issues (yeah,
even for logging).
Should FOP itself multithread, or would it be better to let whatever
would call FOP do the multithreading? I don't know what Xalan does with
their translets, I suspect they just rely on the call
Simon Pepping wrote:
But
hyphenation is done deep down in the process, where any reference to
the start-up objects is lost. How can I configure it?
The idea is to use an object which represents some global context
and is reachable from nearly anywhere in the FO tree and LM tree.
I'd think the
On 08.05.2004 23:04:40 Simon Pepping wrote:
> I am trying to enable user configuration of the directory of
> hyphenation files, like in the maintenance code. Configuration of the
> renderers is easy, because they are instantiated in Fop.main(). But
> hyphenation is done deep down in
Hi,
I am trying to enable user configuration of the directory of
hyphenation files, like in the maintenance code. Configuration of the
renderers is easy, because they are instantiated in Fop.main(). But
hyphenation is done deep down in the process, where any reference to
the start-up objects is
gzilla/show_bug.cgi?id=28431
[PATCH] Hyphenation of words with punctuation marks
--- Additional Comments From [EMAIL PROTECTED] 2004-04-26 19:35 ---
Luca,
I agree with item 1. Although the spaces before the hyphenated word
are often incorrect, the word is hyphenated correctly, and the
gzilla/show_bug.cgi?id=28431
[PATCH] Hyphenation of words with punctuation marks
[EMAIL PROTECTED] changed:
What|Removed |Added
Summary|Hyphenation of words with |[PATCH] Hyphe
gzilla/show_bug.cgi?id=28431
Hyphenation of words with punctuation marks
--- Additional Comments From [EMAIL PROTECTED] 2004-04-19 10:30 ---
Simon,
concernig names, unnecessary "if", etc. , I agree with you.
It seems to me that your change concerning hyphenation exceptions works
gzilla/show_bug.cgi?id=28431
Hyphenation of words with punctuation marks
--- Additional Comments From [EMAIL PROTECTED] 2004-04-17 05:17 ---
Your assumptions appear correct, I checked the Washington Post newspaper and saw
that hyphenation does indeed occur with words that have a period or co
gzilla/show_bug.cgi?id=28431
Hyphenation of words with punctuation marks
--- Additional Comments From [EMAIL PROTECTED] 2004-04-16 19:46 ---
Created an attachment (id=11265)
A slightly modified patch
gzilla/show_bug.cgi?id=28431
Hyphenation of words with punctuation marks
--- Additional Comments From [EMAIL PROTECTED] 2004-04-16 19:45 ---
Created an attachment (id=11264)
An expanded test fo file
gzilla/show_bug.cgi?id=28431
Hyphenation of words with punctuation marks
--- Additional Comments From [EMAIL PROTECTED] 2004-04-16 19:44 ---
Luca,
The patch works well.
I do not find the name bAfterLetter very clear. It really is
bNonLetterAfterLetters, but that is too long. I find bEndOfL
gzilla/show_bug.cgi?id=28431
Hyphenation of words with punctuation marks
--- Additional Comments From [EMAIL PROTECTED] 2004-04-16 13:30 ---
Created an attachment (id=11259)
test fo file: words with punctuation marks and parenthesis
gzilla/show_bug.cgi?id=28431
Hyphenation of words with punctuation marks
--- Additional Comments From [EMAIL PROTECTED] 2004-04-16 13:29 ---
Created an attachment (id=11258)
proposed patch to HyphenationTree
gzilla/show_bug.cgi?id=28431
Hyphenation of words with punctuation marks
Summary: Hyphenation of words with punctuation marks
Product: Fop
Version: 1.0dev
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Normal
Pr
> I think it would be better to report this item in a patch of
> its own. It really is a new issue.
Ok, sorry.
I'm going to do as you suggest.
Luca
have found another small bug concerning hyphenation in the
> HyphenationTree.hyphenate() method.
> Before checking the exception list or using the algorithm, the
> function "normalizes" the word: during this phase, if a non-letter character
> is found null is returned.
&
gzilla/show_bug.cgi?id=27773
[PATCH] Hyphenation
--- Additional Comments From [EMAIL PROTECTED] 2004-04-14 19:03 ---
Created an attachment (id=11238)
test fo file: words with punctuation marks and parenthesis
gzilla/show_bug.cgi?id=27773
[PATCH] Hyphenation
--- Additional Comments From [EMAIL PROTECTED] 2004-04-14 19:02 ---
Created an attachment (id=11237)
proposed patch to HyphenationTree
gzilla/show_bug.cgi?id=27773
[PATCH] Hyphenation
--- Additional Comments From [EMAIL PROTECTED] 2004-04-14 19:00 ---
Yes, I was quite surprised to see that all the information stored in the
BreakPoss was "thrown away" before adding areas; I chose to duplicate the
needed val
gzilla/show_bug.cgi?id=27773
[PATCH] Hyphenation
--- Additional Comments From [EMAIL PROTECTED] 2004-04-09 09:28 ---
Hi Luca,
Your patch looks good. It works fine on your test fo, and it also
works fine on a test fo I had lying around.
There are a few things to note:
AreaInfo.bHyphena
gzilla/show_bug.cgi?id=27773
[PATCH] Hyphenation
--- Additional Comments From [EMAIL PROTECTED] 2004-04-05 16:41 ---
Created an attachment (id=11138)
updated diff
gzilla/show_bug.cgi?id=27773
[PATCH] Hyphenation
--- Additional Comments From [EMAIL PROTECTED] 2004-04-05 16:40 ---
Sorry, I'm here again (hope I am not making too much a mess!) :-)
I'm going to attach an updated proposed patch, as I noticed there was an error
in the one I poste
gzilla/show_bug.cgi?id=27773
[PATCH] Hyphenation
--- Additional Comments From [EMAIL PROTECTED] 2004-04-05 09:22 ---
Hi all
I apologize for having posted some proposed changes without a line explaining
what I was changing and why.
Really sorry, I'm going to try and do it now.
First
gzilla/show_bug.cgi?id=27773
[PATCH] Hyphenation
--- Additional Comments From [EMAIL PROTECTED] 2004-03-19 11:39 ---
Created an attachment (id=10869)
FO sample file to test the behavior of fop before and after the patch
gzilla/show_bug.cgi?id=27773
[PATCH] Hyphenation
--- Additional Comments From [EMAIL PROTECTED] 2004-03-19 11:38 ---
Created an attachment (id=10868)
patch created using cvs diff
gzilla/show_bug.cgi?id=27773
[PATCH] Hyphenation
Summary: [PATCH] Hyphenation
Product: Fop
Version: 1.0dev
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Enhancement
Priority: Other
Component: page-
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
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
- s
rki wrote:
> > But that's not the reason I write this. I've done the relicensing on the
> > XML FOP project and was again confronted with our hyphenation files. Two
> > of them now have the ALv2 header because for these two files all legal
> > problems have been
Jeremias Maerki wrote:
But that's not the reason I write this. I've done the relicensing on the
XML FOP project and was again confronted with our hyphenation files. Two
of them now have the ALv2 header because for these two files all legal
problems have been dealt with
I don
(ccing fop-dev and XML PMC)
Last year I've invested hours after hours doing a license audit on the
XML FOP project mainly because of problems with the hyphenation pattern
files. These files have been converted to XML by FOP contributors but
almost all files are coming from TeX sof
jeremias2004/02/27 09:48:09
Modified:src/java/org/apache/fop/layout/hyphenation ByteVector.java
CharVector.java Hyphen.java Hyphenation.java
HyphenationException.java HyphenationTree.java
Hyphenator.java
FopImageConsumer.java
src/java/org/apache/fop/layout/hyphenation
HyphenationTree.java
Log:
Removed unnecessary semi-colon.
Revision ChangesPath
1.27 +1 -1 xml-fop/src/java/org/apache/fop/layoutmgr/PageLayoutManager.java
Index
gzilla/show_bug.cgi?id=13734
Hyphenation does not work correctly on long string with many '-'
--- Additional Comments From [EMAIL PROTECTED] 2003-12-29 09:24 ---
Sorry but this bug was created one year ago and I work no more on that subject
for several months.
The second prob
gzilla/show_bug.cgi?id=21641
Infinit loop within too small areas using hyphenation
--- Additional Comments From [EMAIL PROTECTED] 2003-12-21 19:01 ---
OK in the development version.
gzilla/show_bug.cgi?id=16713
Hyphenation error in tables
--- Additional Comments From [EMAIL PROTECTED] 2003-12-21 19:01 ---
The attachments require other files which are not attached: three xsl files and
an external graphic.
gzilla/show_bug.cgi?id=13734
Hyphenation does not work correctly on long string with many '-'
--- Additional Comments From [EMAIL PROTECTED] 2003-12-21 18:58 ---
The first case works OK in the development version. See attachment.
The behaviour of the second case is to be expecte
gzilla/show_bug.cgi?id=16626
Hyphenation causing java.io.IOException error
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RE
gzilla/show_bug.cgi?id=23985
Hyphenation Problems with filenames, numbers
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
gzilla/show_bug.cgi?id=23985
Hyphenation Problems with filenames, numbers
Summary: Hyphenation Problems with filenames, numbers
Product: Fop
Version: all
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Pr
gzilla/show_bug.cgi?id=22048
PDF renderer and hyphenation break character order
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RE
gzilla/show_bug.cgi?id=22048
PDF renderer and hyphenation break character order
Summary: PDF renderer and hyphenation break character order
Product: Fop
Version: 0.20.4
Platform: PC
URL: http://staff.csc.fi/aniemela/fopbug2.pdf
OS/Version:
gzilla/show_bug.cgi?id=21641
Infinit loop within too small areas using hyphenation
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|Critical|
gzilla/show_bug.cgi?id=21641
Infinit loop within too small areas using hyphenation
Summary: Infinit loop within too small areas using hyphenation
Product: Fop
Version: 0.20.5
Platform: PC
OS/Version: Other
Status: NEW
Severity: Cr
I did some rearranging in our doc to get the configuration page pared down
to only configuration information, and to move some configuration content
there that was lurking in other places (attempting to keep them
cross-referenced). One of the side effects is that the hyphenation doc has
been moved
ibility
to make use of OpenOffice.org's hyphenation stuff.
Umm, zilch. But then, th OOo hyphenation files I saw are just
the FOP hyphenation files sans XML tags and with character
encoding issues instead.
J.Pietschmann
-
To
ere. Additional candidates:
PDF library, Transcoders, a free image library etc. etc.
Another question: How does your work relate to the general possibility
to make use of OpenOffice.org's hyphenation stuff.
Jeremias Maerki
-
To
Hi,
as I wrote quite some weeks ago I took an extended look at
hyphenation, with the possible target of creating APL
licensed patterns from our own dictionaries. I also looked
at the current hyphenator.
I finally seem to have grasped how hyphenation and
hyphenation pattern generation from a marked
gzilla/show_bug.cgi?id=20411
German hyphenation is ^H^H^Hwas missing
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
gzilla/show_bug.cgi?id=20411
German hyphenation is ^H^H^Hwas missing
--- Additional Comments From [EMAIL PROTECTED] 2003-06-02 11:08 ---
Created an attachment (id=6595)
Hyphenation file for (new) German orthography
--
gzilla/show_bug.cgi?id=20411
German hyphenation is ^H^H^Hwas missing
Summary: German hyphenation is ^H^H^Hwas missing
Product: Fop
Version: 0.20.5
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority:
With the kind help of Alex V. Alishevskikh I've been able to commit a
new pattern file for russian. The file should be pretty safe from a
legal point of view. Interested parties will find the details in the
comments provided in ru.xml.
Yipee! :-)
Jeremias Maerki
the
> > one for committers. Thanks a lot!
> >
> > On 17.03.2003 15:23:55 Jeremias Maerki wrote:
> > > I've received an email a few minutes ago from a FOP contributor telling
> > > me that I will receive a confirmation mail from the original author of
>
e systems that agree exactly with the program presented
here."
Now, I suppose that an argument could be made that the hyphenation patterns
are not part of the algorithm, but I think an equally good argument can be
made that they are. They are certainly part of the TeX distribution, and
Knuth's lice
ontributor telling
> me that I will receive a confirmation mail from the original author of
> one of the problematic hyphenation files, that he allows us to use his
> file. But strictly following the rules I have to ask him to file a grant.
> I hope he
There's another IMO: Clause 7 expects a restriction that the ASL can't
provide.
On 17.03.2003 14:32:16 Dirk-Willem van Gulik wrote:
> See below the Latex License.
>
> http://www.latex-project.org/lppl.html
>
> It seems to me that clause '8.B" makes this license more restrictive than
> the
Thanks, Steven and Dirk for responding!
On 17.03.2003 14:28:44 Dirk-Willem van Gulik wrote:
>
> > > Before we start here's a little background on the hyphenation stuff:
> > > Our hyphenation file are XML files that are derived from TeX hyphenation
>
> Under wha
Folks,
See below the Latex License.
http://www.latex-project.org/lppl.html
It seems to me that clause '8.B" makes this license more restrictive than
the ASF license - and we thus should not allow code(fragements) which are
under this license in downloads from ASF infrastructure.
Or am
> > Before we start here's a little background on the hyphenation stuff:
> > Our hyphenation file are XML files that are derived from TeX hyphenation
Under what license where the original TeX files ?
> > 2. If the former (of [1]) is true, we need a grant from the copy
fop-devs)
>
> (I don't know where might be the best place to discuss this. fop-dev is
> currently very low-traffic.)
>
> The FOP team needs help. In February we realized that we had problematic
> hyphenation pattern files in our codebase. For example, some of them
> we
jeremias2003/03/11 04:52:22
xml-fop/src/java/org/apache/fop/layout/hyphenation - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
> 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 sam
anese 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
>
gzilla/show_bug.cgi?id=4316
Problem of hyphenation in inline-areas
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Reso
rrent
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(TR
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 t
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 hav
* 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&#
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
> liste
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 com
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
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 p
pends. 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
ng 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 :-(
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.Pie
t;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?
&
icenses. 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 patt
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 f
hough 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:
Hello all (licensing specialists, XML PMC people, fop-devs)
(I don't know where might be the best place to discuss this. fop-dev is
currently very low-traffic.)
The FOP team needs help. In February we realized that we had problematic
hyphenation pattern files in our codebase. For example,
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 gettin
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 PROT
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
1 - 100 of 247 matches
Mail list logo
