Merge branch 'main' of https://github.com/giellalt/giellalt.github.io

apps/AppLocalisation.md

@@ -17,9 +17,24 @@ Localisation of each of them is described below.
 
 [borealium.org](https://github.com/borealium/borealium.org) is almost always localised using Pontoon. Log in using your GitHub account, it should be automatic. The exact setup of the localisation is as follows:
 
--   [Borealium Core](https://divvun-pontoon-vm.norwayeast.cloudapp.azure.com/projects/borealium/): the main web site, general texts and descriptions. All UI languages should be translated 100 % for this Pontoon project
--   Borealium Resources (except Pahkat resources): localised names and descriptions for the language resources listed on Borealium. This is a separate Pontoon project (to be created), and the only localisation requirement is that every resource is localised into its own language + English. Other languages may be added as desired or deemed useful, but it is not required.
--   Páhkat resources:
+-   **[Borealium Core](https://divvun-pontoon-vm.norwayeast.cloudapp.azure.com/projects/borealium/):** the main web site, general texts and descriptions. All UI languages should be translated 100 % for this Pontoon project
+-   **Borealium Resources (except Páhkat resources):** localised names and descriptions for the language resources listed on Borealium. There is [a separate Pontoon project for each language's resources](https://divvun-pontoon-vm.norwayeast.cloudapp.azure.com/projects/), and the only localisation requirement is that every resource is localised into its own language + English, where English is the reference as well as the last-resort fallback language. Other languages may be added as desired or deemed useful, but that is not required. **Adding new resources:**
+    - add basic info and links in `data/resources/` (copy one of the existing ones, then edit as needed)
+    - use string identifiers instead of actual strings
+    - add the string identifiers to the appriopriate localisation file in `resources/en/*-resources.ftl`, and provide suitable text in English (this becomes the reference text for localisation into other languages)
+    - localise the resources as needed in Pontoon (new strings for new resources are automatically synced to Pontoon each hour (on the hour)); the set of languages to localise into is configured in the file `resources/*-l10n.toml`, which has a very simple structure (example file taken from Faroese):
+
+        ```toml
+        [[paths]]
+            reference = "en/fao-resources.ftl"
+            l10n = "{locale}/fao-resources.ftl"
+            locales = [
+                "fo",
+                "da",
+            ]
+        ```
+    - Pontoon reads this config file, and in this case, Faroese resources should be localised into Faroese and Danish, using English as the reference. One adds more target localisations by adding the wanted language codes to the file above.
+- **Páhkat resources:**
     -   Spellers:
         -   native language and English: `configure.ac`, in the variables `SPELLER_NAME_NATIVE`, `SPELLER_NAME_ENG`, `SPELLER_DESC_NATIVE` and `SPELLER_DESC_ENG`. The text in these variables will be used to name and describe the spellers both in Borealium.org, and in other places.
         -   Other languages: add them to `manifest.toml.in`, under the sections `[speller.name]` and `[speller.description]`, as many as is needed.
@@ -38,14 +53,14 @@ Localisation of each of them is described below.
             description: Mobiltastatur for sørsamisk fra Divvun-gruppa.
         ```
         - One can add as many `locales` as needed.
-        - The new/edited locales are pushed to the Páhkat server on the next successfull CI build, and from there it is automatically picked up by borealium.org on the next site build. [**NB!** This seems not to work ATM. A [bug report](https://github.com/borealium/borealium.org/issues/32) exists.]
+        - The new/edited locales are pushed to the Páhkat server on the next successfull CI build, and from there it is automatically picked up by borealium.org on the next site build.
 
 **All Pontoon localisations** are automatically synced from Pontoon to GitHub, but *only* after the localisations have been *accepted*. **All Pahkat resource** localisations are automatically picked up on each site rebuild. The site is rebuilt every hour (on the hour), and on every `git push` to the repository.
 
-It is still possible to also do localisations directly in GitHub, and those changes will be synced with Pontoon automatically. For that reason, the documentation below is kept for reference.
-
 Pontoon projects and user configuration is administered [here](https://divvun-pontoon-vm.norwayeast.cloudapp.azure.com/a/).
 
+It is still possible to also do localisations directly in GitHub, and those changes will be synced with Pontoon automatically. For that reason, the documentation below is kept for reference.
+
 ---
 
 All pathnames in this section are relative to the root of the [borealium.org](https://github.com/borealium/borealium.org) repository.

infra/GettingStartedOnWindows.md

@@ -27,17 +27,25 @@ TODO: We should sort these out. While waiting, you are on your own. We want to
 
 #### Find a place for your files
 
-When you open the Linux terminal window, you are in `/home/yourlinuxusernamn/`. To see your home catalogue on Windows, write: `ls /mnt/c/Users/YourWindowsUserName/`
+When you open the Linux terminal window, you are in `/home/yourlinuxusernamn/`. 
 
-A good idea would be to make an alias in the _.profile_ file of your linux home folder, e.g. something along the lines of:
+
+Microsoft advices users to work with linux files on the linux part of the harddisk. For a presentation, see this [https://learn.microsoft.com/fi-fi/windows/wsl/filesystems#file-storage-and-performance-across-file-systems]( introduction to working with linux files on Windows). Important in this context are the reasons for working in your home catalogue. In order to access your linux files from the Windows file system you should write `\\wsl$` in the address bar of the file system.
+
+In your linux home directory, you should make a folder containing all and only the repositories (catalogues) from [github.com/giellalt](https://github.com/giellalt), you may e.g. call it `giellalt`. 
+
+
+It is possible to acces the files in your Windows home catalogue as follows: `ls /mnt/c/Users/YourWindowsUserName/`
+
+If you want to process your Windows files in linux you make an alias in the _.profile_ file of your linux home folder, e.g. something along the lines of:
 
 ```
-alias lgtech = "pushd /mnt/c/Users/YourWindowsUserName/Documents/lgtech"
+alias windoc = "pushd /mnt/c/Users/YourWindowsUserName/Documents/"
 ```
 
 ... where **YourWindowsUserName** should be replaced with your Windows user name (= the name of your home catalogue on Windows).
 
-Then writing `lgtech` when you open Linux will bring you directly to the relevant folder. You then may install all language technology files here. The good thing with installing them here and not under the home directory is that you can access the files with Windows programs (e.g. TextEdit) as well (but remember to use _UTF-8_ encoding!)
+Then writing `windoc` when you open Linux will bring you directly to the relevant folder.
 
 #### Install what is needed
 

proof/spelling/testdoc/error-markup.md

@@ -128,7 +128,7 @@ traditional speller is unable to detect them.
 Morpho-syntactic errors
 -----------------------
 
-    TEMPLATE: {wrong form}£{pos,gf,cat,orig,errtype|correct form}
+    TEMPLATE: {wrong form}£{pos,cat,orig-errtype,gf|correct form}
 
 Errors that require an analysis of (parts of) the sentence or
 surrounding words to be detected and corrected. In the resulting xml,
@@ -137,8 +137,8 @@ the element is named <errormorphsyn>.
 -   **Mark-up attributes:**  
     **pos** { noun \| verb \| adj \| adv \| num \| interj \| pp \| cc \|
     cs \| pcle \| prop \|pers \| refl \| dem \| resip \| indef \| x }  
-    **gf** { subj \| obj \| advl \| fin \| infin \| spred \| opred \|
-    pcle \| interj \| app \| conj \| pph \| x \| attr }  
+    **gf** { subj \| obj \| agr \| advl \| fin \| infin \| spred \| opred \|
+    pcle \| interj \| app \| conj \| pph\| pocompl \| prcompl \| attr  \| subjagr \| qagr \| x }  
     **cat** { nomsg \| nompl \| gensg \| genpl \| akksg \| akkpl \|
     illsg \| illpl \| locsg \| locpl \| comsg \| compl \| ess \| sg1prt
     \| sg2prt \| sg3prt \| du1prt \| du2prt \| du3prt \| pl1prt \|
@@ -155,25 +155,31 @@ the element is named <errormorphsyn>.
     ger \| vgen \| x }  
     **errtype** { agr \| case \| tense \| mode \| number \| mix \| x }
 -   **Some explanations:**  
-    gf = grammatical function  
-    subj = subject  
+    advl = adverbial, e.g. *Mun boađán 'sotnabeaivi'* vs. *Mun boađán 'sotnabeaivve'*  
+    app = apposition  
+    attr = attribute  
+    conj = conjunction/subjunction  
+    eagr = agreement with existential subject
     fin = finite verb  
+    genpl = acc/gen pl
+    gensg = acc/gen sg  
+    gf = grammatical function
     infin = infinite verb  
-    obj = object  
-    spred = subjectpredicative  
+    interj = interjection  
+    nump = numeral phrase  
+    obj = object
+    oblsubj = oblique subject (interference error of type "muu kalga porgâđ"
     opred = objectpredicative  
-    advl = adverbial, e.g. *Mun boađán 'sotnabeaivi'* vs. *Mun boađán
-    'sotnabeaivve'*  
-    pph = pp phrace, e.g. *sullo guovdu* vs. *guovdu sullo*  
-    conj = conjunction/subjunction  
     pcle = particle  
-    interj = interjection  
-    app = apposition  
-    attr = attribute  
+    pocompl = complement of postposition (also prcompl)
+    pph = pp phrace, e.g. *sullo guovdu* vs. *guovdu sullo*  
+    pred = predicative  
+    qagr = agreement with quantifier phrase
+    qucompl = complement of quantifier
+    spred = subjectpredicative  
+    subj = subject  
+    subjagr = agreement with subject
     x = unknown  
-    nump = numeral phrase  
-    gensg = acc/gen sg  
-    genpl = acc/gen pl
 
 <!-- -->