Changes between Version 44 and Version 45 of TracTicketTemplatePlugin


Ignore:
Timestamp:
Dec 7, 2015, 11:10:26 AM (7 years ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified
  • TracTicketTemplatePlugin

    v44 v45  
    55== Description
    66
    7 This plugin enables users to create a ticket using templates which can be customized by Trac administrator and themselves.
     7This plugin enables users to create a ticket using templates which can be customized by the Trac administrator and the users themselves.
    88
    99Key features:
     
    1414=== Changes in version 0.7
    1515
    16  * This version has fully i18n support with Trac `0.12dev-r9098` above.
    17  * New feature: support '''My Template'''. Everyone can manage their own templates now.
     16 * This version has full i18n support with Trac `0.12dev-r9098` and above.
     17 * New feature: support '''My Template''': everyone can manage their own templates now.
    1818 * New feature: add permission '''TT_USER''' to fine-grained control '''My Template'''.
    1919 * New feature: template can include any fields, the default field is description.
     
    2121 * New feature: support importing and exporting ticket_templates (by Russell Ballestrini).
    2222 
    23 See: '''ZoomQuiet''' ~ Collection KSPEG Trac hacking
     23See: '''ZoomQuiet''' ~ Collection KSPEG Trac hacking.
    2424
    2525== Bugs/Feature Requests
     
    4545'''Important''': Please backup your ticket templates if you are upgrading this plugin.
    4646
    47 Prerequisite: [pypi:simplejson simplejson] when Python is earlier than version 2.6.
     47Prerequisite: [pypi:simplejson Simplejson] when Python is earlier than version 2.6.
    4848
    49 You can install this software as a normal Trac plugin.
     49You can install this software as a normal Trac plugin:
    5050
    5151 1. Uninstall this plugin if you have installed it before.
     
    8181Current languages supplied with the plugin are:
    8282 * English (default)
    83  * Chinese(simplified)
     83 * Chinese (simplified)
    8484 * Japanese
    8585 * German
     
    8787
    8888If you can't find the language you want, you could do it yourself.
    89  1. Init your language catalog, take `et_EE` for example:
     89 1. Init your language catalog, taking `et_EE` (Estonian) as an example:
    9090 {{{#!sh
    9191python setup.py init_catalog -l et_EE
     
    9595python setup.py update_catalog -l et_EE
    9696}}}
    97  1. Do translate with your favorite editor, the language file locate in tickettemplate/loclate/et_EE/LC_MESSAGES/tickettemplate.po
    98   * Note: this .po file should be saved with UTF8 encoding.
     97 1. Translate with your favorite editor, the language file locate in `tickettemplate/loclate/et_EE/LC_MESSAGES/tickettemplate.po`
     98  * Note: this .po file should be saved with UTF-8 encoding.
    9999 1. Update catalog again, for normalizing the manual edits:
    100100 {{{#!sh
     
    120120
    121121 * Trac administrator should define the template for all ticket types:
    122   * Login as administrator, open Admin -> Ticket System -> Ticket Template
    123   * '''load''' the template of each ticket type, modify them and '''apply changes'''
     122  * Login as administrator, open Admin -> Ticket System -> Ticket Template.
     123  * '''load''' the template of each ticket type, modify them and '''apply changes'''.
    124124 * After defined ticket template, normal user can create ticket using predefined template by '''change ticket types''' dropdown list items.
    125125
    126 || Screen capture of the //New Ticket// page =|| [[Image(NewTicketPage-v0.7.png,50%)]] ||
    127 || Screen capture of the //Admin// panel =|| [[Image(AdminTicketTemplatePage-v0.7.png,50%)]] ||
     126|| Screen capture of the //New Ticket// page =|| [[Image(NewTicketPage-v0.7.png, 70%)]] ||
     127|| Screen capture of the //Admin// panel =|| [[Image(AdminTicketTemplatePage-v0.7.png, 70%)]] ||
    128128
    129129 * About template params:
     
    131131  * The template:
    132132  {{{
    133 blah blah %(my_param)s blah blah
     133foo bar %(my_param)s baz qux
    134134}}}
    135135  * Call newticket:
     
    139139  * Rendered:
    140140  {{{
    141 blah blah anything blah blah
     141foo bar anything baz qux
    142142}}}
    143143  * And owner field would be filled by myname by Trac's default convention.