Skip to content
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

Manual Translators Please Subscribe to this Issue #182

Open
baconpaul opened this issue Apr 15, 2021 · 5 comments
Open

Manual Translators Please Subscribe to this Issue #182

baconpaul opened this issue Apr 15, 2021 · 5 comments
Labels
Help Wanted Extra attention is needed

Comments

@baconpaul
Copy link
Contributor

Hi!

First, thanks for kindly translating the manual. If you are a manual translator please subscribe to this GitHub issue and we will use it (plus the #documentation channel in discord) to notify folks if there are big changes or so on.

Best practices for a manual translation are

  1. Please call it Surge-XX.md where XX is the standard 2 letter code for your language (DE, FR, JP, etc...)
  2. Please make the permalink manual-XX
  3. If possible, put near the top of your manual that "this manual was translated as of ..." - but we are still working on that
  4. Please ask on this issue and we will link to the translated manual from the top of the english manual

In SurgeXT we may be able to internationalize more fully - things like link to a german manual from the menu if your computer has a german language region. If so we may occasionally hit up this issue for some testing or changes there too.

And finally, thanks for working to translate the manual!

Pre-tagging @mkruselj @VincyZed @mynameismuhl

@ghost
Copy link

ghost commented Apr 15, 2021

In addition to what Paul wrote above, here are some things i learned to be helpful for myself.
Maybe some of it is also helpful for others:

  • By all means, use a translate program/web translator for your first draft to make starting less painful,
    but remember: humans write words wrong, bots write wrong words.
  • For tech terms you don't know an appropriate translation for,
    looking for it in English Wikipedia and then toggle the language can sometimes give a better result,
    since these articles are not auto-translated.
  • Make decisions what not to translate early in the process.
  • Making sure to keep the same line numbering as the original speeds up later changes a lot.

@ManabuMiwa
Copy link

ManabuMiwa commented Dec 11, 2022

Hi all!

I'm working on Japanese translation.
I guess it will take for a while because size of the contents is huge though, I'll make a PR when I'm ready.

Please point out if I'm doing something wrong.

Screenshot 2022-12-11 at 10 55 31 AM

Edit: Fix a broken link (Mar 18, 2023)
Sorry for delaying my work.

@mthierman Thanks for streamlining TOC/dropdown code!❤️

@baconpaul
Copy link
Contributor Author

Oh that's super cool!

@VincyZed
Copy link
Collaborator

@ManabuMiwa Awesome! Let us know if you have any questions. 🙂

@surge-synthesizer surge-synthesizer deleted a comment Jan 31, 2023
@surge-synthesizer surge-synthesizer deleted a comment Jan 31, 2023
@surge-synthesizer surge-synthesizer deleted a comment Jan 31, 2023
@mthierman
Copy link
Collaborator

So we had removed the german manual link from the website, but the markdown was never removed. I have fixed the frontmatter/image links to get Astro building a page for it again at the old link.

I think we agreed to remove it, as these things go unmaintained and fall out of date. But I will keep it alive as an archive, same as Surge 1.9 english manual.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Help Wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

5 participants