> Can we discuss a better way to translate Rails documentation and blog posts?
> It is so counterproductive that there is no option to display translations
> when accessing each documentation.
> Could we follow the Ruby or React repository structure?
If you’re familiar with the topic, or have at least looked into it a bit,
perhaps you could summarise what those strategies look like, and their
trade-offs?
>From my own quick look at what those seem to be doing, I see how it would work
>to translate the rubyonrails.org marketing site, but not any of the
>documentation that lives in the main rails/rails repository (which includes
>the guides).
If there’s general agreement with a better solution, are you offering to make
it happen?
(I have mixed feelings about translations of release-announcement blog posts in
particular: improving accessibility is good, but if it means a
seemingly-official channel will lag months behind reality...)
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rubyonrails-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/rubyonrails-core/D6E9AD56-EE8A-46C2-B4FC-DCB870D02D47%40trebex.net.
