Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Add your comments directly to the page. Include links to any relevant research, data, or feedback.

Status

NOT STARTED

Impact

HIGH

Driver

Alessandro Domanico 

Approver

Stakeholders

Niccolò Pasquetto Henrique de Almeida Riccardo Costa

Informed

Due date

Outcome

Star

Background

At the moment the Swing GUI translations are provided as .properties and .csv files in the project’s bundle/ subfolder. These files are also hosted on Transifex platform for the community contribution. Thanks to the GitHub-Transifex integration, new strings are automatically uploaded to Transifex and 100% translations are pushed back to GitHub (via PullRequest).

The aim is of course to recycle, if possible, the actual transaltions.

Relevant data

  • .properties files are used by the GUI

  • .csv files are used by the SQL scripts for the initial DB setup

  • .csv are hosted as .xlsx in Transifex and their management is manual at the moment (no GitHub-Transifex integration)

Options considered

Option 1:

Option 2:

Description

Separated Translation files between “gui” and “ui”

Same translation files

Pros and cons

(plus) possibility to adopt different and more reliable translations formats

(plus) It’s a Standard

(minus) double maintainance until “gui” will be still included in the release packages

(minus) more resources on Transifex

(plus) Same translations files for both “gui” and “ui”

(plus) Only one set of resources on Transifex

(minus) Transifex can handle automatically only one repository (Pull Requests), so updating both components will require manual work or more advanced release scripts

Estimated cost

LARGE

MEDIUM

Action items

  • To define the localization pattern for the “ui” component

Outcome

  • No labels

Open Hospital powered by ISF
2005 - 2016 ISF © Informatici senza frontiere - ONLUS