5 Mar
2010
5 Mar
'10
9:30 a.m.
On Thu, Mar 4, 2010 at 8:44 PM, James Fisherwrote: > I think you're thinking of 'forking' as something dangerous (yeah, the word > sounds painful), as something that will fragment the community, as something > that destroys the concept of 'authority'. It's really not. Where you get > forking you get merging at roughly the same rate. Just an example. I have made a sort of "fork" of luatex 0.46 with luatex lunatic --- see last eurotex meeting. This is what I have learned 1) it's doable by every one with some skills in programming 2) it's nothing new from typographical point of view 3) we -- as TeX community -- don't need it. So it's really true that one can modify/fork luatex for his needs --- and I will do it again, I have other binding on my list. It's also true that in this way luatex+mkiv can become your powerful and private tool for your particular workflow, or that in this manner some modifications can enter in main luatex, if Taco thinks that they are ok For example actually I see more and more problems in dynamic loading, so I think that my modifications are not ok for luatex --- but Taco has the last word , and it's not a problem for me. But, still, we -- as TeX community -- don't need it . Actually we must support Taco and Hans in their job of development luatex and mkiv with testing and meaningful request; development team is up and running from about 5years and they made a really good job until now and I see no reason for changes . (I'm not on dev. team btw. , so it's my opinion) This is why I don't see documentation as a high priority --- of course I'm always waiting the next pdf from Hans. -- luigi