You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just wondering if we should use language-specific screenshots in our docs...
If we do, it will introduce some maintenance overhead (currently, 1 screenshot X #supportedLanguages). However, it will also make the docs more inclusive (besides giving us an opportunity to showcase our support for language localization).
For example, the following screenshots in the README may not be very comprehensible for a native Hindi speaker (if they are not fluent in English) just like how the Hindi text in the README is not very comprehensible for a native English speaker (if they are not fluent in Hindi):
I know an English speaker won't look at the Hindi docs but a Hindi speaker would...
If the app supports language localization, it may be a good idea to showcase it in the docs as well.
The text was updated successfully, but these errors were encountered:
I'm a bit torn, on one hand I think it would be great for non-native English speakers. On the other hand it might be too big of a burden? A lot of translators don't fiddle with programming.
If we could only open the app automatically with a script and take the screenshots :D
Just wondering if we should use language-specific screenshots in our docs...
If we do, it will introduce some maintenance overhead (currently, 1 screenshot X #supportedLanguages). However, it will also make the docs more inclusive (besides giving us an opportunity to showcase our support for language localization).
For example, the following screenshots in the README may not be very comprehensible for a native Hindi speaker (if they are not fluent in English) just like how the Hindi text in the README is not very comprehensible for a native English speaker (if they are not fluent in Hindi):
I know an English speaker won't look at the Hindi docs but a Hindi speaker would...
If the app supports language localization, it may be a good idea to showcase it in the docs as well.
The text was updated successfully, but these errors were encountered: