Let's break down the task of adding translation support for product descriptions and metadata. This involves several steps, including setting up translation files, integrating them into your product model, and displaying them in the UI. ### Step 1: Create Translation Files for Products We'll store product translations in JSON files, similar to how we handle locale messages. Create a new folder structure under `src/main/resources/translations/products/` with tenant-specific files: ```json // src/main/resources/translations/products/en_US.json { "product.description": "This is a high-quality product description in English", "product.title": "Premium Product", "product.specifications": { "weight": "Weight: {0} kg", "dimensions": "Dimensions: {0} x {1} x {2} cm" } } ``` ### Step 2: Create a Tenant-Specific Translation Service We'll create a service to load and manage tenant-specific translations: ```java @Service public class ProductTranslationService { private final String TRANSLATIONS_PATH = "translations/products/%s.json"; @Autowired private TenantService tenantService; public Map getTranslations(String language) { String tenantId = tenantService.getCurrentTenantId(); String filePath = String.format(TRANSLATIONS_PATH, language); try { Resource resource = new ClassPathResource(filePath); Map translations = new HashMap<>(); if (resource.exists()) { Map map = new ObjectMapper() .readValue(resource.getInputStream(), new TypeReference>() {}); map.forEach((key, value) -> { if (value instanceof String) { translations.put(key, (String) value); } }); } return translations; } catch (IOException e) { return new HashMap<>(); } } public void addTranslation(String key, String value, String language) { // Implementation to add new translations } public void updateTranslation(String key, String value, String language) { // Implementation to update existing translations } } ``` ### Step 3: Integrate Translations into Product Details Modify your product model to include translated descriptions: ```java public class Product { private String id; private String descriptionKey; private Map translatedDescriptions; public String getDescription() { return translatedDescriptions.get("product.description"); } public String getTitle() { return translatedDescriptions.get("product.title"); } // Getters and setters } ``` ### Step 4: Use Translations in Your Controller Update your product controller to fetch and apply translations: ```java @Controller public class ProductController { @Autowired private ProductService productService; @Autowired private ProductTranslationService translationService; @GetMapping("/product/{id}") public String getProduct(@PathVariable String id, Model model) { Product product = productService.findById(id); Locale locale = LocaleContextHolder.getLocale(); Map translations = translationService.getTranslations(locale.getLanguage()); product.setTranslatedDescriptions(translations); model.addAttribute("product", product); return "product/details"; } @ModelAttribute("currentLocale") public String currentLocale() { return LocaleContextHolder.getLocale().getLanguage(); } } ``` ### Step 5: Display Translated Content in Thymeleaf Update your product details template to use translated values: ```html Product Details

Product Title

Product Description

``` ### Step 6: Add Language Switcher to Product Page Include a language switcher in your product template: ```html

``` ### Step 7: Best Practices 1. **Use UTF-8 Encoding**: Ensure all translation files are encoded in UTF-8 to support special characters. 2. **Fallback Mechanism**: Provide fallback translations for keys that might not exist in specific language files. 3. **Testing**: Test translations thoroughly for all supported languages. 4. **Organized Structure**: Maintain a consistent folder structure for translation files. 5. **Version Control**: Use version control to track changes in translation files. ### Step 8: Next Steps 1. **Add More Languages**: Continue adding support for more languages as needed. 2. **Enhance UI**: Improve the user interface to make language switching more intuitive. 3. **Document Translations**: Document your translation conventions for future developers. 4. **Automated Testing**: Implement automated tests for translation rendering. ### Step 9: Further Reading - [Spring Boot Internationalization Guide](https://docs.spring.io/spring-boot/docs/current/reference/html/features.html#features.internationalization) - [Thymeleaf Documentation](https://www.thymeleaf.org/documentation.html) - [Java Locale Documentation](https://docs.oracle.com/javase/8/docs/api/java/util/Locale.html) - [NumberFormat API Documentation](https://docs.oracle.com/javase/8/docs/api/java/text/NumberFormat.html)