Skip to content

feat(i18n): Initial multilingual support implementation#123

Open
Shrutim1505 wants to merge 2 commits intoeclipse-sw360:mainfrom
Shrutim1505:multilingual-support
Open

feat(i18n): Initial multilingual support implementation#123
Shrutim1505 wants to merge 2 commits intoeclipse-sw360:mainfrom
Shrutim1505:multilingual-support

Conversation

@Shrutim1505
Copy link
Contributor

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.

@Shrutim1505 Shrutim1505 force-pushed the multilingual-support branch from 8005c81 to 03a3d4b Compare March 30, 2025 10:19
Signed-off-by: Shruti78 <[email protected]>

feat(i18n): add multilingual support

Signed-off-by: Shruti78 <[email protected]>
@Shrutim1505 Shrutim1505 force-pushed the multilingual-support branch from 03a3d4b to 921e2cb Compare March 30, 2025 10:21
@Shrutim1505
Copy link
Contributor Author

Shrutim1505 commented Mar 30, 2025

image
a short preview for convertiong english language to french , can u please approve this so I could start changing all the files @GMishx @heliocastro @KoukiHama

@KoukiHama
Copy link
Member

Good, we will check this PR.

@KoukiHama KoukiHama requested review from EttingerK, arunazhakesan and heliocastro and removed request for maxhbr March 30, 2025 14:04
@Shrutim1505
Copy link
Contributor Author

@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.

@KoukiHama
Copy link
Member

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.

@KoukiHama
Copy link
Member

To clarify the purpose of the PR, please separate the spelling correction commit from the i18n commit.

@KoukiHama
Copy link
Member

@GMishx @heliocastro
I'd also like to hear your thoughts on this: Since it's quite a large task to translate everything at once, do you think we should merge partially translated pages (with some English content still remaining), or wait until the French translation is fully complete before merging?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants