Building a short German dictionary as PB

Fabian
Fabian Member Posts: 1,006 ✭✭✭
edited November 21 in English Forum

Hello Dave

I have not build a German dictionary until now. It is short but I have searched how to do it. Unfortunately the https://wiki.logos.com/Building_a_Dictionary_PB give for me on MacOS with Safari 17.1 only replacement images.

Thanks

Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης· 

Tagged:

Comments

  • Dave Hooton
    Dave Hooton Member, MVP Posts: 35,667 ✭✭✭

    Unfortunately the https://wiki.logos.com/Building_a_Dictionary_PB give for me on MacOS with Safari 17.1 only replacement images.

    This example should help you create a dictionary with TOC

    5078.My Lexicon.docx

    Dave
    ===

    Windows 11 & Android 13

  • Fabian
    Fabian Member Posts: 1,006 ✭✭✭

    Hello Dave

    Many thanks for your help.

    I have now some questions or issues. The lexicon is after a text and two headings. If I now put the lexicon words in [[@Headword:Messias]] then the jump from the text by a triple click (this i have done so in the preferences) goes only to the heading before. If I scoll down I see the word is highlighted in blue. But the visual is stuck on the heading before. 

    Second the [[Messias >> Headword:Messias]] don't link.

    I see you have the last two as headings too. Is this necessary or should I do all as Headings.

    It seems I have to do all as headings.

    I have also the issue the [[Messias >> Headword:Messias]] don't link by hover over. I see the linking-hand, but no pop-up is coming. 

    I try to do something similar as the images below. The Headword is on the same level as the content and the links has a preview.

    Thanks for your help

    Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης· 

  • Fabian
    Fabian Member Posts: 1,006 ✭✭✭

    Hello Dave

    I get now the lexicon or more wordbook to work. 

    Only the [[label >> Headword:link]] don't work. It seemed they worked one time by clicking on it but now nothing happens.

    Thanks

    Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης· 

  • Dave Hooton
    Dave Hooton Member, MVP Posts: 35,667 ✭✭✭

    I try to do something similar as the images below. The Headword is on the same level as the content and the links has a preview.

    My example shows you cannot do that, because the content (definition) will be treated as part of the Table of Contents (TOC). That line is a Word Heading style.  Your definition (content) should be on the next line and has Normal style.  Links can be internal or external.

    See my example of a Dictionary 1780.Glossary.docx

    In the PB tool, it should be Type: Dictionary and the Language should be English if you decide to compile it.

    The LXX entry is  linked internally with pop-up  -->  [[see Septuagint >> Headword:Septuagint]]  i.e. it is linked to the Septuagint entry.

    The external link for Saturate also has a pop-up  ---> [[Saturate >> logosres:mwdict11;hw=Saturate]] [[@Headword:Saturate]] verb

    Dave
    ===

    Windows 11 & Android 13

  • Dave Hooton
    Dave Hooton Member, MVP Posts: 35,667 ✭✭✭

    I have now some questions or issues. The lexicon is after a text and two headings. If I now put the lexicon words in [[@Headword:Messias]] then the jump from the text by a triple click (this i have done so in the preferences)

    As I indicated above, you should be compiling a Dictionary for your own language  (not a lexicon).

    i would recommend a double-click for the lookup (jump) as an attempt at a triple click can often be interpreted as a double-click.

    Dave
    ===

    Windows 11 & Android 13

  • Fabian
    Fabian Member Posts: 1,006 ✭✭✭

    Hello Dave

    Many thanks for your help. 

    It works now quite good. Yes as a dictionary it would have some advantages. Currently it is after the Bible. One which is strange it has every time the last Bibile verse reference included in the pop-up.

    It seems Logos add this to every pop-up. 

    Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης· 

  • Fabian
    Fabian Member Posts: 1,006 ✭✭✭

    Hello Dave

    I have now made some changes to the docx. Now the pop-up disappeared. I have rebuild the index, but they don't appear. Could it be I only have to wait more, or is something brocken.

    BTW I have done the heading above in a [[@Headword: ..]] So it appears in the search filed. I hoped the verse ref in the pop-up is then replaced with the actual Headings. But now the pop-up is gone, and the links don't work anymore. 

    Thanks

    Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης· 

  • Dave Hooton
    Dave Hooton Member, MVP Posts: 35,667 ✭✭✭

    I have now made some changes to the docx. Now the pop-up disappeared

    Please upload your source docx file  (or a couple of pages that illustrate the problem).

    Dave
    ===

    Windows 11 & Android 13

  • Fabian
    Fabian Member Posts: 1,006 ✭✭✭

    2570.Fabian test 2.docxHello Dave

    I have encountered 2 issues with Logos

    1. I had a warning of an uncommon font. I have no clue where this came from. I have select all and tried to convert them to New Times Roman. Multiple times. I can't fix it in Word.  I have copied the entire wordbook to a txt editor and put it back to Word. Not to say I had to rebuild all the font styles again. 

    But I got it to work. 

    2. I have taken another copy of the Word file and have deleted all until it worked. I had nearly all to delete until it worked. Only two lines. Docx Anhang. 

    3. On your request I have taken another copy and deleted nearly all until I got it to work. Docx Fabian test 2. After some deleting and adding again I found out, if I have the last heading in

    [[@Headword:Sodom]]{{~ Sodom }}

    Bla bla: slddfsdfkljf sfkjskfdsdfksfj slfjskdfjsjsf slfjskfjsfj slfsjfjsjkfs 

    Then it does's work. If I delete it it, the linking feature for all works. Very strange. 

    Another thing I encountered is in the Anhang I have as location the actual source location. See arrow. Good. But in the other one it has the location as from the last Bible verse. See image in this thread. This is in my opinion not good. If I do an empty heading line to break the heading from above doesn't help.

    In general I can say the linking feature is very difficile. If something not exactly as Logos want. All is inactive and if you click anyway on it the results are completely wrong. For example you click on a link to headword heaven it opens shows words to halleluja. I would love to have a better warning report. 

    4857.Anhang.docx

    7041.Fabian test 2.docx

    Thanks

    Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης· 

  • Dave Hooton
    Dave Hooton Member, MVP Posts: 35,667 ✭✭✭

    2570.Fabian test 2.docxHello Dave

    I have encountered 2 issues with Logos

    1. I had a warning of an uncommon font. I have no clue where this came from. I have select all and tried to convert them to New Times Roman. Multiple times. I can't fix it in Word.  I have copied the entire wordbook to a txt editor and put it back to Word. Not to say I had to rebuild all the font styles again. 

    But I got it to work. 

    2. I have taken another copy of the Word file and have deleted all until it worked. I had nearly all to delete until it worked. Only two lines. Docx Anhang. 

    3. On your request I have taken another copy and deleted nearly all until I got it to work. Docx Fabian test 2. After some deleting and adding again I found out, if I have the last heading in

    [[@Headword:Sodom]]{{~ Sodom }}

    Bla bla: slddfsdfkljf sfkjskfdsdfksfj slfjskdfjsjsf slfjskfjsfj slfsjfjsjkfs 

    Then it does's work. If I delete it it, the linking feature for all works. Very strange. 

    It is all in the formatting!

    • the [[Headword]] lines had a peculiar Strong style and I had to use Styles > Clear Formatting before I could apply a Heading 6 style.
    • the content lines needed Styles > Clear Formatting which left them with Normal style.
      • Normal is needed for the Headword  links, so your default style could work for content without links.

    But it needed a hidden Headword  [[@Headword:Stop]] with some content ("The end") for  the Sodom headword to work properly.

    6471.Fabian test 2.docx

    Ensure that you enforce a type Dictionary for the PB to avoid other problems. I removed the bible milestone to avoid a major issue with the Headword milestones.

    Dave
    ===

    Windows 11 & Android 13

  • Fabian
    Fabian Member Posts: 1,006 ✭✭✭

    Hello Dave

    Many many thanks. I wasn't aware of the Styles > Clear Formatting. Just as remember to me Bereich Formatvorlagen > Formatierung löschen. 

    I have seen somewhere in the wiki about the Stop Milestone, but it was not clear enough for me. Thanks for your very useful explanation.

    Thanks again.

    Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης· 

  • Fabian
    Fabian Member Posts: 1,006 ✭✭✭

    Hello Logos

    I'm not happy. If I make a one little mistake with the formatting all links doesn't work. And even if I reverse the action and save it. It doesn't come back. This feature is to difficile. This has to be more robust. 

    Thanks.

    Fabian

    Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης· 

  • Dave Hooton
    Dave Hooton Member, MVP Posts: 35,667 ✭✭✭

    Hello Logos

    I'm not happy. If I make a one little mistake with the formatting all links doesn't work. And even if I reverse the action and save it. It doesn't come back. This feature is to difficile. This has to be more robust. 

    It requires some skill with setting styles in Word, but I have never found it onerous to check for Normal style with links. It is also acknowledged that finding a "little mistake" can be very onerous.

    You should make a suggestion at https://feedback.logos.com/boards/logos-desktop-app, but Faithlife have not advanced PB's for many years!

    Dave
    ===

    Windows 11 & Android 13

  • Fabian
    Fabian Member Posts: 1,006 ✭✭✭

    Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης· 

  • Fabian
    Fabian Member Posts: 1,006 ✭✭✭

    I'm so annoyed of this fragil feature...

    I have now corrected a typo normal text. Just added a -. And now the full linking feature of this file is gone.

    This is unusable as it is now. Please make them more robust.

    Thanks.

    Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης· 

  • Dave Hooton
    Dave Hooton Member, MVP Posts: 35,667 ✭✭✭

    I have now corrected a typo normal text. Just added a -. And now the full linking feature of this file is gone.

    Please provide a full description or upload a docx file with the issue.

    Dave
    ===

    Windows 11 & Android 13

  • Fabian
    Fabian Member Posts: 1,006 ✭✭✭

    Hello Dave

    Sorry for the late response.

    I have done the lexicon as you said. I have cleared all the formats. Then I have marked the Headwords as headings. I imported it and all worked fine. All links I have done was functioning. 

    In between a Word update came out.

    Then later I saw there is a mistake in the normal text. Not in the heading of Headword or links to the Headword. Just simply plain text of the lexicon. I added a dash. Not copy paste, simply typed. Saved it and I rebuild it. After the import the links aren't working anymore. 

    I have only 1 Block text, 1 left angle text, 1 footnote, and the 4 headings. All is in Times new roman.

    Always to close Logos and to open it drives me also crazy.

    I have now again reduced the docx to the minimum.

    So it don't work.

    5722.Anhang test.docx

    If I delete  either one of the two below. This part (which is now not visible)

    or this part (which is now not visible)

    Only the second link appear correct. But not the first one doesn't work either. 

    If I delete both parts. Both links works.

    I have no clue why. All I can say it is very frustrating.

    I have only an appeal on Logos to make the linking feature more robust. 

    Thanks

    Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης· 

  • Dave Hooton
    Dave Hooton Member, MVP Posts: 35,667 ✭✭✭

    I have now again reduced the docx to the minimum.

    So it don't work.

    5722.Anhang test.docx

    I can fix this because the document uses my Normal style. I don't know how you can retrieve your "Normal"style, but an Internet search should help.

    I note that you use Word's "language" with English for the headings and German for the content/definition. You should:

    • Define German as the language for the document and the Personal Book
    • For the headwords use [[@Headword+en:Abaddon]]{{~ Abaddon }}, where en means that the word is English.

    Dave
    ===

    Windows 11 & Android 13

  • Fabian
    Fabian Member Posts: 1,006 ✭✭✭

    Hello Dave

    Many thanks. Your explanation solved some issues. I guess they came as I have copied the text to another Word document and I had the automatic language recognizer on. 

    I would love if Logos recognize a link to a headword which doesn't match the language and gives a warning than simply not work. It would be good if there is any content in the warnings. So for example the "Link to Headword XY is failed."

    And if only this link doesn't work. Currently then all links are unusable. So to find which one is the bad one is hard to find.

    But this helped me on the full Lexicon not. I have selected all and marked as German. After the import I have some warnings. 

    [Warning] Bad character in string: 0x000A
    [Warning] Bad character in string: 0x000A
    [Warning] Bad character in string: 0x000A
    [Warning] Bad character in string: 0x000A
    [Warning] Bad character in string: 0x000A
    [Warning] Bad character in string: 0x000A
    [Warning]

    I don't know if this is the reason the linking feature don't work. One is empty. I have no clue. An internet search doesn't help me which character this is to solve. I have also no clue where they are?

    I would love if the linking still works. 

    I imported it again and now the links works again. Strange. Foremost why, and why they may not work next time by import. A more robust with better reports would be great.

    Thanks. 

    Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης· 

  • Dave Hooton
    Dave Hooton Member, MVP Posts: 35,667 ✭✭✭

    But this helped me on the full Lexicon not. I have selected all and marked as German. After the import I have some warnings. 

    [Warning] Bad character in string: 0x000A

    Your work method is confusing. What document have you "selected all and marked as German". Is this then imported to another document?

    1. You should set the default language by clicking the Language in the toolbar at the bottom of the document.
    2. Once you have a lexicon entry working correctly use the Hints and Tips for Consistent Formatting throughout the document.

    Dave
    ===

    Windows 11 & Android 13

  • Fabian
    Fabian Member Posts: 1,006 ✭✭✭

    Hello Dave 

    Thanks. I talked about two files. One I have as full lexicon. And one I had copied from the first and reduced it to the point I posted in the forums. 

    Currently I was able to have working links. 

    Thanks, I appreciate your willingness and time to help me. I come back if I ran in a problem again.

    Thanks for the Hints and Tips.

    Fabian

    Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης· 

  • Fabian
    Fabian Member Posts: 1,006 ✭✭✭

    Hello Dave

    This is taken from the file which I had added the page numbers. Since then some links are corrupt. 

    4382.corrupted Links.docx

    The Asia works.

    The Areopag not. 

    Both has worked before. 

    Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·