| At line 198 added 33 lines |
| = using words : *pro* internationalisation |
|
| **basic error:**\\ |
| Using words in wiki syntax is //not// an obstacle to internationalisation, rather the contrary ; as long as the author can use his/her own language ! |
| Such (key)words need not and should not be used for prominent formatting, such highlight or list. Rather it may be very useful for precising elements. Especially for imported blocks, or variables. This allows using the same syntax for analog , but distinct element types. For instance : |
|
| ((page navigation | dynamic=true)) |
|
| ((box new_page | title="crear nov paj")) |
| ((image logo.png | tag="logo" | hSize=55)) |
|
| (()) means import -- a keyword shows the type of element -- then its id/location -- and possible parameters. |
|
| Technically, it's really easy to do. The best would be to include the available translations into the parser. Otherwise, it can be done in the editor, which even gives the user the possibility to change the lexicon. |
| Both solutions are based on a dictionary. |
| **build lexicons** |
| * give each feature a descriptive name/ID, such as "dynamically_imported_image" |
| * choose a clear keyword for each ID in all languages |
| * from this build a lexicon per language |
| **write in your own language** |
| * the site admin and/on the user can choose the language |
| * separating foreground & background : the editor reads and displays keywords in the chosen language but stores matching IDs |
| //or// |
| * the parser transcodes to html according to the language parameter |
| **distribute** |
| * the real source holds IDs, not language-dependant keywords |
| * the lexicons are present on all sites who know creole |
| * other authors read the same source in their //own// language |
|
| //Note that this principle works for any programming language ! With such an supple editor -- foregroung/background separation --, your could programm C or python or whatever in your own mother tongue. And even change language features to fit your view: I would change assignment to ':' instead of '='.// |
|
|
|
| At line 234 added 2 lines |
|
|
| At line 210 changed 6 lines |
| |= style | | | | | |
| | highlight | * ! | ! | | * conflict with list\\! good | |
| | distinct | / | / | / | perfect !? | |
| | monospace | # = _ | = | | # conflict with anchor & list | |
| | litteral/escape | ~ {{{{{{}}}}}} \ = " ' | " | | " pb at start of line | |
| |= link/pointer | | | (may also be considered as component) | then use brackets for component | |
| |= style | | | | simple char at start of line for alinea style | |
| | highlight | ** !! | !! | | * conflict with list\\! good | |
| | distinct | // | // | | perfect !? | |
| | monospace | ## == __ |= = | | # conflict with anchor & list | |
| | litteral/escape | ~~ {{{{{{}}}}}} \\ "" '' | " | | " pb at start of line? | |
| |= link/pointer | | | | then use brackets for component | |
| At line 231 changed one line |
| | code | (()) | | ((python print("nohtyp"))) | parenthesis ? | |
| | code | (()) | | ((python {{{|}}} print("nohtyp"))) | parenthesis ? | |
| At line 276 added 2 lines |
| (*) A link may also be considered as a generated component. This choice would be consistent with the facts : a link is not only text, and it accepts parameters. Syntax : [[link page | alias]]. Pb : it makes longer a very common feature. But the real typing pb lies in the double double bracket, not in typing a short word, as there's already text to type in the address. Or what ? Side advantage : it makes brackets or braces free for something else (placeholder - variable - what else ?). |
|
| At line 246 changed 32 lines |
| = using words : *pro* internationalisation |
|
| **basic error:**\\ |
| Using words in wiki syntax is //not// an obstacle to internationalisation, rather the contrary ; as long as the author can use his/her own language ! |
| Such (key)words need not and should not be used for prominent formatting, such highlight or list. Rather it may be very useful for precising elements. Especially for imported blocks, or variables. This allows using the same syntax for analog , but distinct element types. For instance : |
|
| ((page navigation | dynamic=true)) |
|
| ((box new_page | title="crear nov paj")) |
| ((image logo.png | tag="logo" | hSize=55)) |
|
| (()) means import -- a keyword shows the type of element -- then its id/location -- and possible parameters. |
|
| Technically, it's really easy to do. The best would be to include the available translations into the parser. Otherwise, it can be done in the editor, which even gives the user the possibility to change the lexicon. |
| Both solutions are based on a dictionary. |
| **build lexicons** |
| * give each feature a descriptive name/ID, such as "dynamically_imported_image" |
| * choose a clear keyword for each ID in all languages |
| * from this build a lexicon per language |
| **write in your own language** |
| * the site admin and/on the user can choose the language |
| * separating foreground & background : the editor reads and displays keywords in the chosen language but stores matching IDs |
| //or// |
| * the parser transcodes to html according to the language parameter |
| **distribute** |
| * the real source holds IDs, not language-dependant keywords |
| * the lexicons are present on all sites who know creole |
| * other authors read the same source in their //own// language |
|
| //Note that this principle works for any programming language ! With such an supple editor -- foregroung/background separation --, your could programm C or python or whatever in your own mother tongue. And even change language features to fit your view: I would change assignment to ':' instead of '='.// |
|
| = newline / paragraph : the big problem ! |
| = newline / paragraph : the hole big chaos problem ! |
.