Jeroen Ruigrok van der Werven wrote: > On 5/19/06, ymasuda <[EMAIL PROTECTED]> wrote: > > Although there are no explicit rules for translated doc, I think there > > should be some guidelines: for example, reStructuredText, with ".txt" > > extension, UTF-8 for non-ASCII charsets, etc. If there are any > > additional requirements, please point them out. > > I typically use .rst for restructured text so that vim (and possibly > other editors) can pick up the appropriate highlighting easily. > > What I typically did for some projects is making sure every document > contains the revision id from the document it was translated from. In > this way you have a easier synchronisation mark to work from when the > documentation changes.
Thanks Jeroen for comment. The original Django document comes with source code distribution with '.txt' suffix, so I prefer to use '.txt'. Exactly as you pointed, revision id of the original document is very important. Since it's a kind of metada, I think commit messages are more appropreate for it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
