Ævar Arnfjörð Bjarmason wrote: > There's some documentation aimed at developing that I'd like to see / > write in Git at some point. > > Developing: > > * How to work with Gettext > > * How to write portable code, i.e. constructs to avoid in C / shell > script etc (these keep coming up). Maybe: Documentation/technical/api-gettext.txt Documentation/CodingGuidelines Documentation/PlatformNotes or some variations on the theme? > * How to deal with gettext / submit po files / keep them up to date > etc. gittranslation.7? > * Core git concepts (that need to be translated), maybe I could > adopt the gitglossary to this task, but it'd need to be a bit > more structured, i.e. describe core data concepts first, then > some other terms. That sounds good. Once we develop infrastructure for translating manpages, we could encourage translators to do gitglossary first to standardize terminology. > Actually, on that point, do we have documentation that describes > git's data model in one place? I.e. everything from blobs to > trees, how raw commit objects etc. look. Something like "Git for > computer scientists". Hopefully some pic wizard can convert that to nroff. :) I think Tommi Virtanen should be easy to reach in case anyone wants to try adapting the article somehow. Hope that helps, Jonathan -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html