<<If you can't read it it is not clearly indicated.
Ken
>>
I can't read Chinese, but an OGL product declared as 100% OGC would be clearly indicated. Readability is not a requirement. Clear indication is. And "this entire compiled binary is absolutely, with no exceptions, 100% OGC" is about as clear a designation as I can manage. Again -- there's no requirement for character sheets that the Quark file you lay them out in be distributed with the character sheet. There should be no requirement that code be destributed with a binary -- the binary is being distributed and needs licensing, not the code (which is not being distributed).
...
Another list member wrote:
<<(And to show that I'm not being obtuse...) No, the real problem with making
the whole file OGC is that you probably don't have the right to contribute
the runtime library of your development environment as OGC. However, if you
didn't use the built-in runtime library (good luck there) then you probably
could contribute the whole executable as OGC.>>
And I don't even know that this is an issue. If your compiler packages specific free-standing DLLs with your application, then declare the compiled binary as OGC and the external DLLs as "not OGC". If your compiler just makes one monster binary with no external files, then you may have a problem.
Lee
