-
Notifications
You must be signed in to change notification settings - Fork 6.2k
try to use deepseek with an agent to auto i18n to zh #12032
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: SamYuan1990 <yy19902439@126.com>
Signed-off-by: SamYuan1990 <yy19902439@126.com>
Signed-off-by: SamYuan1990 <yy19902439@126.com>
Signed-off-by: SamYuan1990 <yy19902439@126.com>
Thanks! I don't have an issue with an AI translation, but if you don't mind, can you also read and verify the accuracy of the translation to make sure it makes sense please 🤗 A few other things of note:
|
Hi @stevhliu , may I know where can I find all doc-builder syntax? and sure after go through the docs with a basic check I will make this PR ready for review. |
I hope I am right as I can use and ... it seems |
Signed-off-by: SamYuan1990 <yy19902439@126.com>
Hi @stevhliu , I go through the docs with vs code, and... BTW, I followed instruct as https://github.com/huggingface/diffusers/blob/main/docs/README.md#generating-the-documentation and...
and btw, for doc-builder , I meet error as I have to install pytorch?
|
You can find the syntax on the doc-builder repo. For example,
Yeah, looks like you may be missing PyTorch in your env. Can you try installing it and re-running the command? |
Hi @stevhliu do we have a glossary? but not rules one by one... the rules one by one requires new joiner as me having knowledge base as markdown, html, Framework Content? LaTeX? see LaTeX and markdown is language, and seems tips and others are glossary. here are my reproduce steps:
and yes...
|
@stevhliu in function resolve_links_in_text it will dynamic load a python code which needs .... but it breaks in the middle when dynamic compile
with function |
@stevhliu additional information.
as a document parts, why do we need dynamic library checking? |
@stevhliu , I opened another issue for how to compile the build. as huggingface/doc-builder#613 I traced code try to run container version, but... huggingface/doc-builder#614 which seems the container is not been used in document build. (sad face) |
I tried today... but no further progress. @stevhliu , waiting for your feedback and further comments. |
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
There's not a glossary, but feel free to open a PR to turn it into one if that helps! As for the other issues, I'm not exactly sure what the problem is 😅 . But you can preview the docs here |
The reason is |
and @stevhliu , what make the thing worse. as I can't access moon-ci-docs.huggingface.co due to GFW, so I have to relay on local preview to check the content. Lucky in PR build, I can have the html content. ![]() I tried my best to compile it on my local but ... it doesn't work. I found one issue and I fixed in today's PR. |
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.
But... here we can see with example as [~ModelMixin.compile_repeated_blocks] this tag, the compile logic is no same between zh and en version and I don't know why.
It's because the API docs for compile_repeated_blocks
doesn't exist in the Chinese version it just gets rendered in plain code format instead of a link to the API docs as in the English version.
The docs LGTM structurally. One thing to note is can you align the toctree
with the English one? I also can't review the translated content since I don't read Chinese. If they look good to you, then I'm happy to merge!
Signed-off-by: SamYuan1990 <yy19902439@126.com>
I just make a fix to adjust |
What does this PR do?
Fixes # (issue)
Support some document i18n with DeepSeek in an agent.
Before submitting
This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
yep.
Did you read the contributor guideline?
I don't have access to discord, so I contracted someone offline for this attempt.
Did you read our philosophy doc (important for complex PRs)?
Was this discussed/approved via a GitHub issue or the forum? Please add a link to it if that's the case.
Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
Did you write any new necessary tests?
n/A?
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.