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

[i18n] Make user documentation localizable #1298

Open
FitikWasTaken opened this issue Sep 1, 2024 · 3 comments
Open

[i18n] Make user documentation localizable #1298

FitikWasTaken opened this issue Sep 1, 2024 · 3 comments
Labels
feature Features and feature requests that are specific to Bridgy Fed, not fully described by the protocols.

Comments

@FitikWasTaken
Copy link

Both the Fediverse and the BlueSky has a big share of non-English speaking users

Fediverse has a big amount of non-English users (second and third biggest mastodon instances are Japanese speaking) and the BlueSky has a big amount of non-English users as well

I think it would be very nice if fed.brid.gy and fed.brid.gy /docs could be translated, as it would answer questions non-English users might have too

Ideally it could be translatable on a service like Crowdin/Weblate/Transifex etc

@snarfed
Copy link
Owner

snarfed commented Sep 2, 2024

This is a great idea! I'd love to have the docs and front page localized. Thanks for the suggestion, and for the translation service ideas!

It's not my highest priority right now, but it could be a great project for another contributor to work on, especially someone familiar with the workflow for those translation services.

In the meantime, @FitikWasTaken do you speak Japanese or Portuguese or another language popular on Bluesky or the fediverse right now? Any idea how good Google Translate is with the docs, eg https://fed-brid-gy.translate.goog/docs?_x_tr_sl=auto&_x_tr_tl=pt&_x_tr_hl=en&_x_tr_pto=wapp ?

@FitikWasTaken
Copy link
Author

FitikWasTaken commented Sep 3, 2024

I don't speak neither of these languages sadly, I speak 3 other languages (Russian, Hebrew and Esperanto), but all of these languages are currently unsupported on BlueSky, even if they have small communities on Fedi/Bsky.

I checked how good automatic translation for Russian and it's uhh okay, it's understandable/intelligible, at least for me, but it's not perfect, it's not very grammatically correct, structured weirdly and uses some weird terms that aren't used on Fedi/BlueSky.

For example it have translated "mutes" in the context of blocks as "turning off audio" and various small mistakes like that. It also translates "follows" literally, like "stalks" and that sounds kinda creepy.

You can have built in auto translator if you don't want to deal with it, I seen websites that use it, also technically then you'll be supporting all languages google translate supports (Like 300 of them). It's obviously worse for smaller languages(Like Hebrew) as they have smaller text corpus.

@qazmlp
Copy link

qazmlp commented Sep 3, 2024

Any idea how good Google Translate is with the docs, eg https://fed-brid-gy.translate.goog/docs?_x_tr_sl=auto&_x_tr_tl=pt&_x_tr_hl=en&_x_tr_pto=wapp ?

It doesn't seem idiomatic to me. It's understandable, but likely not good enough to show by default based on the browser language, or at least I hate when websites do that with German.
(My Portuguese isn't good however. I can read most simple and technical texts but not write it without a translator.)

You could add a link to Google-translate the current page somewhere near the top.


Regarding Japanese, most auto-translation is really pretty abysmal and can cause misunderstandings.
It's possible to make it work by using non-idiomatic English as input, but that's a skill by itself.
(I can speak and write Japanese roughly at "tourist" level, but it's enough to understand inflection.)

You could still add the Google Translate link as users are mostly aware of how bad it is.
Many Japanese users prefer DeepL Translate since its output feels more natural, but in my experience it often makes factual mistakes instead. ("Currency conversion", negating some sentences, repetitions, things like that.)

@Tamschi Tamschi added the feature Features and feature requests that are specific to Bridgy Fed, not fully described by the protocols. label Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Features and feature requests that are specific to Bridgy Fed, not fully described by the protocols.
Projects
None yet
Development

No branches or pull requests

4 participants