Skip to content

Commit 863ca94

Browse files
committed
add Han feedback
1 parent 06f06b1 commit 863ca94

File tree

1 file changed

+50
-46
lines changed

1 file changed

+50
-46
lines changed

translations.mdx

Lines changed: 50 additions & 46 deletions
Original file line numberDiff line numberDiff line change
@@ -50,57 +50,61 @@ The ongoing translation process follows this sequence:
5050
3. The translation job updates, removes, or creates the required files in all subscribed languages based on your `docs.json` file.
5151
4. For each subscribed language, the translation job creates a separate branch and pull request containing the translated changes for your review
5252

53+
<Info>
5354
Mintlify will never automatically publish translations to production. You must review and merge each translation pull request before the changes are live.
55+
</Info>
5456

5557
The automatic translation job doesn't handle manual changes to the localized files or the `docs.json` navigation trees well. Make all changes in your English content and let the translation service manage the localized versions.
5658

5759
We recommend promptly reviewing and merging translation pull requests so that your localizations are kept in sync.
5860

5961
## Troubleshooting and FAQs
6062

61-
<Accordion title="What content is translated?">
62-
The translation service translates all non-code, non-component content in your documentation. This includes:
63-
64-
- Text
65-
- Links
66-
- Titles and descriptions in frontmatter
67-
- Component attributes
68-
- Navigation labels
69-
70-
The service does not translate:
71-
72-
- Code blocks
73-
- Images or other media
74-
- Metadata
75-
</Accordion>
76-
77-
<Accordion title="How do I update my translations manually?">
78-
If you need to modify your translations, make any changes directly in the translation pull requests created by the translation service.
79-
80-
Any manual changes may be overwritten the next time the English version of the page is updated and the translation job runs.
81-
</Accordion>
82-
83-
<Accordion title="Why isn't my translation working?">
84-
Check these common issues:
85-
- Verify that your translation subscription is active for the language.
86-
- Confirm that your content uses valid `MDX` formatting.
87-
- Confirm that your `docs.json` file is properly configured.
88-
89-
If you're still running into problems, please [contact support](mailto:[email protected]).
90-
</Accordion>
91-
92-
<Accordion title="Why do translation PRs sometimes include unchanged sections?">
93-
The translation system operates at the page level, and will attempt to translate entire pages when any portion changes.
94-
95-
This approach ensures that the translation is as accurate as possible and removes the need for manual updates to localized files.
96-
</Accordion>
97-
98-
<Accordion title="My desired language isn't available.">
99-
We offer translations for all languages supported by the [languages](/navigation#languages) feature.
100-
101-
If the language you'd like to translate to is not listed, please [contact support](mailto:[email protected]) and we'll be happy to assist.
102-
</Accordion>
103-
104-
<Accordion title="Can I define specific translations for words or prevent terms from being translated?">
105-
The translation service does not support custom translation rules for specific terms or phrases. We are developing this feature for a future release.
106-
</Accordion>
63+
<AccordionGroup>
64+
<Accordion title="What content is translated?">
65+
The translation service translates all non-code, non-component content in your documentation. This includes:
66+
67+
- Text
68+
- Links
69+
- Titles and descriptions in frontmatter
70+
- Component attributes
71+
- Navigation labels
72+
73+
The service does not translate:
74+
75+
- Code blocks
76+
- Images or other media
77+
- Metadata
78+
</Accordion>
79+
80+
<Accordion title="How do I update my translations manually?">
81+
If you need to modify your translations, make any changes directly in the translation pull requests created by the translation service.
82+
83+
Any manual changes may be overwritten the next time the English version of the page is updated and the translation job runs.
84+
</Accordion>
85+
86+
<Accordion title="Why isn't my translation working?">
87+
Check these common issues:
88+
- Verify that your translation subscription is active for the language.
89+
- Confirm that your content uses valid `MDX` formatting.
90+
- Confirm that your `docs.json` file is properly configured.
91+
92+
If you're still running into problems, please [contact support](mailto:[email protected]).
93+
</Accordion>
94+
95+
<Accordion title="Why do translation PRs sometimes include unchanged sections?">
96+
The translation system operates at the page level, and will attempt to translate entire pages when any portion changes.
97+
98+
This approach ensures that the translation is as accurate as possible and removes the need for manual updates to localized files.
99+
</Accordion>
100+
101+
<Accordion title="My desired language isn't available.">
102+
We offer translations for all languages supported by the [languages](/navigation#languages) feature.
103+
104+
If the language you'd like to translate to is not listed, please [contact support](mailto:[email protected]) and we'll be happy to assist.
105+
</Accordion>
106+
107+
<Accordion title="Can I define specific translations for words or prevent terms from being translated?">
108+
The translation service does not support custom translation rules for specific terms or phrases. We are developing this feature for a future release.
109+
</Accordion>
110+
</AccordionGroup>

0 commit comments

Comments
 (0)