gvSIG bugs #2653
Development menu options are not translatable
| Status: | Closed | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | Normal | Spent time: | - | |
| Assignee: |  José Badía | |||
| Category: | Developer tools | |||
| Target version: | 2.2.0-2303 (rev. org.gvsig.desktop-2.0.90) | |||
| Severity: | Minor | Add-on version: | ||
| gvSIG version: | 2.1.0 | Add-on build: | ||
| gvSIG build: | 2233 | Add-on resolve version: | ||
| Operative System: | Add-on resolve build: | |||
| Keywords: | translations, i18n | Proyecto: | ||
| Has patch: | Hito: | |||
| Add-on name: | Unknown |
Related issues
Associated revisions
refs #2653
Development menu options are not translatable
refs #2653
Development menu options are not translatable
refs #2653
Development menu options are not translatable
History
#1
Updated by Álvaro Anguix almost 10 years ago
- Assignee set to Mario Carrera
#2
Updated by Antonio Falciano over 9 years ago
The Tools > Development menu options, together with those of Scripting extension (see #2651), are not translatable yet in build 2265. I think that is should be possible before the release of final gvSIG 2.1, in order to complete the translation of menus at least.
#3
Updated by Álvaro Anguix over 9 years ago
- Category set to Developer tools
#4
Updated by Álvaro Anguix about 9 years ago
- Related to gvSIG bugs #2651: Scripting extension is not translatable added
#5
Updated by Álvaro Anguix about 9 years ago
- Target version set to 2.2.0-2311-rc2
- Assignee changed from Mario Carrera to José Badía
#6
Updated by José Badía about 9 years ago
- Status changed from New to Fixed
#7
Updated by Joaquín del Cerro Murciano about 9 years ago
- Target version changed from 2.2.0-2311-rc2 to 2.2.0-2303 (rev. org.gvsig.desktop-2.0.90)
#8
Updated by Álvaro Anguix about 9 years ago
- Status changed from Fixed to Closed