Actually, I think it is pretty obvious what those files are for, at least it should be for those, who wants to apply for a dev position. However that is true, there is a room for improvement in the documentation of the code. So what we need there, is not a glossary, but proper documentation.
@KeiKun, true if you have some knowledge of C, java or C# you might find what each function does, but some commentaries aren't even translated (check the code for Japanese comments, they're still there since forever)
and I don't think it's fun for new people to search for every file just to know what a variable means or a function does, besides remember this is C, not a an OOP language where you can know directly which class you're using and where to search.
if you have knowledge with C language
its already easy to determine what that file is for~
I agree with you 100% Kratos.
I have about 2 years of OOP(Java) experience but I find I constantly have to refer to 2 or sometimes 3 other files to see what's going on in the source code.
Plus I think it would allow beginners/people whom aren't that familiar with source coding to get their feet wet as opposed to looking at the source, getting overwhelmed and giving up.