FORMAT: zrajm-database
VERSION: 1.4
SHA1: 95f01d17de990455ee8ac49cdda639e32713ed52
URL: http://klingonska.org/dict/dict.zdb
LICENSE: Creative Commons Attribution-ShareAlike 3.0
AUTHOR: zrajm
1. About
========
This is *Klingonska Akademien’s* word database. You’re free to use it in any
way you see fit, as long as you give us credit and provide a link to the
[Klingon Pocket Dictionary](http://klingonska.org/dict/).
* [2012-01-27] 2732 Klingon words (not counting affixes, and words marked
with ‘*’ in their `tlh:` field).
* [2011-11-01] 2698 words.
1.1. Syncing Against This Database
----------------------------------
This file, though human-readable, is written so as to simplify fetching and
syncing by external programs. If you’re writing a program which will
periodically update its own internal dictionary by fetching this database you
should read through the “Metadata Header” section.
If you poll this database for changes, please do not use a shorter polling
interval than 24 hours.
2. Description of This File’s Format
====================================
Character set is UTF-8. No line exceed 79 characters in length (not counting
newline at the end of each line). This goes for both database and comments. The
different parts of this file are:
1. Metadata header
2. Preamble (= comments)
3. Database chunk
1. Section 1
2. Section 2
3. ...
4. Postamble (= comments)
2.1. Metadata Header
--------------------
The *metadata header* is everything up to the first blank line. It is similar
to an email header. It consists of attribute/value pairs, lines with leading
whitespace are a continuation of the previous line. This is the meaning of the
values:
> `FORMAT`: *File format.* Value is always `zrajm-database`. A program fetching
> the database should use this to verify that the correct file is received (and
> that you’re not receiving an error page or similar).
> `VERSION`: *Database version.* This value will change when new fields are
> introduced into the dictionary, if a required field is removed or if the
> format of a field changes. (This rarely happens.) A program fetching the
> database *must not* blindly import the database if `VERSION` has changed
> since last fetch (the program itself will need to be updated to handle these
> changes -- you might want to tell your users to look for a program update
> when this happens).
> `SHA1`: *Database chunk checksum.* This value will change whenever a change
> is made to the actual database (not counting changes in the commentory
> preamble and postamble). A program fetching the database should use this
> value to determine whether or not the database has been updated since last
> fetch. (Only if `SHA1` has changed since last fetching will there be any need
> to update the internal dictionary.)
> `URL`: *Web address of the database.* Use this URL to fetch the latest
> version the database. (A program to doing this should be prepared to handle
> web redirects.)
> `LICENSE`: *Database license.* (I’m *not* claiming to license the Klingon
> language -- the language isn’t mine to claim.)
> `AUTHOR`: *Author of this database.* (As opposed to Marc Okrand, who invented
> the language.)
2.2. Database Chunk
-------------------
The *database chunk* is everything between the lines “`== start-of-data ==`”
and “`== end-of-data ==`” (using two equal signs). The database chunk is in
turn split into any number of sections.
2.3. Sections
-------------
Each *section* is everything between the lines “`=== start-of-
===`” and “`=== end-of- ===`” (using three equal signs).
`` is always lower case, and with hyphens instead of spaces. Any
text occurring between sections are ignored. Each section is sorted in Klingon
alphabetical order. There are four sections in this database (this is unlikely
to ever change):
* `word-list`
* `verb-prefix-list`
* `verb-suffix-list`
* `noun-suffix-list`
### 2.3.1. Section Contents ###
A section consists of one or more *entries* separated from each other by one
blank line.
Each entry is built up of *fields* (attribute/value pairs) consisting of a
*field name* and a *field value*, each field name is separated from its value
with a colon + a single tab character. Like this:
NAME:VALUE
[CONTINUED]
Some field values contain multiple lines (which is good, since lines are not
allowed to be longer than 79 characters [see above]). A line which is a
continuation of the previous line start with a single tab character. (Programs
should consider this indentation equivalent to a single space.)
Field names are from the ‘List of Field Names’ below (no other field names are
allowed), and the name of the field defines the format of the field value. The
same list is used for all sections of the database. (Programs should
disregard/throw away fields whose field name is not on the list below, and
never present any such field to the user.)
### 2.3.2. List of Field Names ###
These are the occurring field names, including descriptions of the format of
the value for each of them. This list us used for all the sections of the
database.
Within each entry, the fields come in the order listed here. (Programs reading
this file should not rely on this order, as it is not considered part of the
file format. Changes in field ordering only will not result in change of the
`VERSION` number.)
Fields are either: ‘required’ (= present in all entries); ‘optional’ (= occur
in some entries) or ‘multiple’ (= occur some entries but sometimes more than
once in the same entry).
* `tlh:` Klingon word [REQUIRED]
Contains a Klingon text given in curly brackets (e.g. `{jotHa’}`), and
optionally a word counter (split into pre-word, post-word, and post-word
sub-counter, described below). The Klingon word is also preceded by an
asterisk in certain cases (described below).
NOTE: If there is more than one word inside the curly brackets `data:
phrase` is also set.
A leading asterisk is used to indicate `deprecated` and `non-canon` words
(e.g. `*{jIn}`). NOTE: Such entries also (1) have the `warn:` field set and
(2) have `data: non-canon` or `data: deprecated`. (See: `warn:` and `data:`
below.)
Words that are homonyms also have one or more counter(s) for describing the
layout of the word in the pocket dictionary. There are three such counters:
1. **pre-word counter** comes before the word (in square brackets) and
separates homonyms that are not semantically related. E.g. `[1] {nIH}`
(verb) versus `[2] {nIH}` (noun).
2. **post-word counter** comes after the word (in square brackets) and
separates homonyms that are related in meaning, but which have different
parts-of-speech. E.g. `{bach} [1]` (verb) versus `{bach} [2]`
(noun).
3. **post-word sub-counter** comes after the word (after a period, inside
the same square brackets as the post-word counter) and separates
homonyms that are related in meaning *and* have the same
parts-of-speech. (This can, for example, be a word with slightly
different meanings in {ta’ Hol} and some dialect.) E.g. `{cheSvel} [.1]`
(noun) versus `{cheSvel} [.2]` (noun) (regional).
All three counters may be used the same time for a specific word. E.g. `[2]
{pa’} [.2]` (noun) (slang) or `{qaD} [2.1]`
(noun). Taking these counters into account, each `tlh:` field in the
dictionary is unique.
Ordering of homonyms is (currently) loosely based on dialect and
part-of-speech. Standard dialect words are sorted before slang/regional
words, and part-of-speech order is as follows.
> adv >> v >> excl >> pro >> ques >> conj >> num >> n >> name
(Basically ‘verby’ words come first -- since adverbials can form sentences
in their own right, as well as take part of a sentence they’re deemed
‘verbier’ that normal verbs, pronouns and (some) question words also move
between acting as verbs and nouns and are there fore considered quite verby
too. numerals can likewise assume the role of adjectives, which makes them
verbier than a plain noun.)
This ordering stuff will be formalised (and maybe changed) in the future.
Lookup word markup («...») also occurs inside the curly brackets of this
field. Everything said about that under the `en:` field also applies here.
* `warn:` warning for deprecated or non-canon entries [OPTIONAL]
NOTE: All words with a leading asterisk in `tlh:` field, have this field
(and no others). Words with a leading asterisk are also labeled `non-canon`
or `deprecated` in their `data:` field.
* `pos:` part-of-speech [REQUIRED]
Gives the part-of-speech, or word class of the entry. The value is a full
description (not an abbreviation). Allowed values are:
* adverbial
* conjunction
* exclamation
* name
* noun
* noun suffix type 1
* noun suffix type 2
* noun suffix type 3
* noun suffix type 4
* noun suffix type 5
* numeral
* pronoun
* question word
* verb
* verb prefix
* verb suffix type 1
* verb suffix type 2
* verb suffix type 3
* verb suffix type 4
* verb suffix type 5
* verb suffix type 6
* verb suffix type 7
* verb suffix type 8
* verb suffix type 9
* verb suffix type rover
* `en:` English definition (from canon sources) [REQUIRED]
English definition of the Klingon word, with all English lookup words
(those words you you would look for in the English--Klingon side of the
dictionary) marked with <...> or «...». (These angle brackets are used for
extracting and sorting entries for the English--Klingon side of a
dictionary, they should not be presented for the end user.)
Single angle brackets <...> indicates that the word has been used as a
lookup word in a *canon* word list (TKD, KGT or similar). Double angle
brackets «...» marks words that have not appeared as lookup words in any
canon word list, but which are nevertheless considered to be an acceptable
lookup word (commonly these are words used in canon, but not in a canon
*word list*).
Some additional markup is also used:
~...~ = italic
{...} = Klingon (bold)
* `sv:` Swedish translation of `en:` [REQUIRED]
Same format as `en:` (except that `<...>` is never used, since there has
never been any Klingon canon written in Swedish).
If a Swedish translation is missing it is marked with «», and the same
entry also have a `meta: FIXME` comment.
* `desc:` very short description [OPTIONAL]
A very brief text describing the Klingon word, meant for inclusion in the
pocket dictionary. -- Since brevity is of the essence for this field, the
following common dictionary abbreviations are used (their unabbreviated
forms are not allowed):
* pl. = plural
* sg. = singular
* obj. = object
* subj. = subject
* s.o. = somebody/someone
* s.t. = something
Some additional markup is also used:
~...~ = italic
{...} = Klingon (bold)
* `def:` source where definition can be found [REQUIRED]
Defining source references for this entry. A source count as ‘defining’ if
it substantially adds to the understanding of the word. This is usually the
first canon mention of the word (where the translation of the word is
given), but occasionally there are multiple sources that are important for
understanding the word (with additional grammar specific to the word,
additional English words to describe it, etc.).
Source syntax.
* The name of a source is always just one word. (Only alphanumeric
characters and hyphen are allowed.)
* After the source name (space separated) may follow a page or chapter
reference (e.g. "TKD p.45"). This word may never be given in
parentheses.
* If there are more than one source, they are separated by semicolon.
* Secondary source(s) may be specified for each source. Secondary sources
are given in parentheses after a (primary) source. -- A secondary
source is a source that contains a (whole, or partial) transcript of
the primary source. (Secondary sources are especially important where
the primary source is difficult to find or obtain.)
Source names.
* Most sources use the common abbreviations (TKD, CK, PK, TKW, KGT,
etc.). For {HolQeD} articles volume and number is included in the name
(e.g. "HolQeD-04-3"). In the case of email, news, web and {qep'a'}
sources the name is preceded by a date (e.g. "1997-07-20-email" or
"1996-qep'a'").
* If there are more than one article in the same issue, or more than one
news/email/web posting the same day, the source is further labeled with
a letter (e.g. "1997-09-01d-news" or "2002-09-holqed-11-3-b").
* Each sources references point out a file in canon/. To transform a
source name into a file name, first a string is generated by downcasing
the source reference, removing apostrophes and appending '.txt'.
Thereafter the canon/ directory is searched for a file matching this
description (optionally preceded by a date).
Examples:
def: TNK (2011-10-29-Email)
def: TKD; SBX-S14 (HolQeD-04-3-a); SBX-S26 (HolQeD-05-3-b)
In the top example have TNK as a primary source, and points out that TNK
material relevant for this entry can also be found in "2011-10-29-Email".
The second example have three primary sources, TKD, and Skybox cards S14
and S26, with each Skybox card having a secondary source in the form of
{HolQeD} articles which published transcripts of the cards in question.
* `ref:` canon sources where it also occurs [OPTIONAL]
Reference source. Basically this means any source where the word is
mentioned. Typically one or two illuminating examples are given, but not
much more. Same syntax as 'def:' field.
* `cite:` quote from specific source [MULTIPLE]
One `cite:` field per quote. Each value ends with source reference (with
same syntax as 'def:' field) in square brackets.
* `com:` special comment concerning the entry [OPTIONAL]
Comments concerning the word of this entry. Basically any comment that (1)
is of interest to the user and (2) does not belong in the `cite:` or
`meta:` or `pun:` fields.
FUTURE (March 2012): The `cite:` field is still quite new, and much of the
`com:` field contents will be migrating there.
* `pun:` comments about puns and/or word play [OPTIONAL]
Comments related to puns. Anything from certain and verified puns, to
mnemonics, to wild speculation on the punnyness of the word.
* `see:` pointer to related word(s) (separated by semicolon) [OPTIONAL]
Pointers to synonyms, antonyms and words with similar meanings. Right now
not very consistently implemented.
* `tag:` topic tags [REQUIRED]
Semicolon-separated list of tags, used to lump entries together by topic.
(This field is considered free text, adding/changing of categories will not
change dictionary VERSION.) This is intended to help users find words
related to any the specific topics.
The first tag is the coinage year (the year of the first occurrence of the
word) -- in some cases this will be before TKD. E.g. if the word occurred
in "Star Trek: The Motion Picture" the coinage year will be 1979 -- even
though that was before the language was actually invented).
The following topics currently exist:
+ `Anglicism` = The Klingon word is borrowed from English (e.g., {qa'vIn}).
+ `animal`
+ `architecture`
+ `body part`
+ `clothing`
+ `color`
+ `country`
+ `curse`
+ `economics`
+ `family`
+ `fighting`
+ `food`
+ `KLCP1` = The 502 basic words which one needs to know in order to pass
the first level of KLI’s “Klingon Language Certification Program”.
+ `Klingonism` = An English translation is borrowed from Klingon (e.g.,
~bat'leth~).
+ `landscape`
+ `math`
+ `measure`
+ `music`
+ `placement`
+ `quantity`
+ `religion`
+ `shape`
+ `time`
+ `weather`
Possible/likely changes: Renaming of some categories to include more words.
* `data:` data tags [OPTIONAL]
Semicolon-separated list of tags. Differs from `tag:` in that the `data:`
tags also affect the presence or format of other fields.
+ `derived form` = The entry is a word built from other Klingon morphemes
(these words are included in the dictionary to provide a non-obvious
lookup entry in the English--Klingon side of a dictionary; such a
`derived form` may thus be excluded from the Klingon--English side when
generating a dictionary); e.g. {chenmoHwI’} constructed from {chen} ‘take
form’ + {-moH} ‘cause’ + {-wI’} ‘one who does’.
+ `phrase` = The Klingon word in the entry contains space (i.e. the Klingon
lookup entry is more than one word). NOTE: This tag is always present
when there is a space in the `tlh:` word.
+ `deprecated` = The Klingon word of the entry occurs misspelled in canon.
The entry is included only for completeness, and also carries a warning
which should be displayed to the user. Words marked with this tag may be
excluded from the Klingon--English side of a dictionary, and *should* be
excluded from the English--Klingon side. Examples: *{tIb}, *{pu’bej} etc.
NOTE: An entry with this tag always carry a `warn:` field + leading
asterisk in `tlh:` as well.
+ `non-canon` = The Klingon word of the entry is not canon (used for words
that, for various reasons, otherwise might be mistaken for canon). The
word is sometimes a word previously thought of as canon, but later
disproven, sometimes it is a word occurring in canon either misspelled,
or as an example of incorrect usage. Non-canon words are not included in
the pocket dictionary. NOTE: An entry with this tag always carry a
`warn:` field + leading asterisk in `tlh:` as well.
+ `non-phonotactic` = The Klingon word of the entry does not adhere to the
standard rules for how Klingon syllables are made. Examples are {qIrq}
and {pIqarD}.
+ `exclude from K-E` = This entry will not be included in the
Klingon--English side of the pocket dictionary. Words are only excluded
when they are present elsewhere in the dictionary, or when they are
understandable anyway. E.g. “number suffixes” are excluded because they
have their own reference table. Derived forms such as words ending in
{-moH} (when they do not differ from the expected meaning ({bolwI’}
is included, but {bolwI’} would not be, since it is
obvious frob {bol} + {-wI’} ).
* `id:` unique, permanent entry ID [REQUIRED]
The entry ID uniquely identifies an entry in the dictionary (even across
dictionary updates). IDs are guaranteed to be unique, and will not be
reused (i.e. the ID of a deleted entry will never re-appear in the
dictionary, unless the same dictionary entry is taken back). The ID of an
entry remain the same, even when the entry is otherwise modified.
The ID value is intentionally kept as short as possible, to facilitate
their use for both humans an machines. (We suggest writing `id:Qmp` when
using an ID in text, as this value can be pasted straight into the online
Klingon Pocket Dictionary to view the entry.)
ID values, written in base58, are always three characters long. Values that
look similar to Klingon words are disallowed (so as to avoid confusion).
This gives us: 58^3-(16*5*16) = 193,832 possible ID values -- far more than
is likely to ever be needed. (Base58 was chosen for clarity, it is also
used for Bitcoin addresses.)
* `meta:` meta comment about entry [OPTIONAL]
Editor’s comments on the entry. This is, for example, comments on how the
various sources have been combined to form the entry, concerns regarding
how to interpret the canon for the entry, or a FIXME if the entry is known
to need some additional work.
3. History
==========
Brief list of changes made for each VERSION of this file format. Most recent
changes first.
* 2012-11-21 v1.3 -- Added 'id:' field.
* 2012-11-02 v1.2 -- Added new supersection delimiting the database chunk
from the comments in the file (encompassing all other sections). Also added
`SHA1` metadata field.
* 2012-03-25 v1.1 -- Corrected misspelling ‘conjuction’ -> ‘conjunction’ in
`pos:` field. (This warranted a VERSION update since the content of this
field is exactly specified in the description -- had it been a free text
field, VERSION would not have been updated).
* 2012-03-24 v1.0 -- Added metadata header. Rewrote dictionary preamble to
clarify the file format.
4. Dictionary Consistency
=========================
To verify the internal consistency of the database use the `check-dict` program
available at . It is written in Perl,
and is typically run with:
usr/bin/check-dict /dev/null
Next comes the first database section.
== start-of-data ==
=== start-of-word-list ===
tlh: {bach} [1]
pos: verb
en:
sv: «skjuta»
def: TKD
ref: TKW p.148
cite: The verb used for ~shoot~ when referring to disruptors is {bach}.
Technically speaking, one shoots the energy beam from the disruptor.
The general word for any energy beam (~ray~) is {tIH}, so a disruptor's
beam is {nISwI' tIH}. Thus, the correct formation is {nISwI' tIH bach}
(~shoot the disruptor beam~). As a practical matter, however, the {tIH}
is often left out, and {nISwI' bach} is the common way to say ~shoot a
disruptor.~ Similarly, {pu' bach} is ~shoot a phaser.~ [KGT p.56]
tag: 1985; fighting; KLCP1
id: Qmp
tlh: {bach} [2]
pos: noun
en:
sv: «skott»
def: TKD
tag: 1985; fighting; KLCP1
id: Z8d
tlh: {bachHa'}
pos: verb
en: , make a [slang]
sv: «fela», göra ett «misstag» [slang]
def: KGT
ref: KLINW
pun: This is the first word in the K-E side of the dictionary, and is
incorrectly given as a noun. MO has confirmed this to be an intentional
error (since there is always an error somewhere, in every dictionary).
tag: 1997
id: yLa
meta: FIXME -- Should this word even be used? {Qagh} seem to mean the same
thing.
tlh: {bagh}
pos: verb
en:
sv: «knyta», «binda»
def: TKDa
tag: 1992
id: 3Do
tlh: {baghneQ}
pos: noun
en: «spoon»
sv: «sked»
def: 1998-05-05a-News
ref: KLINW
pun: Spoonerism on {nagh beQ} ~flat stone~.
tag: 1998; food
id: 8aq
tlh: {baH}
pos: verb
en: (torpedo, rocket, missile)
sv: «eld», «avfyra» (torped, raket, missil)
def: ST1; TKD
tag: 1979; fighting; KLCP1
id: Nh3
tlh: {baHjan}
pos: noun
en: «launcher»
sv: «eldrör», «avfyrningstub», «avfyrare»
def: BoP
ref: KLINW
tag: 1998
id: xi1
tlh: {baHwI'}
pos: noun
en:
sv: «skytt», «artillerist»
def: TKD
tag: 1985; fighting; KLCP1
data: derived form
id: WPq
tlh: {baj}
pos: verb
en: , for (actively)
sv: «tjäna», göra sig «förtjänt» av, «arbeta» för (aktivt)
def: TKW p.125; KGT
cite: {yInlu'taH 'e' bajnISlu'.} ~Survival must be earned.~ [TKW p.125]
cite: {yay chavlu' 'e' bajnISlu'.} ~Victory must be earned.~ [TKW p.125]
cite: {vuv be' 'e' baj} ~win the favor of a woman~ [KGT p.69]
tag: 1996
id: msr
tlh: {bal}
pos: noun
en: , ,
sv: «krus», «kanna», «kruka», «burk», «flaska»
def: KGT
tag: 1997
id: 848
tlh: {banan naH}
pos: noun
en: «banana»
sv: «banan»
def: TNK (2011-10-31-Email)
tag: 2011; food
data: phrase
id: 8pp
tlh: {bang}
pos: noun
en: , one who is loved, «beloved»
sv: «älskad», någon som är älskad, älskade
def: TKD
ref: TKW p.159
tag: 1985; KLCP1
id: R32
tlh: {bang «bom»}
pos: noun
en:
sv: «kärlekssång»
def: KGT
tag: 1997; music
data: phrase; derived form
id: adL
tlh: {bang «pong»}
pos: noun
en: «pet name»,
sv: «smeknamn», «ömhetsbetygelse»
def: KGT
tag: 1997
data: phrase; derived form
id: ehk
tlh: {baq}
pos: verb
en: ,
sv: «avsluta», «avbryta»
def: KGT
ref: HolQeD-12-2 p.9
cite: A duel ends, normally, with death. It is often the case, however, that
one of the combatants will have been outmaneuvered and will find
himself in a position from which he clearly cannot recover. Should this
occur, he will probably shout out {baq}, a clipped form of {yIbaq}
(~Terminate it!~). It is not normal in this context for him to shout
out something like {HIHoH} (~Kill me!~), even though this is what he
means. [KGT p.69]
tag: 1997
id: jMo
tlh: {baqghol}
pos: noun
en: type of , <~bahgol~>
sv: en slags «sprit», «~bahgol~»
def: KGT
tag: 1997; Klingonism
id: QHZ
tlh: [1] {baQ}
pos: verb
en: be , be just picked (fruit, vegetable)
sv: vara «färsk», vara «nyplockad» (om frukt, grönsak)
def: KGT
tag: 1997; food
id: HxN
tlh: [2] {baQ}
pos: verb
en: «~bat'leth~» from one hand to the other
sv: «kasta» en «~bat'leth~» från den ena handen till den andra
def: KGT
tag: 1997; fighting
id: KSB
tlh: {baQa'}
pos: exclamation
en: (general «invective»)
sv: (generellt «invektiv»)
def: TKDa 5.5/p.178
ref: KLINW
tag: 1992; curse
id: gJz
tlh: {barat}
pos: noun
en: «India»
sv: «Indien»
def: TNK (2011-10-29-Email)
tag: 2011; country
id: JFP
tlh: {bargh}
pos: noun
en: flat-bottomed for food preparation
sv: flatbottnad «skål» för matberedning
def: KGT
tag: 1997; food
id: 2Fk
tlh: {barot}
pos: name
en: «Barot»
sv: «Barot»
def: KGT p.182
cite: {tI'vIS barot puqloD} ~T'vis, son of Barot~ [KGT p.182]
tag: 1997; Klingonism
id: HoG
tlh: {baS}
pos: noun
en:
sv: «metall»
def: TKD
tag: 1985
id: znu
tlh: {baS «'In»}
pos: noun
en: «bell» (percussion instrument made of metal)
sv: «klocka» (slaginstrument gjort av metall)
def: KGT p.75
tag: 1997; music
data: phrase; derived form
id: Jym
tlh: {batlh} [1]
pos: adverbial
en: , with «honor», «honorably», «honorable»
sv: «ärofullt», med «ära», med «heder», «hedervärt»
def: TKD
ref: TKW pp.47, 71, 129
tag: 1985
id: Pc8
tlh: {batlh} [2]
pos: noun
en:
sv: «ära»
def: TKD
ref: TKW pp.53, 67; HolQeD-12-3 p.9; KLINW
cite: [...] {batlh}, on the other hand, is a grander, more general, more
philosophical concept, associated with integrity, rectitude, scruples,
and principles. [HolQeD-12-3 p.9]
see: {quv}
tag: 1985
id: D7p
tlh: {batlhHa'}
pos: adverbial
en:
sv: «skamligt», med «vanära»
def: TKW pp.55, 139; KGT
cite: {batlhHa' vanglu'taHvIS quv chavbe'lu'.} ~One does not achieve honor
while acting dishonorably.~ [TKW p.55]
cite: {Qu' buSHa'chugh SuvwI', batlhHa' vangchugh, qoj matlhHa'chugh, pagh
ghaH SuvwI''e'.} ~If a warrior ignores duty, acts dishonorably, or is
disloyal, he is nothing.~ [TKW p.139]
tag: 1996
id: KCa
tlh: {bav}
pos: verb
en:
sv: röra sig i en «omloppsbana» kring, «kretsa» kring
def: TKD
tag: 1985
id: LWF
tlh: {bay}
pos: noun
en: Klingon ~«{b}»~ sound
sv: klingonskans «{b}»-ljud
def: 2009-qep'a' (2009-07-27-Email)
tag: 2009
id: mi3
tlh: {ba'}
pos: verb
en:
sv: «sitta»
def: TKD
tag: 1985; KLCP1
id: wJM
tlh: {beb}
pos: noun
en: «roof»
sv: «tak», yttertak
def: 1998-12-07-News
ref: KLINW
cite: On occasion, though, the ceiling of the top floor is called {pa' beb},
literally ~room's roof~ (from {pa'} ~room~ plus {beb} ~roof~). The term
{beb} refers to the covering on top of a structure. [1998-12-07-News]
tag: 1998; architecture
id: 5kS
tlh: {beb mutlhwI'}
pos: noun
en: «roofer»
sv: «takläggare»
def: 2012-01-12-Email
tag: 2012; architecture
data: phrase
id: 68e
tlh: {bech}
pos: verb
en:
sv: «lida»
def: TKD
tag: 1985
id: yts
tlh: {begh}
pos: noun
en:
sv: «deflektorer»
def: TKD
tag: 1985
id: h38
tlh: {beH}
pos: noun
en:
sv: «gevär»
def: TKD
tag: 1985; fighting
id: Jpf
tlh: {bej} [.1]
pos: verb
en:
sv: «vaka» över, hålla ett öga på, «titta» på
def: TKD
ref: TKW p.19
tag: 1985; KLCP1
id: B1R
tlh: {bej} [.2]
pos: verb
en: be , be , be , be [slang]
sv: vara helt «säker», vara «viss» [slang]
def: KGT
tag: 1997
id: qUL
tlh: {bel} [1]
pos: verb
en: be
sv: vara «nöjd», vara «belåten»
def: TKD
tag: 1985; KLCP1
id: i5L
tlh: {bel} [2]
pos: noun
en:
sv: «välbehag», «nöje»
def: TKD
ref: TKW p.45
tag: 1985; KLCP1
id: KzM
tlh: {belHa'}
pos: verb
en: be
sv: vara «missnöjd», vara «missbelåten»
def: TKD
tag: 1985
data: derived form
id: f7j
tlh: {bem}
pos: noun
en:
sv: «fot«sula»»
def: KGT
tag: 1997; body part
id: M1L
tlh: {ben}
pos: noun
en: s ago,
sv: för ... «år» sedan, «år gammal»
desc: {loSmaH ben jIboghpu'} ~I'm 40 years old~ (lit. ~I was born 40 years
ago~); {cha'vatlh ben HIq} ~two century old ale~
def: TKD; PK; 1996-12-12a-News; KGT
cite: ~I will drink two century old ale.~ {cha'vatlh ben HIq vItlhutlh.} [PK]
cite: {vagh SanID ben buDbe' wamwI'pu'. ngugh Ho'Du'chaj lo' chaH, 'ach DaH
tajmey lo'.} ~5,000 years ago, hunters were not lazy. Then (at that
time) they used their teeth, but now they use knives.~
[1999-11-05-News]
com: Combinations with {ben} and quantity words other than numbers are often
seen on tlhingan-hol, even though canon support for them is (so far)
missing. E.g. {ben law'} ~many years ago~, {ben puS} ~[a] few years
ago~, {'op ben} ~some (unknown number of) years ago~.
pun: Igor/Aryeh pointed out [on tlhingan-hol] that the Hebrew word *ben*
~son~ is used when giving ages (for males); e.g. *Ani ben X* ~I am X
[years] old~, *Hu ben X* ~He is X [years] old~.
tag: 1985; time
id: iR9
tlh: [1] {bep}
pos: verb
en: ,