For anyone who doesn’t see why this is important, נסו בבקשה לחשוב איך הייתן·ם מרגישות·ים אם הייתן·ם צריכות·ים לשאול שאלה בעברית כדי להצליח לעשות משהו בטייפסט שהיה חשוב לכן·ם, אבל לא היתה לכן·ם אוריינות עברית ברמה מספקת בשביל לעשות את זה.
I can sympathize. I live in a country where I cannot use my native language to interact with society and have to use a language I am not completely proficient in. I can’t even read it for the most part.
The idea that language differences pose an accessibility issue is not new, but many people haven’t experienced it personally.
Now, if accessibility is the main issue being brought up, wouldn’t it be more advantageous to focus on the entry points? I.e., a new user to Typst is not likely going to learn Typst from the forum. They will look at tutorials and docs and examples. If these are translated it is helpful.
That being said, I don’t think the state of Typst is necessarily ready for that kind of investment of time and effort. The engine is continuing to change which means documentation is in flux and it is hard to keep translations in sync.
This discussion and the ideas presented need serious consideration regarding issues of scale and scope, and how any idea to “add X for each Y” can place significant burden on administrators.
I’ve stated other issues above.
1 Like
Running more than one Discourse instance is unsustainable. As is, we are marshalling more compute resources for Discourse than for all of Typst’s own components combined (note that the Forum was more or less idle when this screenshot was taken). On top, it would be difficult to administer multiple instances. If we add multiple languages, it will be on this instance.
3 Likes
If running discorse is so resource intensive, are there other forum softwares that should be considered?
Discourse is widely used and we (or more specifically, @reknih) put a lot of effort into customizing it, so we won’t move away from it.
5 Likes