The goal of this project is to provide examples of how we can integrate i18n with Vaadin Flow quickly and easily, without any additional configuration.

In this demonstration, you can observe how we can switch between 4 languages: English, Spanish, Finnish, and French. The translations to Finnish and French have been made possible thanks to ChatGPT. This project illustrates the ease with which we can integrate multiple languages using Vaadin Flow, highlighting the functionality of dynamic language switching without the need for additional configurations.

Before proceeding, it is recommended to read the documentation and understand how i18n works in Vaadin. In this implementation, we are using the LocaleChangeObserver observer to receive events related to language changes. This approach allows us to dynamically manage language settings and adapt the user interface according to user preferences.

To use localization and translation strings, the application needs only to have the translation properties available on the classpath under the directory, vaadin-i18n with the filename prefix, translations. e.g.,

• src/main/resources/vaadin-i18n/translations.properties
• src/main/resources/vaadin-i18n/translations_es.properties
• src/main/resources/vaadin-i18n/translations_fi.properties
• src/main/resources/vaadin-i18n/translations_fr.properties

The file translations.properties is a default translation file that’ll be used for any Locale that doesn’t have a specific translations file.

The project is a standard Maven project. To run it from the command line, tab mvnw (Windows), or ./mvnw (Mac & Linux), then open http://localhost:37186 in your browser.

The 'defaultGoal' is configured in the pom file.

# Mac & Linux
./mvnw

# Windows
  mvnw

To create a production build, call

# Mac & Linux
./mvnw clean package -Pproduction

To create a production build, call

# Windows
mvnw clean package -Pproduction

This will build a JAR file with all the dependencies and front-end resources, ready to be deployed. The file can be found in the target folder after the build completes.

Once the JAR file is built, you can run it using

java -jar target/i18n.jar 

To build the Dockerized version of the project, run

# Mac & Linux
./mvnw clean package -Pproduction

# Windows
mvnw clean package -Pproduction

docker build . -t vaadin-i18n-app:latest

Once the Docker image is correctly built, you can test it locally using

docker run -p 37186:37186 vaadin-i18n-app:latest

• MainLayout.java in src/main/java contains the navigation setup (i.e., the side/top bar and the main menu). This setup uses App Layout.
• views package in src/main/java contains the server-side Java views of your application.
• views folder in frontend/ contains the client-side JavaScript views of your application.
• themes folder in frontend/ contains the custom CSS styles.

• Read the documentation at vaadin.com/docs.
• Follow the tutorial at vaadin.com/docs/latest/tutorial/overview.
• Create new projects at start.vaadin.com.
• Search UI components and their usage examples at vaadin.com/docs/latest/components.
• View use case applications that demonstrate Vaadin capabilities at vaadin.com/examples-and-demos.
• Build any UI without custom CSS by discovering Vaadin's set of CSS utility classes.
• Find a collection of solutions to common use cases at cookbook.vaadin.com.
• Find add-ons at vaadin.com/directory.
• Ask questions on Stack Overflow or join our Discord channel.
• Report issues, create pull requests in GitHub.