Grammalecte  Check-in [d59335ae38]

Overview
Comment:[doc] formatting update
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk | doc
Files: files | file ages | folders
SHA3-256: d59335ae38de723b49480f7880589dc0afbaf9b089087638cb7b2aa9bce1452a
User & Date: olr on 2017-06-05 19:37:08
Other Links: manifest | tags
Context
2017-06-05
19:40
[doc] build.txt renamed build.md check-in: fbaf324acf user: olr tags: doc, trunk
19:37
[doc] formatting update check-in: d59335ae38 user: olr tags: doc, trunk
17:18
[build] adjustment of previous commit check-in: 63129ede50 user: olr tags: build, trunk
Changes

Modified doc/build.txt from [d154148022] to [50002dce5e].

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
..
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72

BUILDER

= Required =

    Python 3.6
    Firefox Nightly
    NodeJS
        npm
        jpm
    Thunderbird


= Commands =

== build a language ==

    make.py LANG
        generate the LibreOffice extension and the package folder.
        LANG is the lang code (ISO 639).

        This script uses the file `config.ini` in the folder `gc_lang/LANG`.

== First build ==

    Type:
        make.py LANG -js

    This command is required to generate all necessary files.

== options ==

    -b --build_data
        Launch the script `build_data.py` in the folder `gc_lang/LANG`.

    -d --dict
        Generate the indexable binary dictionary from the lexicon in the folder `lexicons`.

................................................................................
        Launch Firefox Nightly.
        Unit tests can be lanched from Firefox, with CTRL+SHIFT+F12.

    -tb --thunderbird
        Launch Thunderbird.


= Examples =

    Full rebuild:
        make.py LANG -b -d -js

    After modifying grammar rules:
        make.py LANG -t

    If you modify the lexicon:
        make.py LANG -d -js

    If you modify your script build_data.py:
        make.py LANG -b -js






|









|

|







|






|







 







|












<
<
<
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
..
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69




BUILDER

# Required #

    Python 3.6
    Firefox Nightly
    NodeJS
        npm
        jpm
    Thunderbird


# Commands #

## build a language ##

    make.py LANG
        generate the LibreOffice extension and the package folder.
        LANG is the lang code (ISO 639).

        This script uses the file `config.ini` in the folder `gc_lang/LANG`.

## First build ##

    Type:
        make.py LANG -js

    This command is required to generate all necessary files.

## options ##

    -b --build_data
        Launch the script `build_data.py` in the folder `gc_lang/LANG`.

    -d --dict
        Generate the indexable binary dictionary from the lexicon in the folder `lexicons`.

................................................................................
        Launch Firefox Nightly.
        Unit tests can be lanched from Firefox, with CTRL+SHIFT+F12.

    -tb --thunderbird
        Launch Thunderbird.


# Examples #

    Full rebuild:
        make.py LANG -b -d -js

    After modifying grammar rules:
        make.py LANG -t

    If you modify the lexicon:
        make.py LANG -d -js

    If you modify your script build_data.py:
        make.py LANG -b -js



Modified doc/syntax.txt from [2900658ffe] to [4f6735223c].

92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
    __<i>/option3__  pattern
    ...

Rules can be named:
    __[i]/option1(name1)__  pattern
    __[u]/option2(name2)__  pattern
    __[s>/option1(name3)__  pattern
    __<u>/option3(name4)__  pattern
    __<i>/option3(name5)__  pattern
    ...

Each rule name must be unique.


The LCR flags are also optional. If you don’t set these flags, the default LCR
flags will be:







|
|







92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
    __<i>/option3__  pattern
    ...

Rules can be named:
    __[i]/option1(name1)__  pattern
    __[u]/option2(name2)__  pattern
    __[s>/option1(name3)__  pattern
    __<u>(name4)__          pattern
    __<i>(name5)__          pattern
    ...

Each rule name must be unique.


The LCR flags are also optional. If you don’t set these flags, the default LCR
flags will be: