Not sure what I still missing here but related texts still appearing in English.
Is there any way to include the Spanish translation files to further versions? See attached the files (webapp contain the main translation file and is the one for the jdbc extensions)

2017-12-07 21:31 GMT+01:00 Mike Jumper <>:
For the translation strings of extensions, each JSON file containing translations needs to be declared within the guac-manifest.json.

In the case of guacamole-auth-jdbc, you'll need to modify the guac-manifest.json file of each extension which pulls in the common translations defined by guacamole-auth-jdbc-base:

* guacamole-auth-jdbc-mysql
* guacamole-auth-jdbc-postgresql
* guacamole-auth-jdbc-sqlserver

- Mike

On Dec 6, 2017 10:16, "David Rodriguez" <> wrote:
Thanks again Mike

I have created an es.json file inside the related folder and built the client again, however these texts still appearing in English. Do you know if there is any other place that need to me modified in order to automatic use the es.json if Spanish language is selected as display language in Guacamole?

2017-12-05 19:07 GMT+01:00 Mike Jumper <>:
On Tue, Dec 5, 2017 at 7:28 AM, David Rodriguez <> wrote:
I'm setting the Spanish translation file for Guacamole and it is almost completed, however there are some sections which doesn't appear in the English translation file. These are the below. Is there any place where I can get the english template, so I can translate it to Spanish and finish it?  Thanks




In this case, these fields are defined by the guacamole-auth-jdbc-* extensions, and the translation strings are within an "en.json" file defined in the "guacamole-auth-jdbc-base" project which contains the common basis for all database-specific implementations defined within guacamole-auth-jdbc:

There are additional translation strings defined by the CAS, Duo, and Open ID extensions, as well, though not quite as extensive as the above.

- Mike