Modify

Opened 5 years ago

Closed 4 years ago

#762 closed defect (fixed)

Plugins description not translatable

Reported by: anonymous Owned by: stoecker
Priority: minor Component: Core
Version: Keywords:
Cc:

Description

Following elements are not translatable:

a) all presets
b) the plugin descriptions
c) the new MOTD (whereas the all start screen was)

At least the presets are a major issue. Fixing josm to allow translations as well as adapting the gettext calls to get the texts from the xml files should both not be too complicated.

Attachments (1)

Just add tr.patch (1.1 KB) - added by xeen 4 years ago.
Just add tr() around description

Download all attachments as: .zip

Change History (10)

comment:1 Changed 5 years ago by anonymous

  • Summary changed from Presets, Plugins description and MOTD not translatable to Plugins description not translatable

Updated subject. The others have been done.

Changed 4 years ago by xeen

Just add tr() around description

comment:2 Changed 4 years ago by xeen

  • Summary changed from Plugins description not translatable to [Patch?] Plugins description not translatable

Is there a reason why this can't be achieved using tr()? My guess is that these won't automatically show up in Launchpad hence making it either pretty useless or and immense amount of work.

If that's the case, I'll develop something more sophisticated.

comment:3 Changed 4 years ago by anonymous

  • Summary changed from [Patch?] Plugins description not translatable to Plugins description not translatable

We have a wiki and thus the texts can change always. Also the translations will not cover these texts and thus are never translated.

The correct way would be to separate the langauge related information and the rest on the WIKI page (e.g. like for MOTD).

comment:4 Changed 4 years ago by xeen

  • Owner changed from framm to xeen
  • Priority changed from major to minor

Will work on this.

comment:5 Changed 4 years ago by stoecker

Best would be a TRAC-Skript adding the plugin-versions to josm.openstreetmap.de/versions automatically.

E.g. add

  • filename
  • version
  • josm-version
  • author
  • description

from plugins.

Now we could add translations to the plugins and use the normal translation system like for presets.

The plugins page could then be generated automatically or reduced to link to these files which are not in SVN.

comment:6 Changed 4 years ago by stoecker

Added SVN stuff to version-file.

comment:7 Changed 4 years ago by stoecker

  • Owner changed from xeen to stoecker

Changed that a bit. Plugins now can be reached under
http://josm.openstreetmap.de/plugin

TODO:

  • Add Plugin-Link for a webpage link in MANIFEST
  • Add "lang.Plugin-Description" in Manifest, e.g. "de.Plugin-Description".
  • Update plugin descriptions
  • Parse non-svn plugins
  • Generate Trac support for plugins page allowing to generate a SVN-plugin [plugin:name] and external [plugin:url] and a template page {Template:Plugins:lang} which contains these sets. THe Plugin page and localized variants will then be auto-generated.

comment:8 Changed 4 years ago by stoecker

Done:

  • [ [ Plugins(en|name|author|description|version|More details) ] ] works for multiple languages
  • Plugin-Link introduced
  • all plugins parsed
  • localized forms introduced

Missing:

  • update build.xml's to include useful data
  • add descriptions to translations
  • add tr and localized support in JOSM
  • add Plugin-Link support in JOSM

comment:9 Changed 4 years ago by stoecker

  • Resolution set to fixed
  • Status changed from new to closed

Fixed in r1588.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed .
as The resolution will be set. Next status will be 'closed'.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.