You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Leonard Wagner (Jira)" <ji...@apache.org> on 2023/06/01 22:22:00 UTC

[jira] [Updated] (GUACAMOLE-1799) Include Name and Version in all translation files

     [ https://issues.apache.org/jira/browse/GUACAMOLE-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leonard Wagner updated GUACAMOLE-1799:
--------------------------------------
    Description: 
Only the English and Polish translation files contain the APP.NAME and APP.VERSION properties. The values of these properties are used by the login page for example.

Currently this does not seem to be a problem because the English translation file is _somehow_ always loaded before the translation file of the language that the user requested.

To not have to rely on this behavior and to prepare things for the Angular frontend I would like to include these properties in all translation files.

  was:
Only the English and Polish translation files contain the APP.NAME and APP.VERSION properties. The values of these properties are by the login page for example.

Currently this does not seem to be a problem because the English translation file is _somehow_ always loaded before the translation file of the language that the user requested.

To not have to rely on this behavior and to prepare things for the Angular frontend I would like to include these properties in all translation files.


> Include Name and Version in all translation files
> -------------------------------------------------
>
>                 Key: GUACAMOLE-1799
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1799
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole
>            Reporter: Leonard Wagner
>            Priority: Trivial
>
> Only the English and Polish translation files contain the APP.NAME and APP.VERSION properties. The values of these properties are used by the login page for example.
> Currently this does not seem to be a problem because the English translation file is _somehow_ always loaded before the translation file of the language that the user requested.
> To not have to rely on this behavior and to prepare things for the Angular frontend I would like to include these properties in all translation files.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)