Open Eric-Arellano opened 5 months ago
@ilyaspiridonov (ilyaspiridonov) sent the following message over slack
Hi all, upon looking at those errors with our dev team, here are the issues we have identified:
- The JA folder seems to contain English files that we did not translate. I don’t believe they are supposed to be there. Here’s an example https://github.com/Qiskit/documentation/blob/main/translations/ja/api/migration-guides/qiskit-algorithms-module.mdx
- Those English files contain certain issues that were likely introduced after copying (do you have some sort of processor?). Example from the above file:
**[Legacy]\:**
while in the En source this string looks like this**[Legacy] Using QuantumInstance:**
- The files we have translated seem to have common issues introduced by Crowdin, which is escaping that makes the the formula parser go crazy:
\\
instead of:\
- Another issue presumably introduced by crowdin is the extra Tab characters before the closing tags like here:
<Admonition type="tip" title="Recommendations">
- Learn how to generate OpenQASM code in the Explore gates and circuits with the Quantum Composer tutorial.
- Review the OpenQASM 3 feature table.
- Read the OpenQASM 3 Qiskit API reference.
- Read the OpenQASM 2 Qiskit API reference.
- Visit the OpenQASM Live Specification.
Perhaps you also downloaded the untranslated files from Crowdin (English)? Which may explain why there are English files in the JA folder, and why they are also broken.
We’ve fixed those issues in the files we translated, here’s the package: fixed-translations.zip
You may want to remove the other English files from the JA directory and talk to Crowdin about fixging those issues (escaping and closing html tags being not on the same level as the open tags (extra tabulation)
Found by
npm run check-pages-render -- --translations
on Jan 24:To check that they render, run
./start
locally then go to e.g.localhost:3000/ja/build/bit-ordering
.