> So one way to move forward is to effectively have two manuals, one > containing traditional user-written text (GFDL), the other containing > generated text (GPL). If you print it out as a book, the generated > part would just appear as an appendix to the manual, it's "mere > aggregation".
This is not acceptable to me. You have just described the status quo, what we are already doing. It is very difficult to link api references to manual references in two separate documents. What I want to do is full integration, and not be forced into these aggregations. And I am being denied. I am very disheartened by this conversation. I'm actually incredulous, exactly as expressed by Diego, that this is even an issue. These ivory tower replies about awesome docs written by programmer-scribe-monks for simple C interfaces that none of the email authors is in fact writing are incredibly annoying to me, as somebody who is actually doing this work. Let's at least give weight to the people in the gcc community who are doing this work, ok? Or else I will stop doing it. This should be a minor detail, not a month long thread. All we are asking is for the permission to render GPL code as GFDL in addion to GPL. No freedoms are being lost here dudes. -benjamin
