| At line 196 added 3 lines |
| = marking components |
| todo |
|
| At line 200 added one line |
| //buiding a matching table// |
| At line 201 changed one line |
| == character <--> use matching table |
| == feature --> character table |
| At line 209 changed one line |
| |= link/pointer | | | (may be considered\\as generated block) | \\ then use brackets for generated\\ & braces are free | |
| |= link/pointer | | | (may be considered\\as generated block) | then use brackets for generated\\& braces are free | |
| At line 215 changed one line |
| | new alinea\\paragraph | NLNL NL § {{{\\\}}} | | | prefered NLNL or § | |
| | new alinea\\paragraph | NLNL NL § {{{\\\}}} | | | see alinea break\\§ similar to list & title\\NLNL good display | |
| At line 223 changed 2 lines |
| | imported | () | | (image address) | | |
| | generated | {} | | {toc} | | |
| | component | {{}} | | {{image address}} | | |
| At line 226 changed one line |
| | code | | | | | |
| | code | (()) | | | parenthesis ? | |
| At line 229 changed one line |
| | scissor/glue | {{{\\}}} __ | | | avoid ! \\ not a tag | |
| | scissor/glue | {{{\\}}} __ | | | avoid ! (confusion)\\not a tag | |
| At line 239 added 5 lines |
| == feature --> character table |
| todo -- the opposite of above, to better see free & matching characters |
|
|
|
| At line 246 added 3 lines |
| **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 : |
| At line 250 added 3 lines |
| ((page navigation | dynamic=true)) |
| ((box new_page | title="crear nov paj")) |
| ((image logo.png | tag="logo" | hSize=55)) |
| At line 240 changed one line |
| = newline / paragraph : the big problem ! |
| (()) means import -- a keyword shows the type of element -- then its id/location -- and possible parameters. |
| At line 256 added 15 lines |
| 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 |
| At line 272 added one line |
| //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 274 added 4 lines |
| = newline / paragraph : the big problem ! |
| todo -- see notes about that everywhere on this page |
|
|
.