choo121600 commented on issue #51123: URL: https://github.com/apache/airflow/issues/51123#issuecomment-2948230449
Thanks for the suggestion @potiuk ! I totally agree that `yaml` is more human-friendly and reduces the risk of syntax errors compared to `json`, especially when translators manually edit the files. Currently, the reason we use json is that i18next by default expects translation files in **json format** on the client side, and loading yaml directly in the browser would require bundling a yaml parser, which would increase the frontend bundle sizeㄷ something we want to avoid for performance reasons. To get the best of both worlds, I’m considering the following approach: - **Store and maintain translation files in yaml format on the backend** (making it easier for contributors to edit and review) - Serve the translations through an API endpoint that loads yaml files, **parses them on the server, and returns json responses** - Let the frontend continue to load translations as JSON via i18next’s standard HTTP backend without extra yaml parsing in the client This way, we keep the translation source files developer and contributor-friendly with yaml, while preserving frontend performance and compatibility with existing i18next tooling. Would love to hear your thoughts or concerns on this approach! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
