Difference between revisions of "BPFK style guidelines for Lojban dictionary definitions (proposal draft)"

From Lojban
Jump to: navigation, search
(nu zasygau)
 
m (formata nu cikre)
Line 3: Line 3:
 
== General ==
 
== General ==
  
Each meaning definition should be clear, easy and comfortable to read for everyone, and not cluttered with slashes, obscure abbreviations or anything else hindering readability or comprehension. Lists of appropriate translations or glosses are preferably put into a dedicated dictionary entry field, separate from the main definition.
+
* Each meaning definition should be clear, easy and comfortable to read for everyone, and not cluttered with slashes, obscure abbreviations or anything else hindering readability or comprehension. Lists of appropriate translations or glosses are preferably put into a dedicated dictionary entry field, separate from the main definition.
Each meaning definition should be simple, made from simple terms, even if that leads to more verbosity.
+
* Each meaning definition should be simple, made from simple terms, even if that leads to more verbosity.
Each meaning definition should be as generic as possible, so as to encompass the whole semantic range of the lexeme being defined.
+
* Each meaning definition should be as generic as possible, so as to encompass the whole semantic range of the lexeme being defined.
The appropriate gloss words are recorded in the gloss fields.
+
* The appropriate gloss words are recorded in the gloss fields.
The etymologies are presented along with the definition in order to help retaining the term and its origin.
+
* The etymologies are presented along with the definition in order to help retaining the term and its origin.
The various sumti types must be specified between parentheses: proposition (du'u), event (nu), property (ka), quantity (ni)…
+
* The various sumti types must be specified between parentheses: proposition (du'u), event (nu), property (ka), quantity (ni)…
The predicate argument slots are marked with the x1…xN notation. The place structure's etymology (mostly relevant with lujvo) should be moved to the note fields, or ideally to a dedicated field.
+
* The predicate argument slots are marked with the x1…xN notation. The place structure's etymology (mostly relevant with lujvo) should be moved to the note fields, or ideally to a dedicated field.
  
  

Revision as of 16:33, 19 July 2015

BPFK style guidelines for Lojban dictionary definitions (proposal draft)

General

  • Each meaning definition should be clear, easy and comfortable to read for everyone, and not cluttered with slashes, obscure abbreviations or anything else hindering readability or comprehension. Lists of appropriate translations or glosses are preferably put into a dedicated dictionary entry field, separate from the main definition.
  • Each meaning definition should be simple, made from simple terms, even if that leads to more verbosity.
  • Each meaning definition should be as generic as possible, so as to encompass the whole semantic range of the lexeme being defined.
  • The appropriate gloss words are recorded in the gloss fields.
  • The etymologies are presented along with the definition in order to help retaining the term and its origin.
  • The various sumti types must be specified between parentheses: proposition (du'u), event (nu), property (ka), quantity (ni)…
  • The predicate argument slots are marked with the x1…xN notation. The place structure's etymology (mostly relevant with lujvo) should be moved to the note fields, or ideally to a dedicated field.


Language-specific recommendations

(...)