| 19:09 | <rkirsling> | ooh a ja-JP translation PR |
| 19:09 | <rkirsling> | I didn't have time to work on one but I do have time to review one :) |
| 19:16 | <shu> | of ecma262? |
| 19:17 | <rkirsling> | just the website 😅 |
| 19:18 | <rkirsling> | the thought of not only translating the spec but keeping it updated in multiple languages makes my head spin 😵 |
| 19:20 | <shu> | yes that seems not a feasible volunteer effort |
| 19:20 | <shu> | we'd need to hire a translation house who knows technical terms |
| 19:20 | <shu> | seems very expensive |
| 19:21 | <shu> | in some ways ecma262 is much better suited for translation than other PL specifications because of how pseudocode-y it is |
| 19:21 | <shu> | like the C++ spec? good luck with that |
| 19:21 | <rkirsling> | true |
| 19:31 | <leobalter> | well, I believe it gets even harder when we need to rethink the website structure to *properly* provide multiple languages, on top of everything else mentioned |
| 19:31 | <leobalter> | I'm a fan of website localizations but it requires time-investment |
| 19:32 | <leobalter> | and my concern goes only for the website, not even reaching the complexity of the specs and their living state |