Important instructions

• Please translate the Main and Simulator components first; they are much more important than the Gallery and Modules components.
• The syntax [Text](/url) is for links. Only the "Text" part should be translated (e.g. becoming [文字](/url)).
• The syntax `code` and \(LaTeX\) are for code, and should not be translated (e.g. same as English) except for placeholder and natural language subscripts.
• If you use machine translation, please do the necessary post-editing before saving, or within three days after first saving.
• If you have a GitHub account, you need to link it to your translator account (or use GitHub-recognized email) in order to appear as contributors on GitHub. Otherwise, your name/id will only appear on the bottom of the About page.

Adding a new language

• To create a new language, click into the Main component and click "+" in the upper left corner of the list.
• Due to resource limit, if you want to add a language which is only a small variant of an existing language (e.g. American or British English), or one with little practical use (e.g. Latin), please discuss with the maintainer first.
• In some situations, there may be no strings in the new component. You may need to wait for a few hours for the strings to be synced.
• After the strings are synced, please translate at least the first 20 strings in the Main component in the next three days.

Details

The components are

• Main: The strings for the home page, about page, and all the "Tools" and "View" descriptions. Most of them are shared between the home page and the simulator.

• Simulator: The strings which are only for the simulator. Not including the content of the "Tools -> Other -> Import Modules" window.

• Gallery: The strings for the Gallery page and of all the items in the Gallery. This includes the text in the carousel in the home page and the examples in the module tutorial.

• Modules: The content of the "Tools -> Other -> Import Modules" window, and the module tutorial page.

  The simulator web app will have the language option as long as the translation starts. But other webpages will be built only if the number of translated string reaches some threshold and/or certain strings are translated. After the translation is updated, the repo (and thus the website) will be updated within a week.

  Some of the strings are in Markdown format. Do not add additional line breaks unless necessary (they will be shown as line breaks on the webpage). For strings that already contains line breaks but not due to new paragraphs or itemize (especially the ones in the gallery data), please make similar line breaks in the target language such that the total width of the text is as closed to the source language as possible, and the breaking points as semantically reasonable as possible. In this case, the number of lines does not need to match that of the source strings.

  The key of the string provides some information about the context of the string. For example, the ambiguous string "Translation" has the key sceneObjs.Handle.transformations.translation, indicating that it appears in the "Transformations" option of the "Handle" object in the scene, and hence means the geometrical translation, not language translation. Another example is the string "Architecture / Alpine" which seems unrelated to optics. But looking at Its key galleryData.seaMirage.architecturealpine, one can see that it appears in the "Sea Mirage" item in the Gallery, thus can look at it in the Gallery webpage to understand its context.