-
Notifications
You must be signed in to change notification settings - Fork 29
feat(i18n): Initial multilingual support implementation #123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Shrutim1505
wants to merge
2
commits into
eclipse-sw360:main
Choose a base branch
from
Shrutim1505:multilingual-support
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,69 @@ | ||
| +++ | ||
| title = "SW360" | ||
| linkTitle = "Eclipse SW360" | ||
| +++ | ||
|
|
||
| {{<blocks/cover image_anchor="center" height="full">}} | ||
| <div class="row align-items-center"> | ||
| <div class="col-lg-6"> | ||
| <h4> | ||
| {{< figure src="/sw360/img/logos/logo_full.svg" width="400">}} | ||
| <p class="display-2 mb-0"> | ||
| Software supply chain management done right ! | ||
| </p> | ||
| </h4> | ||
| </div> | ||
| <div class="col-lg-6 mt-5 mt-lg-3 d-sm-block" style="display: none"> | ||
| {{< figure src="/sw360/img/sw360screenshots/sw360screenshot-home.png" | ||
| width="500" >}} | ||
| </div> | ||
| </div> | ||
|
|
||
| <div class="display-cover mt-5"> | ||
| <p> | ||
| SW360 is an open source software project licensed under the EPL-2.0 that | ||
| provides both a web application and a repository to collect, organize and | ||
| make available information about software components. It establishes a | ||
| central hub for software components in an organization. | ||
| </p> | ||
| </div> | ||
|
|
||
| <div class="mx-auto mt-5"> | ||
| <a class="btn btn-lg btn-primary mr-3 mb-4" href="#vision-section"> | ||
| <span style="font-size: larger; font-weight: bolder;">Our Vision</span> | ||
| </a> | ||
| </div> | ||
|
|
||
| {{</blocks/cover>}} | ||
|
|
||
|
|
||
| <a id="vision-section" class="td-offset-anchor"></a> | ||
| <section class="row td-box td-box--secondary td-box--gradient td-box--height-auto"> | ||
| <div class="col"> | ||
| <div class="row"> | ||
| {{% blocks/vision title="Central SW Component Database" %}} | ||
| 360 degree coverage for SW development beside the ‚Coding‘ as the Central SW | ||
| component database | ||
| {{% /blocks/vision %}} | ||
|
|
||
| {{% blocks/vision title="E2E Integration for Software Compliance" %}} | ||
| Having a stable, precise, transparent, controllable and easy extendable OSS toolchain for | ||
| long term running | ||
| {{% /blocks/vision %}} | ||
|
|
||
| </div> | ||
| <div class="row"> | ||
| {{% blocks/vision title="Long Term Controlled OSS Toolchain" %}} | ||
| As automated | ||
| as possible, end-to-end compliance (Legal, Security/SBOM, Export Control) | ||
| tool-chain, seamlessly integrated in the SW development process (e.g. | ||
| DevOps) | ||
| {{% /blocks/vision %}} | ||
|
|
||
| {{% blocks/vision title="Embracing New Technologies" %}} | ||
| Enable easy onboarding of | ||
| new technolgies and new tools (e.g. container, new kind of packages) | ||
| {{% /blocks/vision %}} | ||
| </div> | ||
| </div> | ||
| </section> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,40 @@ | ||
| --- | ||
| title: "À propos d'Eclipse SW360" | ||
| linkTitle: À propos | ||
| menu: | ||
| main: | ||
| weight: 10 | ||
|
|
||
| --- | ||
|
|
||
| {{< blocks/cover image_anchor="top" height="sm" color="primary" >}} | ||
| {{< page/header >}} | ||
| {{< /blocks/cover >}} | ||
|
|
||
| <div class="container l-container--padded"> | ||
|
|
||
|
|
||
| <div class="row"> | ||
| <div class="col-12 col-lg-8"> | ||
|
|
||
| Aujourd'hui, dans la plupart des cas, les logiciels ne sont pas créés à partir de zéro, mais plutôt assemblés à partir de divers composants logiciels tiers préemballés. Par conséquent, les organisations sont confrontées aux défis suivants : | ||
|
|
||
| * Vérifier différents aspects de la conformité lors de l'utilisation de composants logiciels tiers : conformité des licences, contrôles ECC, évaluations de propriété intellectuelle, etc. | ||
| * Partager les connaissances sur les composants logiciels et leurs qualités. Par exemple, quels composants logiciels devraient être recommandés, lesquels devraient être abandonnés selon quels critères ? | ||
| * Fournir une vue d'ensemble des composants utilisés : une organisation et sa gestion de la chaîne d'approvisionnement doivent disposer d'informations sur les actifs intégrés dans quels produits ou solutions. | ||
|
|
||
| Ces trois cas d'utilisation principaux ciblent différents rôles dans une organisation : responsables qualité, développeurs de logiciels, conseillers juridiques, architectes logiciels, responsables R&D, etc. Cependant, tous ces cas d'utilisation partagent un besoin commun d'un hub central qui gère les informations sur les composants logiciels. | ||
|
|
||
| SW360 est un projet logiciel open source sous licence EPL-2.0 qui fournit à la fois une application web et un référentiel pour collecter, organiser et rendre disponibles les informations sur les composants logiciels. Il établit un hub central pour les composants logiciels dans une organisation. SW360 permet de : | ||
|
|
||
| * suivre les composants utilisés par un projet/produit, | ||
| * évaluer les vulnérabilités de sécurité, | ||
| * maintenir les obligations de licence, | ||
| * appliquer des politiques, et | ||
| * générer des documents juridiques. | ||
|
|
||
| Par exemple, SW360 peut déclencher un processus de vérification dans l'outil de conformité open source FOSSology et importer le rapport de vérification résultant. Les données sont soit stockées dans la base de données de SW360, soit importées à la volée depuis des sources externes. À l'avenir, nous prévoyons d'avoir des fédérations d'instances SW360 qui partagent des informations sélectionnées. Outre son interface utilisateur web, toutes les fonctionnalités de SW360 sont disponibles via une API qui permet une intégration dans les outils devops existants. | ||
| </div> | ||
|
|
||
| </div> | ||
| </div> |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
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.