docs(ar): add Arabic translation for documentation pages#8252
docs(ar): add Arabic translation for documentation pages#8252RlxChap2 wants to merge 37 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
One or more co-authors of this pull request were not found. You must specify co-authors in commit message trailer via: Supported
Alternatively, if the co-author should not be included, remove the Please update your commit message(s) by doing |
|
👋 Hi there! This PR was automatically flagged and closed by our quality checks. If you believe this was a mistake, please review our contributing guidelines |
|
👋 Hi there! This PR was automatically flagged and closed by our quality checks. If you believe this was a mistake, please review our contributing guidelines |
|
@RlxChap2 reopen, looks like our check is a little bit aggressive |
|
👋 Hi there! This PR was automatically flagged and closed by our quality checks. If you believe this was a mistake, please review our contributing guidelines |
|
Also let's rebase |
|
/cc @avivkeller How to say to our bot don't close after reopen? |
|
👋 Hi there! This PR was automatically flagged and closed by our quality checks. If you believe this was a mistake, please review our contributing guidelines |
oh i see, so what is the solution rn ? |
yeah i did a rebase in the another pr #8253 |
This comment has been minimized.
This comment has been minimized.
The ‘exempt’ label, which we can customize to a different name if needed |
|
@RlxChap2 can you rebase? |
|
For reference, this PR was blocked because several files did not end in a newline AND a commit exceeded 500 characters. Fixing one of those in future PRs will prevent a block |
yeah sure lemme try to fix those |
Translate initial blog and configuration index content to Arabic while preserving MDX structure. Co-authored-by: ameencfw <ameencfw@users.noreply.github.com> Co-authored-by: Shimizu Hiroyuki <amtixdev@gmail.com>
|
finally i fixed all of them is it good rn ? @alexander-akait |
…main files to arabic
|
used ai to help me in the issues that appears from the checks and this is what did ai changed at - "lint:markdown": "markdownlint --config ./.markdownlint.json --rules ./src/utilities/markdown-lint-enforce-lang-aliases.js \"**/*.{md,mdx}\"",
+ "lint:markdown": "markdownlint --config ./.markdownlint.json --rules ./src/utilities/markdown-lint-enforce-lang-aliases.js --ignore \"src/content/**/printable.mdx\" --ignore \"src/content/**/_*.mdx\" --ignore \"src/content/contribute/Governance-*.mdx\" \"**/*.{md,mdx}\"",
also i prefer this PR to be in a separate branch to avoid causing any issues to the main project |
|
Hello @alexander-akait last things we need to do are change the button layout issue and translate the main page, after these changes this PR will be done for all translations |
7 participants
Summary
this is in progress PR for the Arabic translation of webpack.js.org documentation, also this PR is opened to make it easier to keep the translation branch up to date with upstream changes and resolve merge conflicts as they appear this Translation work is still ongoing
What kind of change does this PR introduce?
docs
Did you add tests for your changes?
no this is a documentation/translation-only change, also ig we will change the translation in the codes:
example:
Print Pagewe will change it from the code to Arabic and it will be like:طباعة الصفحةDoes this PR introduce a breaking change?
Maybe, because we changed the layout from ltr to rtl
If relevant, what needs to be documented once your changes are merged or what have you already documented?
translated documentation is included in this PR More translated pages will be be added
Use of AI
used ai to help me in the issues that appears from the checks
and this is what did ai changed at
package.json:also i prefer this PR to be in a separate branch to avoid causing any issues to the main project