Bug 4792 - translate Web Access
Summary: translate Web Access
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Web Access (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Samuel Mannehed
URL:
Keywords: relnotes, upstream
Depends on:
Blocks:
 
Reported: 2013-09-04 14:53 CEST by Pierre Ossman
Modified: 2017-04-11 14:41 CEST (History)
0 users

See Also:
Acceptance Criteria:


Attachments

Description Pierre Ossman cendio 2013-09-04 14:53:11 CEST
It is a user visible interface so it should be translated.
Comment 1 Samuel Mannehed cendio 2016-10-28 20:19:48 CEST
Basic and incomplete translations have been included in upstream noVNC. Currently translations exists for the most common status messages visible in the user interface. Languages that are added except for English so far are German, Dutch, Greek and Swedish.
Comment 2 Samuel Mannehed cendio 2017-01-10 12:43:02 CET
A more complete solution with translations of the HTML as well, exist in upstream noVNC now. See https://github.com/novnc/noVNC/pull/718
Comment 3 Samuel Mannehed cendio 2017-01-10 12:44:45 CET
Note that the upstream solution currently does not support format strings yet. We might want to, for example be able to give a file like this to Spanish translators:

> msgid "white"
> msgstr ""
>
> msgid "The %s house"
> msgstr ""

We would want the translation:

> msgid "white"
> msgstr "Blanca"
>
> msgid "The %s house"
> msgstr "La casa %s"

To get the end result:

> "La casa Blanca"

Currently we can not use the format notation:

> msgid "The"
> msgstr "La"
>
> msgid "white"
> msgstr "Blanca"
>
> msgid "house"
> msgstr "casa"

We would, with the current solution, along with loosing good context also get a grammatically incorrect translation:

> "La Blanca casa"

Note You need to log in before you can comment on or make changes to this bug.