... | @@ -370,7 +370,9 @@ and providing a `kr.js` file in their `MathJax/localization/kr` directory that d |
... | @@ -370,7 +370,9 @@ and providing a `kr.js` file in their `MathJax/localization/kr` directory that d |
|
|
|
|
|
## The Translation Files ##
|
|
## The Translation Files ##
|
|
|
|
|
|
In order to make working MathJax data convenient for translators, we will need to provide the translation strings in one of the standard formats, like `.po` for example. The usual approach is to have a program that scans the code for the `_()` calls and builds the data file from that, and that should work with MathJax as well. The `.po` format supports the domain approach, as well as plural forms, and the idea of multiple forms (e.g., verb versus noun). HTML snippets should be translated into HTML strings, so that
|
|
In order to make working MathJax data convenient for translators, we will need to provide the translation strings in one of the standard formats, like `.po` for example. We will need to decide on a format (or perhaps formats) that we want to be able to provide for translators. The examples below will use `.po`, but any format could be chosen.
|
|
|
|
|
|
|
|
The usual approach is to have a program that scans the code for the `_()` calls and builds the data file from that, and that should work with MathJax as well. The `.po` format supports the domain approach, as well as plural forms, and the idea of multiple forms (e.g., verb versus noun). HTML snippets should be translated into HTML strings, so that
|
|
|
|
|
|
["Do it ",["b",null,["now!"]]]
|
|
["Do it ",["b",null,["now!"]]]
|
|
|
|
|
... | | ... | |