Re: build customizability

[brainchild <ericlevy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

[-- Attachment #1.1: Type: text/plain, Size: 1834 bytes --]



> Just replying to this - in this case, you're getting far removed from 
> Pandoc's processing, to the point where the input file for Pandoc is no 
> longer compatible with your system.  What - at this point - is the 
> benefit for using the Pandoc codebase?  If all you want is to parse 
> Markdown or Latex or some other input format, there's lots of 
> specialized parsers out there. 
>

I believe the idea I am expressing is very different from the effect you 
describe.
 

> And further than that - what is the benefit to *Pandoc* of you using the 
> Pandoc code base?  Since this would require a large restructure of the 
> core code, what makes that restructure worthwhile to the Pandoc project? 
>   Again, you're getting well off of Pandoc's goals and aim - and there 
> are other products that do aim for that use. 
>

I'm not sure what you're asking. Pandoc itself can experience no benefits, 
only its users and contributors, who participate in discussions such as 
this one. The amount of restructuring required, however much it is 
determined to be, as for any proposed enhancement, indeed might be a 
prohibitive factor. At the moment, a discussion is occurring such that the 
various difficulties may be discussed openly. 


Note further my earlier comments, which make note of a group already using 
Pandoc. 


What specific project goals do you feel the proposed idea might undermine 
or challenge?
  
 

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/a6771fd7-3253-43bc-82b3-caf659052052%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2585 bytes --]