Note that this <tt>.gpr.py</tt> will automatically use translations if you have them (see [[#Localization|Localization]]). That is, the function "_" is predefined to use your locale translations; you only need to mark the text with <tt>_("TEXT")</tt> and include a translation of "TEXT" in your translation file. For example, in the above example, <tt>_("Attach Source")</tt> is marked for translation. If you have developed and packaged your addon with translation support, then that phrase will be converted into the user's language.

Each #possible report category has a set of standards and interface. The categories CATEGORY_TEXT and = 0 CATEGORY_DRAW use the Document interface of Gramps. See also = 1 CATEGORY_CODE = 2 CATEGORY_WEB = 3 CATEGORY_BOOK = 4 CATEGORY_GRAPHVIZ = 5 CATEGORY_TREE = 6 REPORT_CAT = [[Report API]CATEGORY_TEXT, CATEGORY_DRAW, CATEGORY_CODE, CATEGORY_WEB, CATEGORY_BOOK, CATEGORY_GRAPHVIZ, CATEGORY_TREE] for a draft view on this.

Each report category has a set of standards and an interface. The categories <tt>CATEGORY_TEXT</tt> and <tt>CATEGORY_DRAW</tt> use the Document interface of Gramps. See also [[Report API]] for a draft view on this. The application programming interface or API for reports is treated at in the [[Report-writing_tutorial]]. For general information on Gramps development , see [[Portal:Developers]] and [[Writing a plugin|Writing a Plugin]] specifically.