TASK - Translation and localisation pre-requisites

[trallard]

📌 Summary

🔖 Tasks to complete

🔍 Acceptance Criteria

[gabalafou]

Clarifying question: is this about the end user interface or documentation or both?

[trallard]

End user interface (bokeh plotting)

[gabalafou]

My notes from discussion with Matteusz today:

• the areas that will need to be translated

  • tool bar, descriptions
  • error messages
  • widgets (a few strings)

• most text in Bokeh UI will be user-provided

• Error messages : most only occur in the dev console, we need to surface these to end users that don't know about browser dev tools

• This will be a huge part of the effort ^^

• next steps, in broad strokes:

  1. expose all error messages to UI
  2. mechanism in Bokeh.JS to provide text translations
  3. translations be done (one way or another)

• can this process be integrated automatically?

• some place to store translated strings, part of main bundle, probably fine at the beginning, how much size is needed for translations.
  Main bundle of BokehJS is pushing 1100 kilobytes.

• Reach out to other projects, what has worked for them, pros and cons. We don't want recompile BokehJS every time a translation has been added.

• Cross-reference:

  • Unified Bokeh model for text rendering bokeh/bokeh#10995

[gabalafou]

Some notes today from internal Quansight sync.

Part of this task is:

• Tool or button or something that allows end users to switch languages
• Make sure characters outside Latin alphabets are support (for example, Chinese characters)
• Right-to-left support
• Allow plot authors to mark strings in their own plots as translatable

We also need to determine: are all of the strings that we need to mark as translatable in JavaScript.

Note: out of scope for this issue, doc strings and help text in .py file (e.g., in Python models).