recent Dutch Bible translations please?
A lot of my colleague pastors would be helped out a lot if Logos is willing to carry the most recent Dutch Bible translations. The latest translation available now is from 1951. We have had at least five more recent translations since then.
Is it possible to open a request somewhere on the site?
Comments
-
Jan Wolsheimer said:
A lot of my colleague pastors would be helped out a lot if Logos is willing to carry the most recent Dutch Bible translations.
Yes, this will be great.
In the full SESB http://www.logos.com/product/5181/stuttgart-electronic-study-bible these dutch translations are available:
Dutch Bibles
- NBG-vertaling 1951
- Staten Vertaling
- De Nieuwe Bijbelvertaling
- Willibrordvertaling
- Groot Nieuws Bijbel
It would be nice to be able to buy these seperately.
It is too expensive to buy the complete SESB just to obtain these dutch bibles. I already have the NBG1951 and the Statenvertaling in Logos format.
And I would - really - like to add the new "Herziene Statenvertaling", which was published in last december.
Luuk
0 -
You could have a look on SESB 3.0, which (besides the Statenvertaling and 1951's Bijbel) contains
- Groot Nieuws Bijbel (2006)
- De Nieuwe Bijbelvertaling (2004)
- Willibrordvertaling (1995)
Purchasing SESB might be too expensive as long as you want only the Dutch translations - just wanted to point out that there actually are some for Logos 4.
"Mach's wie Gott - werde Mensch!" | theolobias.de
0 -
Luuk Dondorp said:
And I would - really - like to add the new "Herziene Statenvertaling", which was published in last december.
[Y][Y][Y]
0 -
Jan Wolsheimer said:
A lot of my colleague pastors would be helped out a lot if Logos is willing to carry the most recent Dutch Bible translations. The latest translation available now is from 1951. We have had at least five more recent translations since then.
Is it possible to open a request somewhere on the site?
Similar questions have been asked with regard to german/french/.... Bibles, see for example this thread: http://community.logos.com/forums/t/25063.aspx
Perhaps the best way would be to contact the Nederlands Bijbelgenootschap.
Welkom trouwens op het forum!
0 -
Hendrik-Jan van der Wal said:
[Perhaps the best way would be to contact the Nederlands Bijbelgenootschap.
Today I have sent an email to Henk Sennema (CEO ? at the Jongbloed Publishers of the "Herziene Statenvertaling" ) asking about the possibilities. I will keep you posted about this.
Luuk
0 -
Great. I think that's possible for sure. Point is if the Logos crew is willing to invest in non-English bibles.
0 -
I like the logos software the way it is now, and I want to upgrade with only the latest Dutch translations, without having to buy an expensive CD-rom, filled with additional commentaries - there is already so much to go with in the basic package. How can we go about this?! I guess a lot of theology students and ministers in the Netherlands would purchase Logos, (and thus interesting for logos when you look at an increased market) if it would only include the NBV, Groot Nieuws, Herziene Statenvertaling, Het Boek, enz.
Should we take action by undertaking an online petition? lol!
It's great that there are more of you who really want to see this happening!
0 -
[Y]
Please also add the Herziene Voorhoevevertaling ("Telos vertaling"). I have this translation and the HSV already in Accordance (as an user tool).
Hans
MacOS Sierra / Logos 7 Collector's Edition & All Base Packages / Logos Now
0 -
I would really much like to see the Herziene Statenvertaling and the Naardense Bijbel added to Logos 4.
0 -
Logos, can you pls. make these titles available as indivivual titles, or make a Dutch Bibles pack for all your Dutch users!
0 -
Hi, I'm looking into buying Logos (for personal study, I'm not a pastor or student, just a simple architect - :-D ) and also hoping for (more) Dutch Bible translations.
Logos looks really great...
For those of you having one or more Dutch Bibles in Logos: how well does the search go? Are names, things, places, word search and stuff like that also connected/integrated (in)to the Dutch translations? Can you type/use the Dutch names of the books/people/... for searching or do you have to switch to English Bible translations? Do interlinear Bibles synch with a chosen passage in Dutch Bible? ...
I'd just like to know how well Dutch translations are integrated into the whole concept of Logos. I guess they are integrated quite well, otherwise, it wouldn't be very useful, would it? Any thoughts about this?
Cheers and thanks!
Jo D.
Belgium
0 -
I had some contacts last week with the editors of the Herziene Statenvertaling. They are willing to publish it in Logos and are seriously looking for ways to get that done.
I also wrote about it to the Nederlands BijbelGenootschap, but they didn't give any response.
I also would like to have the Naardense Bijbel. Perhaps publishing can also be asked from the publishers.
I further would like to have Dutch Bible tags recognized for PBB, like it was possible in Logos 3.
Hans
0 -
Pieter Wiltjer said:
Logos, can you pls. make these titles available as indivivual titles, or make a Dutch Bibles pack for all your Dutch users!
Not only Dutch Bibles, but also Dutch commentaries, like CNT, COT. Maybe we should contact Kok and other Dutch publishers.
I am not sure how the search engine works, but I can imagine that a (growing) list of Dutch-English keywords could be made, so that resources in both languages can be searched for in one go.
Patrick
0 -
I would love to have the HSV, de Naardense vertaling and Dutch commentaries, like CNT, COT and some public domain commentaries like Dachsels and de Kanttekeningen in Logos.
0 -
The Foundation Dioneth (www.dioneth.nl has some contacts with Kok Publishers and has also some rights to publish that material digitaly in Dutch.
They have it in digital form.
Once ago I spoke with one of the men form Dioneth and he is a fan of Logos. I forgot however his name.
Publishing in PBB-format is possible! But we have to wait for the recognition of Dutch Bible references, e.g.. 1 Kon -> 1 Ki
Please make contact with them!
0 -
Hi Jo,
it seems nobody answered your questions so far. I'm not Dutch, but German - but I think Logos works much alike for these languages.
Jo Decaesteker said:how well does the search go? Are names, things, places, word search and stuff like that also connected/integrated (in)to the Dutch translations? Can you type/use the Dutch names of the books/people/... for searching or do you have to switch to English Bible translations?
Actually Logos searches what is there, but doesn't translate. So if I search the German-language spelling of something, I will only get hits in resources that use this spelling (e.g. Petrus as opposed to Peter). Since I have next to none German resources (save some bibles), I will use Logos completely in English, and I think I will continue to do so, even if SESB 4.0 (announced for Q4 this year) should contain a German language user interface
. So, if you want to have results from your Dutch resources, search for Dutch expressions, if you want results from the multitude of English language resources, you'll need to search for English expressions. However, you won't need to "switch to another bible translation", as searching can be invoked independent from open resources and configured to address those parts of your library where you want the results to be.Jo Decaesteker said:I'd just like to know how well Dutch translations are integrated into the whole concept of Logos.
. Yes. You may have a number of bibles scroll along (that's what you mean with sync, I suppose) .Jo Decaesteker said:Do interlinear Bibles synch with a chosen passage in Dutch Bible?
Well, that's something everybody has to answer depending on their usage experience. I'm not a scholar or pastor, but use Logos for my armchair-theologian studies. These I conduct - as far as PC usage is concerned - nearly exclusively in English language. Since commentaries, monographs and everything is in English, I usually don't even bother to open up the German language bible - this would be different for someone who prepares sermons or teaches a small group. I know of other people who use the localized German version (L3 has it) for studying the original languages in connection with German bibles and don't even bother for English.Jo Decaesteker said:I'd just like to know how well Dutch translations are integrated into the whole concept of Logos.
Hope this helps,
Mick
Have joy in the Lord!
0 -
Having Dutch translations available for Logos would be great!
I always have to go back to webbased Bibles now if I am preparing dutch sermons.
0 -
I was wondering if someone already converted ds. C. den Boer's commentaries on Paul's letters?
http://www.dsdenboer.refoweb.nl/Exegetica.asp
I am converting them to Docx files which takes some time, so if someone already did, just tell please.
0 -
A.J. van den Herik said:
Publishing in PBB-format is possible! But we have to wait for the recognition of Dutch Bible references, e.g.. 1 Kon -> 1 Ki
Ik heb recent een pogrammaatje geschreven, wat gericht is op het taggen van Nederlandse documenten. Referenties als 1 Kon worden niet alleen omgezet naar referenties die Logos snapt, maar blijven ook in de lopende tekst in Logos staan zoals ze stonden (in de tekst op je scherm zie je dus gewoon "1 Kon" in plaats van "1 Ki").
Ook heb ik recent een programma geschreven die de HSV van statenvertaling.nu afgehaald heeft, en getagd heeft in Logos formaat. Ik heb dus de HSV beschikbaar. Alleen, voordat ik die kan verspreiden heb zal de HSV-stichting eerst daartoe rechten moeten geven.
0 -
Beste Simon,
Ik heb interesse, met name in het conversieprogramma.
Groeten van Hans
MacOS Sierra / Logos 7 Collector's Edition & All Base Packages / Logos Now
0 -
Hans, hierbij:
Dit programmaatje is eigenlijk geschreven voor eigen gebruik, met specifieke documenten in het achterhoofd, dus is niet uitgebreid getest.
De werking is heel simpel:
- Selecteer bovenaan een Word-bestand.
- Klik op de knop "Create taglist". Nu is het bestand tags.xlsx gevuld.
- Open dit bestand met Excel, gooi alle regels weg die geen geldige Schriftverwijzing bevatten. Vul ontbrekende verwijzingen toe. Onder het kopje "reference" staat waar naar gezocht wordt in de tekst, onder het kopje "Display" hoe dit getoond wordt, en onder het kopje "New Reference" de Engelse verwijzing. Zorg dat alle Engelse verwijzingen goed staan, sla het excelbestand op en sluit Excel.
- Druk in het programmaatje nu op de knop "Read taglist"
- Druk vervolgens op de knop "Go"
0 -
Simon,
thank you for making this available. Unfortunately I'm not a Dutch Logos user, but a German. Nevertheless I thought, maybe I could use your program to rework German language Docx-Files into bible references that can be converted by the Logos-PB compiler.
Your program, however, doesn't work on my machine (Win7 32 bit, German-language Office 2007) since it doesn't find a certain file - is this due to the strange Public Key, or do I need to install it into a specific path / directory / folder? Or does it presuppose Office 2010 or a Dutch language system?
No need for you to make this the Ultimate Logos4 Localization Engine - but if there is something I can do to fix and have this tool running, I'd appreciate!
Mick
Have joy in the Lord!
0 -
Hi Mick,
You can use my tool for any language. It just searches for scripture references (meaning 2 to 4 characters, followed by a number) and creates a taglist based on that. If tags are missing, you can manuelly add them. It uses that taglist to search and replace the scripture references to a format Logos can understand.
To use my tool, you need the OpenXML library: http://www.microsoft.com/download/en/details.aspx?id=5124.
That's what the error you're seeing is about. If you install that, it should work fine.I'm sorry I don't have an easy setup program, but when I wrote my program, I wrote it for personal use, not knowing other users were going to use it. I guess the program will need some tweaking, to better support other documents, so if you have a document that isn't working alright, please post it here or send it to me by email.
0 -
I'm on Mac so I can't use this, but it sounds like a great tool. Perhaps you could make a new thread about it in the Files or Windows forum, so that more people can take advantage of it? Not many of those who would be happy to have it will ever find it in a thread about Dutch Bibles. (Though I'm surprised at how much I understand of the conversation above. With a little practice, I could learn to read that.)
Mac Pro (late 2013) OS 12.6.2
0 -
Simon
Hartelijke dank voor de tool. Ik krijg hem echter niet aan het werk. De link werk niet:
To use my tool, you need the OpenXML library: http://www.microsoft.com/download/en/details.aspx?id=5124.
Is deze wellicht verkeerd?
For international users: Thanks for the tool. It doesn't work however. The link seems to be wrong.
Hans
0 -
A.J. van den Herik said:
Simon
Hartelijke dank voor de tool. Ik krijg hem echter niet aan het werk. De link werk niet:
To use my tool, you need the OpenXML library: http://www.microsoft.com/download/en/details.aspx?id=5124.
Is deze wellicht verkeerd?
For international users: Thanks for the tool. It doesn't work however. The link seems to be wrong.
Hans
Hans:
regarding the link, there is just a superfluous period at the end: if you try http://www.microsoft.com/download/en/details.aspx?id=5124 it will lead you to a Microsoft page where the Open XML product installer may be downloaded. I'll try tonight whether the tool works with that installed.
Mick
Have joy in the Lord!
0 -
Thanks! It was indeed that superfluous period!
Hans
0 -
Here's a new build of my program, that doesn't need any separate downloads:
Please let me know if it's working alright. Also I would like to know if the program is working OK, and what's not working OK (like scripture references it doesn't find, etc).
0 -
Beste Simon
Bij mij werkt het helaas nog niet helemaal. Ik krijg weliswaar geen foutmeldingen meer bij het gebruik van het programma, maar er verandert niets in de Word-tekst (geen tags toegevoegd).
Ik stuur twee bestanden op, één oorspronkelijk en één getagged exemplaar.
Met vr. groet
Hans
0640.Joh 1.docxIk heb de verwijzingen in de xlsx-tabel veranderd, maar er gebeurt niets.
0 -
Simon,
Alvast bedankt voor het programma. Ik heb nu geen computer bij de hand dus kan het niet direct proberen.
Aan welke eisen moet het docx bestand voldoen voor wat betreft de bijbelverzen?
Moet ieder vers voorafgegaan worden door boek, hoofdstuk en vers?
Groeten van Hans
MacOS Sierra / Logos 7 Collector's Edition & All Base Packages / Logos Now
0 -
Hi Hans,
You're right. I made some changes, and now it works fine. You can download the new version here: 2110.LogosTagger.zip
Workflow:
- Select a file to tag
- Hit the "Create taglist" button
- Edit the "tags.xlsx" file. Remove all lines that are not valid references. Add missing references (1 Joh, 2 Tim, etc are sometimes not found, and should be added manually). And change the "New Reference" column to English references. Save the Excel file and close it.
- Hit the "Go" button.
This will tag your file fine, except for the references that are not standard, like "Johannes (1:1-18)", "vs.1", "vgl. 8:58". Maybe I will add support for that kind of references in the future.
0 -
HansK said:
Simon,
Alvast bedankt voor het programma. Ik heb nu geen computer bij de hand dus kan het niet direct proberen.
Aan welke eisen moet het docx bestand voldoen voor wat betreft de bijbelverzen?
Moet ieder vers voorafgegaan worden door boek, hoofdstuk en vers?
Groeten van Hans
Het programma in deze topic is voor het taggen van gewone worddocumenten (dus tekst die Schriftverwijzingen bevat). Die Schriftverwijzingen worden omgezet naar een formaat wat Logos snapt. Nu worden alle verwijzingen gevonden die 2 tot 4 karakters groot zijn en gevolgd worden door een cijfer, eventueel voorafgegaan door een 1, 2 of 3. Dus referenties als 1 Joh 3, Mat 4, Mt 5 en Hand 9:2. Mochten bepaalde referenties niet goed herkend worden, laat het me dan even weten, dan kan ik kijken hoe ik die in kan bouwen.
Dit programma is niet geschikt voor het taggen van een Bijbel (wie dat wil kan me het best even een mail sturen met het bestand, dan kan ik kijken wat mogelijk is, ik heb namelijk een programmaatje geschreven voor het taggen van de HSV, wat mogelijk daarvoor bruikbaar is).
0 -
Simon said:
Hi Hans,
You're right. I made some changes, and now it works fine. You can download the new version here: 2110.LogosTagger.zip
Workflow:
- Select a file to tag
- Hit the "Create taglist" button
- Edit the "tags.xlsx" file. Remove all lines that are not valid references. Add missing references (1 Joh, 2 Tim, etc are sometimes not found, and should be added manually). And change the "New Reference" column to English references. Save the Excel file and close it.
- Hit the "Go" button.
This will tag your file fine, except for the references that are not standard, like "Johannes (1:1-18)", "vs.1", "vgl. 8:58". Maybe I will add support for that kind of references in the future.
Simon,
thanks a lot. I'll try this tonight and will report.
When you are thinking of adding more complex things in the future: one thing that so far is a big issue for German language references is the different notation. As you maybe know, we differentiate between chapter and verse with comma instead of colon, e.g. Joh 3,16 for John 3:16, which needs running a search/replace in word and requires a decision everytime a comma is found. Since your tool already knows/guesses the references, it would be a nice enhancement for users of German language texts to replace the comma with a colon.
Have joy in the Lord!
0 -
NewbieMick said:Simon said:
Hi Hans,
You're right. I made some changes, and now it works fine. You can download the new version here: 2110.LogosTagger.zip
Workflow:
- Select a file to tag
- Hit the "Create taglist" button
- Edit the "tags.xlsx" file. Remove all lines that are not valid references. Add missing references (1 Joh, 2 Tim, etc are sometimes not found, and should be added manually). And change the "New Reference" column to English references. Save the Excel file and close it.
- Hit the "Go" button.
This will tag your file fine, except for the references that are not standard, like "Johannes (1:1-18)", "vs.1", "vgl. 8:58". Maybe I will add support for that kind of references in the future.
Simon,
thanks a lot. I'll try this tonight and will report.
When you are thinking of adding more complex things in the future: one thing that so far is a big issue for German language references is the different notation. As you maybe know, we differentiate between chapter and verse with comma instead of colon, e.g. Joh 3,16 for John 3:16, which needs running a search/replace in word and requires a decision everytime a comma is found. Since your tool already knows/guesses the references, it would be a nice enhancement for users of German language texts to replace the comma with a colon.
Can you please post an example document, that does contain such references? Preferable including a chain of references. For example, how would the following look in German: 1 John 9:18,20,10:18,19,11:2-10?
0 -
Simon said:
Can you please post an example document, that does contain such references? Preferable including a chain of references. For example, how would the following look in German: 1 John 9:18,20,10:18,19,11:2-10?
I may be able to post a document later today. I think, your reference could look like 1. Joh. 9,18.20; 10,18f ; 11,2-10, noting
- numerals in book names are often written with the period (as it's "Erster Brief", not "Eins Brief") and abbreviated booknames sometimes indicate the abbreviation by period - however, in commentaries, journals and newer works these periods are often omitted for space reasons and sometimes the space is ommitted, so one could encounter 1Joh or 1 Joh or 1.Joh or 1. Joh instead of 1. Joh.
- chapter and verse are separated by comma
- multiple verses in the chapter separated by period (usually without a space after it) - one consecutive verse indicated by f for "following", multiple by ff (note: I have seen the guideline of a seminary that uses + instead of period, but I have never encountered this notation)
- multiple chapters in the book separated by semicolon (some people may use comma instead)
One source I found on the fly to run your reference tool against is the long Article "Zitat (AT)" in the small theological wiki by German Bible Society http://www.bibelwissenschaft.de/nc/wibilex/das-bibellexikon/details/quelle/WIBI/zeichen/z/referenz/35442/ - it contains rather complex references (such as
Ps 2,7-9;
Ps 21,9-13;
Ps 89,3-5.
20-23.
35-38;
Ps 110,1.
4;
Ps 132,11-12.
14-18) but note that it seems they choose to repeat the bookname if they reference another chapter and to include spaces after the verse-dividing period - this enhances readability but may be due only to their site's version of RefTagger. You see, there are variations. This source would require manual editing of the XLSX since they number chpaters and then start chapter names with bible references, so you end up with e.g. 5. Jer 26,18 which looks like there was a fifth book of Jeremiah...Thanks again for suppporting us!
Mick
Have joy in the Lord!
0 -
NewbieMick said:
- numerals in book names are often written with the period (as it's "Erster Brief", not "Eins Brief") and abbreviated booknames sometimes indicate the abbreviation by period - however, in commentaries, journals and newer works these periods are often omitted for space reasons and sometimes the space is ommitted, so one could encounter 1Joh or 1 Joh or 1.Joh or 1. Joh instead of 1. Joh.
That isn't a problem for my program. Just manually add "Erster Timotheusbrief" (or however thats written in German), and add that to the "tags.xlsx" file. Then it shoud be recognised and correctly tagged.
[quote]
- chapter and verse are separated by comma
- multiple chapters in the book separated by semicolon (some people may use comma instead)
For that, I need to add a special "German notation" mode in my program. I will try to get that into my schedule somewhere in the coming weeks. I do, however, need some documents (or parts of documents) to test with. So can you please post some documents/fragments that are representable.
[quote]
- multiple verses in the chapter separated by period (usually without a space after it) - one consecutive verse indicated by f for "following", multiple by ff (note: I have seen the guideline of a seminary that uses + instead of period, but I have never encountered this notation)
I will add support for this in the next version.
[quote]
One source I found on the fly to run your reference tool against is the long Article "Zitat (AT)" in the small theological wiki by German Bible Society http://www.bibelwissenschaft.de/nc/wibilex/das-bibellexikon/details/quelle/WIBI/zeichen/z/referenz/35442/ - it contains rather complex references (such as
Ps 2,7-9;
Ps 21,9-13;
Ps 89,3-5.
20-23.
35-38;
Ps 110,1.
4;
Ps 132,11-12.
14-18) but note that it seems they choose to repeat the bookname if they reference another chapter and to include spaces after the verse-dividing period - this enhances readability but may be due only to their site's version of RefTagger. You see, there are variations.Thanks
[quote]This source would require manual editing of the XLSX since they number chpaters and then start chapter names with bible references, so you end up with e.g. 5. Jer 26,18 which looks like there was a fifth book of Jeremiah...
The "create taglist" option of my tool isn't meant to be completely errorproof (that would virtually be impossible). It will compile a taglist that is quit accurate, but it should always be manually checked. Even if all references are correctly found, you still need to edit the collumn "New reference" with the corresponding English reference.
The good news is, that the "tags.xlsx" file can be reused. When you have several documents with the same reference-abbriviations, you only have to check/fill the "tags.xlsx" once, and it can be used for all those documents.
0 -
BTW: Can someone please mail the authors of the Herziene Statenvertaling (HSV), and ask for their permission to distribute a PBB copy of the HSV? I have the tagged file ready, so when autorisation is secured, it can be distributed.
0 -
I have some contacts and I know that they are in contact with Logos.
You can mail me at aj.vd.herikATlive.nl and I will give you an emailadress, so you can ask it yourself!
Hans
0 -
Simon said:
The "create taglist" option of my tool isn't meant to be completely errorproof (that would virtually be impossible). It will compile a taglist that is quit accurate, but it should always be manually checked. Even if all references are correctly found, you still need to edit the collumn "New reference" with the corresponding English reference.
Simon,
thanks a lot for this tool. I may prove very helpful in localizing content for PBs unless Logos themselves take up the task to recognize Dutch and German bible references.
I tested it with a document where I copied a number of snippets from various sources. I ran your tool on the file (....orig...), edited the tags.xls, ran PB. Then I did a brutal replace all commas with colons, edited tags, ran again, then I tried to conform the references to what you gave me above (colon2) edited and ran again. This time the Logos PB compiler under beta 12 issued no errors or warnings. Still there seem to be some bugs in the tool, as you can see. However, it worked very well on some references.I see that it doesn't detect "Apg" which is acts - I put this manually into the tags.xlsx but it still doesn't like it. It doesn't detect Dtn (Deuteronomium) as well, which I hoped Logos would pick up by itself.
Attached you will find the documents - I have provided resource links for the online sources in case you need more ideas.3323.LogosTaggerTest.zip
Thanks again,
Mick
Have joy in the Lord!
0 -
Simon,
Ik heb veel interesse in de HSV.
Ben benieuwd.
Groeten van Hans
hans ad blogos.nl
MacOS Sierra / Logos 7 Collector's Edition & All Base Packages / Logos Now
0 -
NewbieMick said:
I tested it with a document where I copied a number of snippets from various sources. I ran your tool on the file (....orig...), edited the tags.xls, ran PB. Then I did a brutal replace all commas with colons, edited tags, ran again, then I tried to conform the references to what you gave me above (colon2) edited and ran again. This time the Logos PB compiler under beta 12 issued no errors or warnings. Still there seem to be some bugs in the tool, as you can see. However, it worked very well on some references.I see that it doesn't detect "Apg" which is acts - I put this manually into the tags.xlsx but it still doesn't like it. It doesn't detect Dtn (Deuteronomium) as well, which I hoped Logos would pick up by itself.
Attached you will find the documents - I have provided resource links for the online sources in case you need more ideas.3323.LogosTaggerTest.zip
Thanks, I'm going to test with these documents, to make my tool German proof [:D]. I hope to have a new version of the tool within the next 2 to 3 weeks.
0 -
Hello Simon
Is there already a new version? I am looking forward to it!
Hans
0 -
Hello.
Maybe it's an good idea to make the HSV available by hand. If we do this with a lot of dutch people it wouldn't be too much work. We can make it as an docx-file for Logos and also in raw text file so we can use it to compile in Bibleworks. Or am I not aloud to name the product of a competitive program? [;)]
Ang hello Hans...........that's a long time ago I heard from you.
I wrote at least three times to Jongbloed Publishers but they really don't know if and when there will be a module for Logos or Bibleworks.
Greetings, Wijnand
0 -
Wijnand said:
Hello.
Maybe it's an good idea to make the HSV available by hand. If we do this with a lot of dutch people it wouldn't be too much work. We can make it as an docx-file for Logos and also in raw text file so we can use it to compile in Bibleworks. Or am I not aloud to name the product of a competitive program?
Ang hello Hans...........that's a long time ago I heard from you.
I wrote at least three times to Jongbloed Publishers but they really don't know if and when there will be a module for Logos or Bibleworks.
Greetings, Wijnand
Creating a docx file for the HSV isn't that difficult. I already have it. But permission of the publisher is needed to distribute it in a legal way. I believe that christians should respect copyright laws, so I'm not going to distribute the docx-file I've created unless someone secures a written permission from Jongbloed for me.
0 -
A.J. van den Herik said:
Hello Simon
Is there already a new version? I am looking forward to it!
Hans
Hi Hans,
Because I'd a lot of papers due, I haven't got the time to work on it since the last version. I hope to work on it next Thursday, and post a new version.
Simon
0 -
Simon,
Thanks! I eagerly look forward to the next release.
For those interested in HSV: the person in charge of digital publishing of the HSV wrote to me in January 2012: 'De verschijning van de HSV in Logos 4 is in gang gezet.' I can give no more information, but I hope that quote gives you some hope!
Hans
0 -
Hello Simon.
You're right about the copyrights. I didn't mean to use it for illegal distribution. But as far I know it isn't illegal to copy, paste and compile for personal use. And that's the only thing I wanted. But maybe it won't be too long before the HSV becomes available for Logos as I read in the post from AJ. WE can wait for that.
I only asked Jongbloed for the Bibleworks version, not for Logos.
Wijnand
0 -
Yes Wijnand H., that's me [:D]
Hans
MacOS Sierra / Logos 7 Collector's Edition & All Base Packages / Logos Now
0 -
Here's the new version, with support for German.
Before using it, clean up your Word document first. You can do that by selecting all text in the document, press CTRL-C (copy), create a new document and set it's language to a language for which you don't have a dictionary installed (I use Swedish myself), and paste the text in it using CTRL-C. Use this new document to feed to my program.
0 -
Simon said:
Here's the new version, with support for German.
Before using it, clean up your Word document first. You can do that by selecting all text in the document, press CTRL-C (copy), create a new document and set it's language to a language for which you don't have a dictionary installed (I use Swedish myself), and paste the text in it using CTRL-C. Use this new document to feed to my program.
Simon,
I've done this, but don't see any changes to the old version:
- the German peculiar reference with comma instead of colons is not supported (or did I miss a switch or something? How does strict or loose work?), so Joh 3, 16 would become John 3 and John 16
- Apg (=Acts) and Dtn ares till not detected
I put the test document and the tagged document, as well as the tags-xls and the log information into a zip.0207.test pbb tagger German 01_tagged.zip
Thanks again for your work!
Have joy in the Lord!
0
