Edgewall Software

Changes between Version 25 and Version 26 of MissingTranslations


Ignore:
Timestamp:
May 8, 2010, 1:51:32 PM (14 years ago)
Author:
Christian Boos
Comment:

clean-up done tasks

Legend:

Unmodified
Added
Removed
Modified
  • MissingTranslations

    v25 v26  
    88=== Admin
    99 - For ''Priorities'', ''Ticket Types'', ''Resolutions'', ''Severities'':
    10    - ~~When adding new enum, the name of the field in the message "The %(field)s \"%(name)s\" has been added." is not translatable.~~
    11    - ~~When removing existing enums, the name of the field in the message "The selected %(fields)s have been removed." is not translatable.~~
    12    - ~~When attempting to add enums with duplicate names, the name of the field in the message "%(type)s %(name)s already exists" is not translatable.~~
    1310   - Note that for ''Milestones'' and ''Versions'' the template file contains separate messages, so they are translatable.
    1411   - Make headers of enum pages be translated as a whole, and not composed of two separate translated words, to allow for correct casing/wording in different languages ([source:trunk/trac/admin/templates/admin_enums.html@9547:19,33#L13])
     
    3027
    3128=== Timeline
    32  - ~~Milestone ''milestone'' completed~~
    3329 - The postfix link "(diff)" is not translatable ([source:trunk/trac/wiki/web_ui.py@9561:719#L705])
    3430
    3531=== Milestone
    36  - ~~In ''view milestone'' the dropdown of the ''ticket status by'' is not translatable.~~
    3732 - In ''view milestone'' and in ''roadmap'', the "Active" and "Closed" words (referring the ticket counts) are not translatable.
    3833
    3934=== Reports
    40 
    41  - ~~Number of matches in reports view.~~ Example:
    42  {{{
    43  (2 matches)
    44  }}}
    4535
    4636 - "Ticket" and "Created" headers in the reports table.
     
    4838=== Ticket
    4939
    50  - ~~When editing a comment, three buttons are shown. Titles (<input ... '''title'''="") of two of them — "Preview" and "Submit changes" — are not translatable.~~
    51  - ~~Two buttons are show next to every comment — "Reply" and "Edit". Titles (<input ... '''title'''="") of them both are not translatable.~~ r9328
    52   [[br]]
    53   Actually, there were ''lots'' of issues with title attributes: those attributes are collected automatically (i.e. no need for explicit `${_('...')}` expressions), but only when the message doesn't contain an expression.
     40// TODO: i18n tips // 
     41 title attributes:: those attributes are collected automatically (i.e. no need for explicit `${_('...')}` expressions), but only when the message doesn't contain an expression.
    5442  In the latter case, they need an explicit `${_('... %(param)s ...', param=...)}` wrapping.
    5543
    56  - ~~In ''newticket'', The ''Reporter'' fieldset title is not translatable.
    57  In ''view ticket'', the ''Author'' fieldset title is not translatable.~~ (same issue)
    58 
    59  - ~~''Attach another file'' button text on `trac/attachment/ticket/<ticketID>` page~~
    60 
    6144=== Query
    62  - ~~When checking the "Show description under each result" ins ''query result'',
    63    the description section that appears below each ticket contains the word ''description'', which is not translatable.~~
    6445
    6546=== Changesets
    66  - ~~When viewing file diff, the ''set'' in "Property %(propname)s set to" is not translatable
    67    (which is strange, considering that in the source browser it is fine..)~~
    6847
    6948=== Wiki
     
    7150==== Version(s) deletion
    7251
    73  - ~~When trying to delete version(s) of wiki pages, on the confirmation page buttons "Delete this version" and "Delete those versions" are not translatable.~~
    74 
    75  - ~~On the same page, the words in italics are not translatable too:~~
    76  > '''Delete ''version(s) 2 to 7'' of WikiStart'''
    77  >
    78  > Are you sure you want to delete ''versions 2 to 7'' of this page?
    79 
    8052==== Page deletion
    81  - ~~When trying to completely delete a page, on the confirmation page the button "Delete page" is not translatable.~~
    82 
    83  - ~~On the same page the word in italics is not translatable:~~
    84  > Are you sure you want to ''completely'' delete this page?
    8553
    8654== Errors
    87  - ~~When attempting ''login'' with no authentication configuration, the message "Authentication information not available. Please refer to the installation documentation." is not translatable.~~
    8855
    8956== Inappropriate grouping
    90  - ~~The string "by" in ''timeline'' and in ''milestone_view'' (which is grouped in the messages template) does not have the same meaning (see also #9159).
    91    In timeline it means the user who made the last change ("by whom"), and in milestone_view it refers to the field to be grouped by ("according to what").~~
    92    - ~~More specifically, the string "ticket status by" in the milestone_view should be treated as one, and not split to "ticket status" and "by".~~
    9357
    9458== Unnecessary strings
     59
    9560This strings probably unchanged in all translations:
    9661{{{
     
    10570}}}
    10671(rblank) I don't know if we can actually ''prevent'' those from being extracted from templates.
    107 {{{
    108 #: trac/templates/macros.html:161
    109 #, fuzzy, python-format
    110 msgid "%(title)s %(unit)s:"
    111 msgid_plural "%(title)s %(units)s:"
    112 }}}
    113 ~~This is #8588 and would be needed for the same reason as the one below, but having different keys unit/units in msgid and msgid_plural doesn't make msgfmt happy...~~
    11472
    115 {{{
    116 #: trac/ticket/templates/ticket.html:267
    117 #: trac/ticket/templates/ticket_box.html:43
    118 #, python-format
    119 msgid "%(field)s:"
    120 }}}
    121 ~~This one is very important and needed for typographical translations
     73// TODO: i18n tips //
     74 typographical translations ::
    12275(e.g. in French, it will be translated to "%(field)s :" and that space is a non-breaking space.
    12376I'll try to see if adding a i18n:comment attribute works.~~