feat(i18n): Initial multilingual support implementation#123
feat(i18n): Initial multilingual support implementation#123Shrutim1505 wants to merge 2 commits intoeclipse-sw360:mainfrom
Conversation
8005c81 to
03a3d4b
Compare
Signed-off-by: Shruti78 <[email protected]> feat(i18n): add multilingual support Signed-off-by: Shruti78 <[email protected]>
03a3d4b to
921e2cb
Compare
|
|
|
Good, we will check this PR. |
Signed-off-by: Shruti78 <[email protected]>
|
@KoukiHama @GMishx Multilingual support is now complete, and the next step I would document each and every page of the website in different languages(as suggested) to ensure comprehensive localization. |
|
Generally fine, but I don't understand French, so I'll let the AI review the French part; if the AI's review results are not worthwhile, ignore them and move on. |
|
To clarify the purpose of the PR, please separate the spelling correction commit from the i18n commit. |
|
@GMishx @heliocastro |
There was a problem hiding this comment.
Based on multiple AI-assisted reviews of the French translation, I would like to share the following comments.
If you find these suggestions reasonable, please go ahead and apply the necessary corrections.
As mentioned earlier, I do not have knowledge of French myself.
🔍 Suggested Edits
Terminology Consistency:
If terms like “logiciel libre” and “open source” are used interchangeably, it would be helpful to clarify how each term is used within the project. This will make it easier for readers to understand.
Use of Polite Language:
If the target audience includes general users, using polite expressions (e.g., “Veuillez consulter...”) can help make the tone more approachable and user-friendly.
Grammar and Syntax Check:
Some sentences may need attention to subject-verb agreement or proper use of prepositions. For example, ensure correct structures such as “Les utilisateurs peuvent accéder à leurs données.”
Translation Consistency:
If the same terms or phrases are translated differently in various parts of the document, try to maintain consistency throughout.

Description
This PR introduces the foundation for multilingual support by:
Adding basic language-specific content for English (content/en/) and French (content/fr/).
Implementing a language switcher in the navbar for easy language selection
Request for Feedback
Before proceeding with full content translation, I’d like to confirm:
✅ Does this approach align with the project's requirements?
✅ Is the current structure (content/en/ and content/fr/) the preferred format?
✅ Any suggestions for improving the implementation before scaling it further?
Next Steps (if approved)
Translate more sections and pages.
Ensure a proper fallback mechanism for untranslated content.
Add support for more variety languages if needed.