Unlocked Greek Lexicon Documentation

This site contains the official documentation for Door43’s Unlocked Greek Lexicon content creation.

Contents:

UGL Phase Goals

Phase 1 Goal

  • Proofread and edit the digital copy of Abbott-Smith’s Manual Greek Lexicon of the NT (A-S) to make it match the printed version

Phase 2 Goal

  • Update A-S to make it more usable for Bible translators so that speakers of English as a second language can use it, and so that it can be translated into other world languages (called LWCs [languages of wider communication] or GLs [gateway languages]) and used by mother-tongue translators of minority languages who can access those languages.

In keeping with that goal, we need to make the following changes to A-S:

  1. Translate and spell out all abbreviations, Latin or English (see Abbreviations)
  2. Update any archaic English
  3. Write definitions to accompany A-S glosses
  4. Delete any references to other English reference books (e.g. MM, Blass, Jannaris), since these will not be available to the users of our lexicon
  5. Make sure that the information from A-S is in the correct place in the markdown file. Examples include Glosses that were put in the Definition field or Explanation field. For reference, the PDF version of Abbott-Smith that was used to form the baseline for Phase 1 can be found at link.

Note

Explanation is optional data for Phase 2 of the project but is used for comments to explain a word’s usage.

The full syntax for these lemma files is defined in Markdown (see Markdown). Here is an example of a lemma file before and after editing:

BEFORE

# ἀπόστολος -ου, ὁ

<!– Status: S2=NeedsEdits –>

<!– Lexica used for edits: –>

## Word data

  • Strongs: G06520
  • Alternate spellings:
  • Principle Parts:
  • Part of speech:
  • Instances in Scripture: 80
  • All Scriptures cited: No

## Etymology:

[ἀποστέλλω]()),

  • LXX/Hebrew glosses:
  • Time Period/Ancient Authors:
  • Related words:
  • Antonyms for all senses:
  • Synonyms for all senses:

## Senses

### Sense 1.0:

#### Definition:

#### Glosses:

a fleet;

#### Explanation:

an expedition;

#### Citations:

a fleet, an expedition (Dem.).

### Sense 2.0:

#### Definition:

#### Glosses:

a messenger;

#### Explanation:

one sent on a mission;

#### Citations:

a messenger, one sent on a mission (Hdt., LXX, [[III Ki 14:6](1Ki 14:6)](1Ki 14:6), and [π.](); v. M, Pr., 37 f.; MM, s.v.; M, Th., i, 2:7 and reff.): [Jo 13:16](Jhn 13:16), [II Co 8:23](2Co 8:23), [Phl 2:25](Php 2:25).

### Sense 3.0:

#### Definition:

#### Glosses:

an Apostle;

#### Explanation:

#### Citations:

In NT, an Apostle of Christ

### Sense 3.1:

#### Definition:

#### Citations:

with special ref. to the Twelve: [Mt 10:2](Mat 10:2), [Mk 3:14](Mrk 3:14), [Lk [11](Gal 1:11):49](Luk 11:49), [Eph 3:5](Eph 3:5), [Re 18:20](Rev 18:20), al., equality with whom is claimed by St. Paul, [Ga 1:1](Gal 1:1), 11 ff, [I Ti 2:7](1Ti 2:7), a1.;

### Sense 3.2:

#### Definition:

#### Citations:

in a wider sense of prominent Christian teachers, as Barnabas, [Ac 14:14](Act 14:14), apparently also Silvanus and Timothy, [I Th 2:6](1Th 2:6), and perhaps Andronicus and Junias (Junia?), [Ro 16:7](Rom 16:7) (v. ICC, in l.); of false teachers, claiming apostleship: II Co [11](Gal 1:11):5, [13](2Co 11:13), [Re 2:2](Rev 2:2). (On the different uses of the term in NT, v. Lft., Gal., 92-101; Cremer, 530; DB, i, 126; DCG, i, 105; Enc. Br., ii, 196 ff.)

AFTER

# ἀπόστολος, ου, ὁ

<!– Status: S2=NeedsReview –>

<!– Lexica used for edits: BDAG, LN, BN, FFM –>

## Word data

  • Strongs: G06520
  • Alternate spellings:
  • Principle Parts:
  • Part of speech:

noun

  • Instances in the New Testament: 80
  • All Scriptures cited: No

## Etymology:

[ἀποστέλλω](../G06490/01.md),

  • LXX/Hebrew glosses:

LXX, [3Km 14:6](1ki 14:6)

  • Time Period/Ancient Authors:
  • Related words:
  • Antonyms for all senses:
  • Synonyms for all senses:

## Senses

### Sense 1.0:

#### Definition:

a group of ships sent on an expedition

#### Glosses:

a fleet; an expedition;

#### Explanation:

This meaning is not found in the NT

#### Citations:

<None>

### Sense 2.0:

#### Definition:

A person sent to deliver a message

#### Glosses:

a messenger; one sent on a mission;

#### Explanation:

#### Citations:

[John 13:16](jhn 13:16), [2Cor 8:23](2co 8:23), [Phil 2:25](php 2:25).

### Sense 3.0:

#### Definition:

a person chosen by Christ to represent him

#### Glosses:

an apostle;

#### Explanation:

This is a frequent use in the New Testament

#### Citations:

### Sense 3.1:

#### Definition:

one of those whom Christ chose and sent out as his representatives

#### Glosses:

#### Explanation:

#### Citations:

with special reference to the Twelve: [Matt 10:2](mat 10:2), [Mark 3:14](mrk 3:14), [Luke 11:49](luk 11:49), [Eph 3:5](eph 3:5), [Rev 18:20](rev 18:20), equality with whom is claimed by Saint Paul, [Gal 1:1](gal 1:1), [11](gal 1:11), [1Tim 2:7](1ti 2:7);

### Sense 3.2:

#### Definition:

someone sent out to represent Christ

#### Glosses:

#### Explanation:

#### Citations:

in a wider sense of prominent Christian teachers, as Barnabas, [Acts 14:14](act 14:14), apparently also Silvanus and Timothy, [1Thess 2:6](1th 2:6), and perhaps Andronicus and Junias (Junia?), [Rom 16:7](rom 16:7); of false teachers, claiming apostleship: [2Cor 11:13](2co 11:13), [Rev 2:2](rev 2:2).

Note

In this documentation, the term View mode (sometimes called markdown mode) refers to what is visible from the Door43 access to a specific .md file. When moving to the Edit mode, all lines of the file are visible to support editing. Using the Preview button will, temporarily, take you to View mode, to verify the displayed contents of your edits. The convention of enclosing data descriptions within curly brackets has been used for the discussion below.

Assignments

Issues

A Door43 Issue has been created for each letter of the Greek alphabet. An individual is assigned, or self-assigns themselves, to be responsible for editing all of the lemmas for that letter, using the Door43 Assignee field.

To work on an Issue

  • Click on Labels to add the blue In Progress label to that issue once you begin work on it. For each of these Issues the person responsible for review of that editing will be identified as a Door43 Participant. These Issues will be used to track the progress of the project at a top level.

Content

The project’s data files are all under the folder content. A subfolder for each Strong’s Plus ID (5 digits long) has been created which has a single file, 01.md, to store the lemma data.

Note

If you open the project’s content folder, you will be presented with an Index page with each of the over 6000 Strongs IDs shown. Selecting one will move you into the View mode for the given lemma.

To more easily access these individual lemma files

  • Open the ugltoc.md file in the templates folder for a list of the Table of Contents (TOC) files for each letter, or
  • Open one of the letter’s TOC files: templates/{Greek letter}/{Greek letter}toc.md, e.g. templates/alpha/alphatoc.md .

In the file ugltoc.md, four columns exist for each letter which have links to the 4 different TOC files for each letter, where each of these will supply links to the associated lemma files for that letter:

  • The Instances column for the TOC file with links to words sorted by their instance count. This TOC file, alone, also has a link, labeled refs, for each lemma to a separate page that lists every instance of that lemma, and this in our Project’s standard Scripture reference format.
  • The Word Sort column for the TOC file with links to words sorted by their Strong’s Plus ID
  • The Undefined column for the TOC file with links to the lemmas that were assigned a temporary, undefined Strong’s Plus ID
  • The Inserted column for the TOC file with links to the lemmas which Alan Bunning has pre-assigned for instances that were not in the Abbott-Smith lexicon.

For example, for the letter Alpha:

Once you have been assigned a letter for editing, you should begin your task using the associated Word Sort TOC file, working through the associated lemmas from most frequently used to less frequently used.

Note

These TOC files do not include the lemmas for each letter which were Inserted by Alan Bunning, nor do they include the Undefined lemmas for each letter that were assigned at the project’s file creation time. See the discussion below.

When you have finished your edits, or finished for the day, for a lemma file you should Commit your changes, leaving the bullet checked for “commit directly to the master branch”. If you are at a point where you want to have the lemma file checked for syntax, send an email to Dave Statezni providing him the Strong’s Plus ID. He will then run the syntax checker against your file with the results from that checker emailed directly to you for review. When you have finished the edits for one or more lemma files (see Markdown), you will need to create a Pull Request (see Creating a Pull Request). When that change has been merged into the main repository by one of the project’s administrators, the syntax checker will automatically be run against any changes for that day and email the results back to the originator of the change. Once you have completed editing for all lemmas in the Word Sort TOC file for a letter, you will need to move to the associated Inserted and Undefined TOC files to complete all of the work for each letter.

Each letter’s TOC files list all of its lemmas across and then down, showing both the Greek word and the Strong’s Plus ID.

At the top of each file are links back to the UGL TOC file and to one of the other TOC files for that letter, e.g. the Word Sort TOC files have links to their associated Undefined {Greek letter} TOC file, e.g. templates/alphaundeftoc.md.

The latter of these also appears at the bottom of the file, along with a link back to the top of the file. For each letter there are a set of lemmas from the Abbott-Smith lexicon and its parsing that did not have a Strong’s ID, had multiple Strong’s IDs, or had a letter appended to the Strong’s ID. These were arbitrarily assigned a Strong’s Plus ID greater than G99000. As editor for a letter, part of your responsibility is to identify (and possibly create) the Strong’s Plus ID (5 digits long) for each of these. Once that data has been added, plus any other data needed to complete the lemma file for these Undefined Strong’s Plus IDs, you should then follow the steps for  Creating a New Lemma file.

Note

The Strong’s Plus ID referenced above was initially developed by Alan Bunning, where he took the 4-digit Strong’s ID and appended a zero to create a 5-digit ID. This gave him extra IDs to be able to qualify different word forms than the standard Strong’s. We will be using this Strong’s Plus identification for this project.

Markdown

The lemma files for en_ugl are defined in Markdown format. This format/language is a convenient means to specify the desired format of the visual output for the project. When you select a lemma file on the DCS web you will see this visual form, though the final, published, visual form may be slightly different. When editing a file, you will be working in the Markdown language environment. This document will endeavor to specify the required Markdown format and content of each lemma file to achieve the project-desired output, consistently across all lemmas for all editors. Markdown is blank line sensitive which means that data within a marker can be entered on multiple consecutive lines and will be merged together from a syntax checking and the visual output perspective. A blank line must be entered between data lines to have that data treated as separate from a syntax checking and the visual output perspective. Markdown also provides a way to add emphasis to data that is entered. Text that is enclosed within a single “*” or a single “_” will be italicized. Text that is enclosed within double “*” or double “_” will be displayed bold. These can be combined to achieve both forms of emphasis. The following example will be displayed as below.

This **bold data**
is entered *with italics* on
multiple consecutive lines

This bold data is entered with italics on multiple consecutive lines

Syntax Checker

A Syntax Checker has been developed to read a lemma markdown file and determine whether it meets the requirements of this document. A change log for that Syntax Checker script, in the form of a Google Doc, can be found at this link

Markers

The Markdown format is achieved with the use of markers (marker lines). Any line which starts with a pound sign, “#” or an asterisk, “*”, is considered a marker. Apart from the first line, there must be at least one blank line before and after each marker. These markers should not be altered or reordered so that consistency across the project can be maintained. Only 4 of these markers allow/require data to be entered as part of the actual marker line. These are:

  1. * Strongs: <Strongs-plus identifier>, see Strongs , below.
  2. * Instances in the New Testament: <instance count>, see Instances Count , below.
  3. * All Scriptures cited: “Yes” or “No”, see All Scriptures cited , below.
  4. ### Sense <sense number>:, see Sense , below.

Note

As was discussed in the Content section, there is a link labeled refs for each lemma in its Greek letter Instance Table of Contents web page which provides a list, in our project’s format, of each of the references to that lemma.

References

UGL Markers

The UGL markers will be identified below. They should remain as entered and they should not be reordered. An example follows this discussion.

1. # <Greek lemma>

The first line of each lemma file is a marker identifying its lemma. The initial format which came from the originating Abbott Smith lexicon uses a dash before the second term. For consistency and alignment with newer lexica, change these to replace the <space>– with ,<space>. This line should be terminated with a period. e.g.

# ἄμφοδον -ου, το

should be changed to:

# ἄμφοδον, ου, το.

2. Comment Markers

Markdown does support specification of comments. Lines 3 and 4 of each lemma file have two comment lines. They start with “<!—“ and end with “–>”. This format specifies non-visible comments, that is comments that are in the lemma file but are not shown in the visual form. These two comment lines must remain in the file as entered:

<!-- Status: S2=NeedsEdits -->

<!-- Lexica used for edits:   -->
Editing for the first of these is only allowed for the value given to S2 (Stage 2 of project) and for the specification of the lexica that were used for editing the file, in the second comment. The valid values for S2 are:
  • NeedsEdit {initial value when you start editing}
  • NeedsReview {value you must enter before performing the git commit for your edits}
  • NeedsFinalCheck {Reviewer enters this when 1st Review is complete}
  • ReadyforPublication {Final Reviewer enters this when Final Check/2nd Review is complete}

The list of lexica should be entered as abbreviations per the list shown in the Lexica section.

3. ## Word data

This is a content/format marker with only other markers associated with it, so no data should be entered for it. .. Requirement 3.1 Marker required with one or more preceding and folowing blank lines, no data, and no terminator

4. * Strongs: Gddddd.

Identifies the Strong’s-Plus ID, with the 5-digit ddddd notation, for the lemma and was generated by the lemma file creation tool and should remain unchanged with the exception of adding a terminating period.

5. * Alternate spellings

This is the first marker where editing is allowed to add data to supply any variant or alternative spellings identified in the referenced lexica. This data should be entered as simple Greek text with no surrounding bracketing or parenthesis as discussed in Greek Lemma Link for referencing other Greek lemmas from this file, since that reference would point back to the current lemma file. Each instance that is specified should be separated with a comma. No additional data is required but any needed textual narrative for an instance should be separated from the Greek by a semicolon. If data is present it should data be terminated with a period.

6. * Principle Parts:

This marker should be left empty for this Stage of the project.

7. * Part of speech:

This marker’s data should contain all of the Part of speech (POS) instances that are found in the UGNT. This data will be provided to each editor as a text file for each Greek letter. Within each file is a sorted list of the Strong’s-Plus IDs with their associated POS data provided in the required link format to the correlative UGG section. The appropriate lines in that file can then be copied and then pasted into the POS marker section. This can be one or more lines which should have intermediate lines ending in a comma and the final line ending in a period.

Requirement 7.1 Marker required with one or more preceding and folowing blank lines. Requirement 7.2 Multiple instances must be separated by a comma Requirement 7.3 The final entry should be termianted in a period Requirement 7.4 Each instance must be formated as: [<UGG Chapter title>](<Web Link to UGG chapter>)

8. * Instances in the New Testament: <count>

This count value should be left as-is since that instance count was based upon the data from the UGNT. The text for this marker may erroneously be Instances in Scripture or Instances in the NT and should be updated to be Instances in the New Testament. This should be terminated with a period.

9. * All Scriptures cited: Yes/No

This marker should be followed with the word Yes or No, indicating whether every instance count reference appears in one of more of the data sections for the 21. #### Citations:, below. This line should be terminated with a period.

10. ## Etymology:

This marker’s data should contain any Greek Lemma Link that is explaining compound words or is explaining some names and places. Any usage in Abbott-Smith of the symbol “<” to designate words that are “derived from or related to” the lemma or any similar identification in other lexica should be moved to 13. * Related words:, below. Where present this data should be terminated with a period.

11. * LXX/Hebrew glosses:

This marker’s data should contain any associated data that was propagated from the A-S lexicon. That propagation may have placed this data under other markers in this file, and if so, it should be moved back to this marker’s data. There may be no LXX/Hebrew gloss data for a given lemma file. Remove or expand any abbreviations that may remain and check the format for all scripture references against Scripture Links. The LXX book references from Abbott-Smith were generally in the format <LXX book>.<chapter>.<verse>. These should be reformatted to reflect the documented reference format for the USFM Names portion of these UGL documents. An LXX/Hebrew gloss contains, at a minimum, a Scripture link and/or a Hebrew lemma link. A space should be used to separate these two if both are present for a single LXX/Hebrew gloss instance. Each instance must be separated from other instances by a comma, even if one instance has only a Hebrew lemma link, one instance has only a Scripture link, or one instance has both links. Each of these comma-separated instances may have leading textual narrative/discussion which must be preceded by a semicolon (;). No special punctutation is needed to transition from this narrative text to one or both of the links for this instance. Where present this data should be terminated with a period. Examples of the different forms of this data are:

{Scripture links only}
  [Exod 22:11](exo 22:11), [10](exo 22:10), [Amos 3:3](amo 3:3), [4](amo 3:4).

   {Scripture and Hebrew links with leading narrative}
         ;in LXX [Num 24:2](num 24:2) [ראה](//en-uhal/H7200), [Job 10:4](job 10:4), [39:26](job 39:26).

   {Scripture and Hebrew links with leading narrative and trailing gloss}
         ;in LXX [Num 24:2](num 24:2) [ראה](//en-uhal/H7200) : to see, [Job 10:4](job 10:4), [39:26](job 39:26).

    {Hebrew link only with leading narrative and trailing gloss}
         ;in LXX chiefly for [רעע](//en-uhal/H7489) : evildoer.

    {2 instances of Hebrew links only with leading narrative and trailing gloss}
    ;in LXX chiefly for [רעע](//en-uhal/H7489) : evildoer, ;in LXX also for [רֹעַ](//en-uhal/H7455) : evil.

12. * Time Period/Ancient Authors:

This marker should have no data supplied for this stage of the project.

14. * Antonyms for all senses:

This marker’s data should contain any other Greek lemmas that are identified by the other lexica as antonyms. These should be formatted per Greek Lemma Link, above. Project time and schedule does not give us the freedom to perform our own research on this topic so we must rely solely upon the other lexica. Any Greek lemma reference identified by other lexica that is not a UGL-defined lemma should be omitted from this lexicon. To determine if a lemma is a UGL-defined lemma you will need to open up the associated Greek letter’s Word Sort TOC file, as discussed in http://ugl-info.readthedocs.io/en/latest/assignments.html#Tomoreeasilyaccesstheseindividuallemmafiles . The lemma must appear in that TOC file to be a UGL-defined lemma and if so, you can see the Strongs-Plus ID for it. Multiple links should be separated by a comma. A period should terminate this data when present.

15. * Synonyms for all senses:

This marker’s data should contain any other Greek lemmas that are identified by the other lexica as synonyms. These should be formatted per Greek Lemma Link, above. Project time and schedule does not give us the freedom to perform our own research on this topic so we must rely solely upon the other lexica. Any Greek lemma reference identified by other lexica that is not a UGL-defined lemma should be omitted from this lexicon. To determine if a lemma is a UGL-defined lemma you will need to open up the associated Greek letter’s Word Sort TOC file, as discussed in To more easily access these individual lemma files . The lemma must appear in that TOC file to be a UGL-defined lemma and if so, you can see the Strongs-Plus ID for it. Multiple links should be separated by a comma. A period should terminate this data when present.

16. ## Senses:

The only permitted data for this marker is one or more Sense markers with their associated sub-markers. Editors should start with the structure and content embedded in the files from the Abbott-Smith lexicon. After review and analysis of the sense data from the other lexica this Abbott-Smith starting point can be expanded with additional sense and sub-sense markers, can be down-sized with the removal of sense and sub-sense markers, and/or merely modified to update the Definitions and/or Glosses with the same number of sense and sub-sense markers.

17. ### Sense <sense number>:

The only permitted data for this marker is the in-line Sense number with a colon as the line terminator and the four sense sub-markers with their associated data. The sense number starts at 1.0 and increments at the decimal digit, the number preceding the decimal point, for each significant sense and increments at the fractional level to differentiate sub-senses of each significant sense. The sense number, and thus the senses, can vary from a single sense with the number 1.0, to complex sub-senses which could be in the form, 3.8.5, which would be the third significant sense, it’s eighth sub-sense, and that sub-sense’s fifth sub-sub-sense. It is recommended that you limit your sense levels to only two decimal digits as, 2.4, but three levels is the maximum, if required for completeness and accuracy. These sense numbers must occur in numerical order in the file, with no missing intermediate numbers; ### Sense 2.4 followed by ### Sense 2.6 would be flagged as a syntax error, since ###Sense 2.5 is missing. Every ### Sense marker is followed only by sub-markers, with no data specified for this marker. Each of the following sub-markers must be present and in the prescribed order given below.

Note

Many lexica use a sense numbering system that includes letters and possibly Greek letters, e.g. 1bα. This lexicon will use only numbers for each of the level of senses appropriate for the lemma, with a decimal point separating the sense from the sub-sense and then the sub-sub-sense numbers.

18. #### Definition:

This marker’s data should contain the top-level definition for this Sense. It can be expressed as a full sentence or as a clause with multiple instances separated by a comma. Narrative text and/or Sense Link can be provided and must follow its associated definition data instance with a semicolon. No termination mark should be entered. Some examples of this clausal form are:

Aromatic substance burned as incense, An altar for burning incense

To burn incense as an offering to a deity; this does not always refer to an incense offering to Yahweh, to burn incense on an altar

19. #### Glosses:

This marker’s data should contain one or more one-word meanings for this sense. Multiple instances should be separated by a comma. Any narrative text and/or Sense Link should follow its associated gloss data instance with a semicolon. No termination mark should be entered.

20. #### Explanation:

This marker’s data should be left empty for this Stage of the project, unless there is discussion needed to explain the context of the Definition and/or Glosses. Multiple instances should be separated by a comma. No termination mark should be entered.

21. #### Citations:

This marker’s data should contain each Scripture reference associated with this sense of the lemma. For a sense with many references, you may choose a subset of those that you believe would be most beneficial for the users of this lexicon. Omitting some for the sake of brevity would be the reason to specify No for the 9. * All Scriptures cited: Yes/No . Each citation instance must be made up of only one Scripture Links, defined above. Optionally a citation instance can be preceded by a narrative discussion or by either or both of the actual UGNT Greek text and an English translation, the latter should be suffixed with the translation source identified as three to four capital letters enclosed in parenthesis: e.g. (ULT),(NASB),(ESV),or (NIV). If narrative discussion is entered this should be preceded with a tilde, “~” and terminsted by a colon, “:”. This narrative discussion may include a single Greek Lemma Link or a single Hebrew Lemma Links but these must follow their documented syntax. An exception to this is that this Greek lemma link does not require a gloss or definition, but if it is present, it should be preceded by a comma, and not a colon as in the standard form. If a gloss or definition for a Hebrew lemma link is provided, it should be preceded by a comma, and not a colon as in its standard form. If any narrative discussion is entered it should precede its assocaited UGNT text or English translation. A semicolon must precede the UGNT text as well as the English translation, if entered. It should be noted that if the UGNT text is entered it would be most beneficial for the downstream translators to have this Greek entered in Greek lemma link format to support hotlinks to the lemmas for each of those Greek words. For this case of entering Greek lemma links, no gloss/definition data should follow each link. Also, where the current Greek lemma occurs within that UGNT text, that Greek word should not be in Greek lemma link format since that hotlink would send the translator back to the current lemma file. It should be entered as simple Greek text. If any or all of these three preceding data pieces are entered they should be separated from their Scripture link with a colon. It should be noted that any narrative discussion is terminated by either a semicolon if there is inserted UGNT and/or English translation or by a colon if neither of these is inserted. To not overburden the translators and not have a congested file, the UGNT text and English translation should be entered for only the first citation link instance. Multiple citation instances must be separated by a comma. No termination mark should be entered for this data except for the citation data of the last Sense level in the lemma file. For this last citation data in the file, it should be terminated with a period. As discussed in 8. * Instances in the New Testament:, above, annotations to this citation data should be made to identify which references have more than 1 instance of this lemma. This identification must be enclosed within curly brackets “{}”. It may be just standard textual narrative or it may include one or more Sense links. As with other marker data, this data can span multiple, consecutive, lines in the file with no blank lines between them. Examples of the format for this annotation are:

   {Under Sense 1.0 of lemma καινός, G25370}
[Luke 5:36](luk 5:36){3 instances, all for this Sense}

  {Under Sense 2.0 of lemma καινός, G25370}
[Rev 3:12](rev 3:12){2 instances, both for this Sense}

   {Under Sense 4.0 of lemma καλέω, G25640 where the passage is not cited in any other Sense Citation data}
[Rom 8:30](rom 8:30){2 instances, one(1) for this Sense, one(1) not cited}

   {Under Sense 1.0 of lemma κἄν, G25790}
[Luke 12:38](luk 12:38){2 instances, one(1) for this Sense and one(1) for [Sense 2.0](#sense-20)}
   {Under Sense 2.0 of lemma κἄν, G25790}
[Luke 12:38](luk 12:38){2 instances, one(1) for this Sense and one(1) for [Sense 1.0](#sense-10)}

    Example with preceding narrative discussion only, without a Greek or Hebrew lemma link:
~Gabbatha, the Greek transliteration of an uncertain Aramaic word: [John 19:13](jhn 19:13)

    Example with preceding narrative discussion only, which includes a Greek lemma link without a gloss:
~Gabbatha, the Greek transliteration of an uncertain Aramaic word used as the equivalent of [λιθόστρωτον](../G30380/01.md): [John 19:13](jhn 19:13)

    Example with preceding narrative discussion only, which includes a Greek lemma link with a gloss:
~Gabbatha, the Greek transliteration of an uncertain Aramaic word used as the equivalent of [λιθόστρωτον](../G30380/01.md), stone pavement: [John 19:13](jhn 19:13)

    Example with preceding UGNT and English Translation, only:
;[καὶ](../G25320/01.md) [γὰρ](../G10630/01.md) [ὁ](../G35880/01.md) [θεὸς](../G23160/01.md) [ἡμῶν](../G14730/01.md) [πῦρ](../G44420/01.md) καταναλίσκον,
;"For our God is a consuming fire." (ULB)
:[Heb 12:29](heb 12:29)

    Example with preceding narrative discussion, UGNT, and English Translation:
~This addresses a significant aspect of God:
;[καὶ](../G25320/01.md) [γὰρ](../G10630/01.md) [ὁ](../G35880/01.md) [θεὸς](../G23160/01.md) [ἡμῶν](../G14730/01.md) [πῦρ](../G44420/01.md) καταναλίσκον,
;"For our God is a consuming fire." (ULB)
:[Heb 12:29](heb 12:29)

Example Markdown file:

# κακῶς.

<!-- Status: S2=NeedsReview -->
<!-- Lexica used for edits: BDAG, FFM, LN, A-S -->

## Word data

* Strongs: G25600.

* Alternate spellings:

* Principle Parts:

* Part of speech:

[Adverb](http://ugg.readthedocs.io/en/latest/adverb.html).

* Instances in the New Testament: 16.

* All Scriptures cited: Yes.

## Etymology:

* LXX/Hebrew glosses:

* Time Period/Ancient Authors:

* Related words:

[κακός](../G25560/01.md): bad, evil.

* Antonyms for all senses:

* Synonyms for all senses:

## Senses

### Sense 1.0:

#### Definition:

Suffer physical harm

#### Glosses:

#### Explanation:

#### Citations:

### Sense 1.1:

#### Definition:

Suffer physical harm without identifying magnitude

#### Glosses:

ill, sick

#### Explanation:

#### Citations:

[καὶ](../G25320/01.md) [ἀπῆλθεν](../G05650/01.md) [ἡ](../G35880/01.md) [ἀκοὴ](../G01890/01.md) [αὐτοῦ](../G08460/01.md) [εἰς](../G15190/01.md) [ὅλην](../G36500/01.md) [τὴν](../G35880/01.md) [Συρίαν](../G49470/01.md) [καὶ](../G25320/01.md) [προσήνεγκαν](../G43740/01.md) [αὐτῷ](../G08460/01.md) [πάντας](../G39560/01.md) [τοὺς](../G35880/01.md) κακῶς [ἔχοντας](../G21920/01.md) [ποικίλαις](../G41640/01.md) [νόσοις](../G35540/01.md) [καὶ](../G25320/01.md) [βασάνοις](../G09310/01.md) [συνεχομένους](../G49120/01.md) [καὶ](../G25320/01.md) [δαιμονιζομένους](../G11390/01.md) [καὶ](../G25320/01.md) [σεληνιαζομένους](../G45830/01.md) [καὶ](../G25320/01.md) [παραλυτικούς](../G38850/01.md) [καὶ](../G25320/01.md) [ἐθεράπευσεν](../G23230/01.md) [αὐτούς](../G08460/01.md)
"The news about him went out into all of Syria, and the people brought to him all those who were sick, ill with various diseases and pains, those possessed by demons, and the epileptic and paralytic. Jesus healed them." (ULB)
[Matt 4:24](mat 4:24),  [Matt 8:16](mat 8:16),  [Matt 9:12](mat 9:12),  [Matt 14:35](mat 14:35),  [Mark 1:32](mrk 1:32),  [Mark 1:34](mrk 1:34),  [Mark 2:17](mrk 2:17),  [Mark 6:55](mrk 6:55),  [Luke 5:31](luk 5:11),  [Luke 7:2](luk 7:2)

### Sense 1.2:

#### Definition:

Suffer physical harm and identifying its magnitude

#### Glosses:

suffer severely

#### Explanation:

#### Citations:

[καὶ](../G25320/01.md) [ἰδοὺ](../G37080/01.md) [γυνὴ](../G11350/01.md) [Χαναναία](../G54780/01.md) [ἀπὸ](../G05750/01.md) [τῶν](../G35880/01.md) [ὁρίων](../G37250/01.md) [ἐκείνων](../G15650/01.md) [ἐξελθοῦσα](../G18310/01.md) [ἔκραζεν](../G28960/01.md) [λέγουσα](../G30040/01.md) [Ἐλέησόν](../G16530/01.md) [με](../G14730/01.md) [κύριε](../G29620/01.md) [υἱὸς](../G52070/01.md) [Δαυείδ](../G11380/01.md) [ἡ](../G35880/01.md) [θυγάτηρ](../G23640/01.md) [μου](../G14730/01.md) κακῶς [δαιμονίζεται](../G11390/01.md)
'Behold, a Canaanite woman came out from that region. She shouted out and said, "Have mercy on me, Lord, Son of David! My daughter is severely demon-possessed."' (ULB)
[Matt 15:22](mat 15:22),  [Matt 17:15](mat 17:15),  [Matt 21:41](mat 21:41)

### Sense 2.0:

#### Definition:

To be morally evil

#### Glosses:

wickedly, speak wrongly

#### Explanation:

#### Citations:

[ἀπεκρίθη](../G06110/01.md) [αὐτῷ](../G08460/01.md) [Ἰησοῦς](../G24240/01.md) [Εἰ](../G14870/01.md) κακῶς [ἐλάλησα](../G29800/01.md) [μαρτύρησον](../G31400/01.md) [περὶ](../G40120/01.md) [τοῦ](../G35880/01.md) [κακοῦ](../G25560/01.md) [εἰ](../G14870/01.md) [δὲ](../G11610/01.md) [καλῶς](../G25730/01.md) [τί](../G51010/01.md) [με](../G14730/01.md) [δέρεις](../G11940/01.md)
"Jesus answered him, "If I spoke wrongly, testify about the wrong, but if rightly, why do you hit me?"" (ULB)
[John 18:23](jhn 18:23),  [Acts 23:5](act 23:5),  [Jas 4:3](jas 4:3).

Valid part of speech, POS, entries:

The following is a list of the valid values for Textual Representation and their corresponding UGG Filename. See the UGG for clarification.

Textual representation UGG filename
Noun noun
Adjective used substantively as a Noun noun_substantive_adj
Adjective used predicatively as a Noun noun_predicate_adj
Proper noun_indeclinable proper_noun_indeclinable;
Adjective adjective
Adjective ascriptive adjective_ascriptive
Adjective restrictive adjective_restrictive
Determiner determiner
Determiner article determiner_article
Determiner demonstrative determiner_demonstrative
Determiner differential determiner_differential
Determiner possessive determiner_possessive
Determiner quantifier determiner_quantifier
Determiner number determiner_number
Determiner ordinal determiner_ordinal
Determiner relative determiner_relative
Determiner interrogative determiner_interrogative
Pronoun pronoun
Pronoun demonstrative pronoun_demonstrative
Pronoun personal pronoun_personal
Pronoun reflexive pronoun_reflexive
Pronoun reciprocal pronoun_reciprocal
Pronoun indefinite pronoun_indefinite
Pronoun relative pronoun_relative
Pronoun interrogative pronoun_interrogative
Verb verb
Verb transitive verb_transitive
Verb intransitive verb_intransitive
Verb linking verb_linking
Verb modal verb_modal
Verb periphrastic verb_periphrastic
Interjection interjection
Interjection exclamation interjection_exclamation
Interjection directive interjection_directive
Interjection response interjection_response

Working with Door43 Git Service

Forking the repository

Before you begin working on creating or modifying files in one of the the Unlocked Lexicon repositories, you will need to fork the project’s repository.

  1. Sign in to your Door43 account at https://git.door43.org/.
  2. Click Fork near the upper right-hand corner of the site.
  3. In the New Fork Repository window, keep the default Repository Name and Description and click on the Fork Repository button.

Note

Once you have forked the repository, you will need to work from the files on your fork only. Once you have committed changes to a file on your fork and it is free of syntax errors, you are ready to merge those changes to the Master repo. To do this you will need to create a Pull Request.

Creating a Pull Request

When you have completed work on a file and are ready for it to be reviewed and merged to the master repository, you will need to create a Pull Request that will be reviewed by another team member before being merged to the master repo.

  1. On the master repository site, click on Pull Requests near the top of the page, then click on the New Pull Request button. The site will compare your fork with the master repository and show differences at the bottom of the page.
  2. Add a title and a description that explain the changes you want to merge to the master repository.
  3. Click Create Pull Request.

Merging a Pull Request

Pull requests will show up near the top of the main repository page.

  1. Click on Pull Requests to see what needs to be reviewed and then merged with the master repository.

Note

Only review and merge content from another contributor, not your own content.

  1. View the file to review the content.
  2. If the content is accurate, merge the Pull Request with the master repository.

Closing Issues

After all of your Pull Requests for an Issue (Greek letter) have been reviewed and merged into the master repository, you can mark your Issue closed and remove the In Progress label from the issue.

Creating a New Lemma file

A new lemma file can be created from an existing lemma file by following the steps below:

  1. Move to the existing lemma file in Door43.
  2. Mentally remember the new Strong’s Plus ID.
  3. Click the Raw option icon.
  4. Select every line and then use the Copy feature (pull-down menu or Ctrl-C).
  5. Click the Browser Back icon.
  6. Click the Files tab and then the Contents tab (this will take a while).
  7. Click the blue New File button.
  8. Paste the contents of the previous file into the area below “<> New File”.
  9. In the blank field to the right of “en-ugl / content / ” enter the new Strong’s Plus ID, followed by “/01.md”, e.g. “G45555/01.md” and click Commit Changes.
  10. It will take approximately one day for this new lemma file to appear in the letter’s toc file, and for the old undefined ID to be removed from the letter’s undefined toc.

Abbreviations

Following are abbreviations to use for various resources.

Abbott-Smith General Abbreviations

  • absol. = absolute
  • acc. = accusative
  • act. = active
  • ad fin. = ad finem (to the end)
  • adj. = adjective
  • adv. = adverb
  • al. = alibi (elsewhere)
  • aor. = aorist
  • Apocr. = Apocrypha
  • App. = Appendix
  • Aram. = Aramaic
  • Att. = Attic
  • bibl. = biblical
  • bis = twice
  • c.= cum (with)
  • cf. = confer (compare)
  • cl.= classics, classical
  • cogn. = cognate
  • compar. = comparative
  • contr. = contracted
  • dat. = dative
  • e.g. = exempli gratia (for example)
  • eccl. = ecclesisastical
  • esp. = especially
  • ex. = example
  • exc. = except
  • f.= and following (verse)
  • ff. = and following (verses)
  • fig. = figurative
  • freq. = frequent
  • fut. = future
  • gen. = genitive
  • Gk. = Greek
  • Heb. = Hebrew
  • i.e. = id est (that is)
  • ib. = in the same place
  • id. = the same
  • impers. = impersonal
  • impf. = imperfect
  • impv. = imperative
  • in l. = in loco (in place)
  • indic. = indicative
  • inf. = infinitive
  • infr. = infra (below)
  • Ion. = Ionic
  • l.c. = loco citato (in the place cited–footnote or endnote)
  • m.= masculine
  • metaph. = metaphorically
  • meton. = metonymy
  • MGr. = Modern Greek
  • n.= note, neuter
  • neg. = negative
  • nom. = nominative
  • om. = omit, omits
  • opp. = opposed to
  • optat. = optative
  • pass. = passive
  • pers. = person
  • pf. = perfect
  • plpf. = pluperfect
  • prep. = preposition
  • prop. = properly
  • ptcp. = participle
  • q.v. = quod vide (see, go to see)
  • rei = of the thing
  • s.= sub (under, below)
  • s.v. = sub voce (under the word or heading given)
  • sc. = scilicet (that is)
  • seq. = sequente (followed by)
  • subjc. = subjunctive
  • subst. = substantive
  • superl. = superlative
  • supr. = supra (above, from a previous reference)
  • syn. = synonym
  • Targ. = Targum
  • v.= vide (see, consult)
  • vb. = verb
  • v.l. = variant reading
  • v.s. = vide sub (see below)

Abbott-Smith Versions and Editions Abbreviations

  • Al = anon. version quoted by Origen
  • Aq = Aquila
  • AV = Authorized version
  • B = Beza
  • E = Elzevir
  • EV = English version (AV and RV)
  • Gr Ven = Graecus Venetus
  • L = Lachmann
  • LXX = Septuagint
  • R (in LXX refs) = Sixtine Ed of LXX (1587)
  • Rec = Received Text
  • RV = Revised Version
  • R, txt, mg = RV text, margin
  • Sm = Symmachus
  • T = Tischendorf
  • Th = Theodotion
  • Tr = Tregelles
  • Vg = Vulgate
  • WH = Westcott and Hort

Abbott-Smith Ancient Writers Abbreviations

  • Ael = Aelian, 2 AD
  • Aesch = Aeschylus, 5 BC
  • Aeschin = Aeschines, 4 BC
  • Anth = Anthology
  • Antonin = Marcus Aurelius Antoninus, 2 AD
  • Apoll Rhod = Apollonius Rhodius, 2 AD
  • Arist = Aristotle, 4 BC
  • Aristoph = Aristophanes, 5 BC
  • Ath = Athanasius, 4 AD
  • CIG = Corpus Inscriptionum Graecarum
  • Dio Cass = Dio Cassius, 2 AD
  • Diod = Diodorus Siculus, 1 BC
  • Diog Laert = Diogenes Laertius, 2 AD
  • Dion H = Dionysius of Halicarnassus
  • Diosc = Dioscorides, 1-2 AD
  • Eur = Euripides, 5 BC
  • Eustath = Eustathius, 12 AD
  • FlJ = Flavius Josephus, 1 AD
  • Greg Naz = Gregory of Nazianzus, 4 AD
  • Hdt = Herodotus, 5 BC
  • Heliod = Heliodorus, 4 AD
  • Herm = Hermas, 2 AD
  • Hes = Hesiod, 9 BC?
  • Hipp = Hippocrates, 5 BC
  • Hom = Homer, 9 BC?
  • Inscr = Inscriptions
  • Luc = Lucian, 2 AD
  • Lys = Lysias, 5 BC
  • Menand = Menander, 4 BC
  • π = Papyri
  • Paus = Pausanias, 2 AD
  • Phalar = Phalaris, Spurius Epp.
  • Philo = Philo Judaeus, 1 AD
  • Pind = Pindar, 5 BC
  • Plat = Plato, 5-4 BC
  • Plut = Plutarch, 2 AD
  • Polyb = Polybius, 2 BC
  • Socr, HE = Socrates, Historia Ecclesiastica, 5 AD
  • Soph = Sophocles, 5 BC
  • Strab = Strabo, 1 BC
  • Test Zeb = Testimony of Zebedee, 2 AD
  • Theogn = Theognis, 6 BC
  • Theophr = Theophrastus, 4 BC
  • Thuc = Thucydides, 5 BC
  • Xen = Xenophon, 5-4 BC

Lexica

These are the abbreviations to use when listing which lexica have been referenced:

BDAG

Bauer, Walter. A Greek-English Lexicon of the New Testament and Other Early Christian Literature. Edited by Frederick W. Danker. 3rd ed. Chicago: University of Chicago Press, 2000

LN

Louw, Johannes E., and Eugene A. Nida. Greek-English Lexicon of the New Testament: Based on Semantic Domains. 2 vols. 2nd ed. New York: United Bible Societies, 1989

FFM

Friberg, Timothy, Barbara Friberg, and Neva F. Miller. Analytical Lexicon to the Greek New Testament. Baker’s Greek New Testament Library. Grand Rapids: Baker, 2000

BN

Newman, Jr., Barclay M. A Concise Greek-English Dictionary of the New Testament. Stuttgart: Deutsche Bibelgesellschaft, 1993

LSJM

Liddell, Henry George, and Robert Scott. A Greek-English Lexicon: With a Revised Supplement. Edited by Sir Henry Stuart Jones and Roderick McKenzie. 9th ed. Oxford: Clarendon, 1996

MM

Moulton, J. H., and G. Milligan. Vocabulary of the Greek Testament. London: Hodder and Stoughton, 1930

A-S

Abbott-Smith, G. A Manual Greek Lexicon of the New Testament. New York: Charles Scribner’s Sons, 1922.

Note

The first two (BDAG and LN) must be referenced for every entry. The next two (FFM and BN) are strongly encouraged.

USFM Names

These are the names that should be used for the USFM form in citation references. For the LXX, we only want to include the Greek names, not the Hebrew names, as shown below.

  • 1 Km = 1 Kingdoms (Heb. 1 Samuel)
  • 2 Km = 2 Kingdoms (Heb. 2 Samuel)
  • 3 Km = 3 Kingdoms (Heb. 1 Kings)
  • 4 Km = 4 Kingdoms (Heb. 2 Kings)
Standard Name USFM Name Standard Name USFM Name
Gen gen Matt mat
Exod exo Mark mrk
Lev lev Luke luk
Num num John jhn
Deut deu Acts act
Josh jos Rom rom
Judg jdg 1Cor 1co
Ruth rut 2Cor 2co
1Km 1sa Gal gal
2Km 2sa Eph eph
3Km 1ki Phil php
4Km 2ki Col col
1Chr 1ch 1Thess 1th
2Chr 2ch 2Thess 2th
Ezra ezr 1Tim 1ti
Neh neh 2Tim 2ti
Esth est Titus tit
Job job Phlm phm
Ps psa Heb heb
Prov pro Jas jas
Eccl ecc 1Pet 1pe
Song sng 2Pet 2pe
Isa isa 1John 1jn
Jer jer 2John 2jn
Lam lam 3John 3jn
Ezek ezk Jude jud
Dan dan Rev rev
Hos hos    
Joel jol    
Amos amo    
Obad oba    
Jonah jon    
Mic mic    
Nah nam    
Hab hab    
Zeph zep    
Hag hag    
Zech zec    
Mal mal    

LXX and Apocrypha

Standard Name USFM Name
Gen gen
Exod exo
Lev lev
Num num
Deut deu
Josh jos
Judg jdg
Ruth rut
1Kgs 1sa
2Kgs 2sa
3Kgs 1ki
4Kgs 2ki
1Chr 1ch
2Chr 2ch
Ezra ezr
Neh neh
Esth esg
Job job
Ps psa
Ps151 ps2
Prov pro
Eccl ecc
Song sng
Isa isa
Jer jer
Lam lam
Ezek ezk
Dan dag
Hos hos
Joel jol
Amos amo
Obad oba
Jonah jon
Mic mic
Nah nam
Hab hab
Zeph zep
Hag hag
Zech zec
Mal mal
1Esd 1es
Tob tob
Jth jdt
Wisd (or WisdofSol) wis
Ecclus (or Sir) sir
Bar bar
EpJer lje
Sgof3Childr s3y
Sus sus
BelandDr bel
1Macc 1ma
2Macc 2ma
3Macc 3ma
4Macc 4ma
ProfMan man

LXX to Canonical Psalms Mapping

Standard(LXX) Psalm # USFM(Canonical) Psalm # Verse comparison
1-8 1-8 Y
9 9-10 N
10-112 11-113 Y
113 114-115 N
114-115 116 N
146-147 147 N
148-150 148-150 Y