Update on Herziene Statenvertaling..

Dear Thomas and Faithlife,
Can we get an update on the progress of the Herziene Statenvertaling?
Looking forward to have it by Christmas ![:)]
Comments
-
I can't promise you Christmas (rather I can promise it won't be Christmas), but I can tell you that production is back to moving and I am waiting to hear back as to when we can expect a delivery! All things considered, while I'd also rather want it yesterday, I am just incredibly thankful that we were able to get the blocking issues resolved with the help of Jongbloed and can now move ahead towards completion!
Director, New Languages & Business Line Management
0 -
Hi Thomas,
Thanks for answering. Now I do hope it gets momentum. Looking forward to its delivery before Christmas next year!
0 -
Thanks! Glad to hear!
0 -
Will HSV be available before Eastern?
Hans
0 -
Will HSV be available before Eastern?
Hans
0 -
Hans van den Herik said:
Will HSV be available before Eastern?
Hans
We won't be able to hit before Easter, but are in the final stages! What's keeping us from shipping it before then? We are currently in the final steps of building a new Bible Data Type (most Bibles have a unique verse numbering scheme and require some custom work to ensure that links, notes, etc. are attached to the correct verse) and those can only be shipped with upcoming Version releases. The hope right now is to ship this with 9.13, which would allow us to ship the Bible shortly thereafter!
Director, New Languages & Business Line Management
0 -
Thanks for the update!
Hans
0 -
That sounds good, thanks for the update!
0 -
We won't be able to hit before Easter, but are in the final stages! What's keeping us from shipping it before then? We are currently in the final steps of building a new Bible Data Type (most Bibles have a unique verse numbering scheme and require some custom work to ensure that links, notes, etc. are attached to the correct verse) and those can only be shipped with upcoming Version releases. The hope right now is to ship this with 9.13, which would allow us to ship the Bible shortly thereafter!
Easter has been, now looking forward to Pentecost. And yes...the HSV !!
0 -
Luuk Dondorp said:
Easter has been, now looking forward to Pentecost. And yes...the HSV !!
In de Nederlandse gebruikersgroep op Facebook werd de maand juli genoemd... Nog even volhouden!
0 -
HJ. van der Wal said:
In de Nederlandse gebruikersgroep op Facebook werd de maand juli genoemd... Nog even volhouden!
Heb geen Facebook account. Had al begrepen dat juni/juli zeer waarschijnlijk is. We kunnen gaan aftellen..!
0 -
HJ. van der Wal said:Luuk Dondorp said:
Easter has been, now looking forward to Pentecost. And yes...the HSV !!
In de Nederlandse gebruikersgroep op Facebook werd de maand juli genoemd... Nog even volhouden!
I'd expect sooner than that (not sure where the context around it came from, since it wasn't me). As mentioned before, the resource itself is ready, we simply need to ship some updated code for it to function, which will ship with 9.13 at the end of next week. After some minor remaining testing to ensure that things work we should be able to get it our right after, so I'd expect to have a ship date in place by late April, the latest early May (at which point in time we'd most likely give our users the customary two week warning before we ship it).
Director, New Languages & Business Line Management
0 -
Thank you for informing us. Looking forward!
0 -
I'd expect sooner than that
Thank you very much for sharing this information!
0 -
Quick update: The resource has shipped internally, meaning we can now schedule a ship date! I've talked with the team, and we are looking to finalize around May 20th. Barring any last minute changes, you should see your pre-order confirmation in your e-mail confirming that date soon (and if you don't have it pre-ordered yet, now is your last chance!).
Director, New Languages & Business Line Management
0 -
-
Eindelijk :-)
TRANSLATE withx
English
Arabic
Hebrew
Polish
Bulgarian
Hindi
Portuguese
Catalan
Hmong Daw
Romanian
Chinese Simplified
Hungarian
Russian
Chinese Traditional
Indonesian
Slovak
Czech
Italian
Slovenian
Danish
Japanese
Spanish
Dutch
Klingon
Swedish
English
Korean
Thai
Estonian
Latvian
Turkish
Finnish
Lithuanian
Ukrainian
French
Malay
Urdu
German
Maltese
Vietnamese
Greek
Norwegian
Welsh
Haitian Creole
Persian
// <![CDATA[
var LanguageMenu; var LanguageMenu_keys=["ar","bg","ca","zh-CHS","zh-CHT","cs","da","nl","en","et","fi","fr","de","el","ht","he","hi","mww","hu","id","it","ja","tlh","ko","lv","lt","ms","mt","no","fa","pl","pt","ro","ru","sk","sl","es","sv","th","tr","uk","ur","vi","cy"]; var LanguageMenu_values=["Arabic","Bulgarian","Catalan","Chinese Simplified","Chinese Traditional","Czech","Danish","Dutch","English","Estonian","Finnish","French","German","Greek","Haitian Creole","Hebrew","Hindi","Hmong Daw","Hungarian","Indonesian","Italian","Japanese","Klingon","Korean","Latvian","Lithuanian","Malay","Maltese","Norwegian","Persian","Polish","Portuguese","Romanian","Russian","Slovak","Slovenian","Spanish","Swedish","Thai","Turkish","Ukrainian","Urdu","Vietnamese","Welsh"]; var LanguageMenu_callback=function(){ }; var LanguageMenu_popupid='__LanguageMenu_popup';
// ]]>TRANSLATE with
// <![CDATA[
var intervalId = setInterval(function () { if (MtPopUpList) { LanguageMenu = new MtPopUpList(); var langMenu = document.getElementById(LanguageMenu_popupid); var origLangDiv = document.createElement("div"); origLangDiv.id = "OriginalLanguageDiv"; origLangDiv.innerHTML = "<span id='OriginalTextSpan'>ORIGINAL: "; langMenu.appendChild(origLangDiv); LanguageMenu.Init('LanguageMenu', LanguageMenu_keys, LanguageMenu_values, LanguageMenu_callback, LanguageMenu_popupid); window["LanguageMenu"] = LanguageMenu; clearInterval(intervalId); } }, 1);
// ]]>
0 -
Eindelijk, HSV is er!!
Het heeft jaren geduurd, maar nu dan toch. Blij mee.
Nogmaals, dank @Faithlife
0 -
Very happy the HSV is finally here as well!
It works well on my PC, but on all my mobile (Android) devices I get "An unknown error occurred opening resource". Does anyone else have this problem as well or found a solution already?
0 -
Daniel,
I can replicate this for the Logos Mobile App on my Android Device. Not opening for "unknown error"
But it is running fine on my MacBook Air and iPhone.
I just opened another new thread for this problem. Perhaps better to move your post over there.
0 -
Hi Luuk,
Thanks for your message. Good to hear it does work on an iPhone, hopefully they'll be able to solve the Android problem.
I did notice your separate post and already added a message there.
0 -
https://community.logos.com/forums/t/207443.aspx
link to post on HSV not opening on Android devices
0 -
This morning I was able to open the HSV on my Android Device (Onyx Boox Poke2 - E-ink) after installing the latest update Logos Mobile for Android. Working fine ! [:)][Y]
0 -
Yes, same here, finally, this was a good test of our patience [:D].
0 -
Apologies for the belated reply, I was out of the office for a bit. I'm glad the team was already able to resolve the underlying issue, so you should be all set.
In addition, I am sure a number of you would also appreciate having the NBV21, so I figured I'd drop a link for the pre-order here as well!
Director, New Languages & Business Line Management
0 -
This post was moved to a new post, for it is a new topic: 207561.aspx
Question related to the released HSV: are there any plans to update this HSV to a full fledged Logos Bible format? Meaning it will feature Interlinear and Reverse Interlinear options like the ESV, KJV. Like this was also available in Bibleworks for some Dutch Bibles.
0 -
Very Appreciated.
I would like to see also: Bijbel in Gewone Taal. Also from Nederlands Bijbelgenootschap!
0 -
Luuk Dondorp said:
This post was moved to a new post, for it is a new topic: 207561.aspx
Question related to the released HSV: are there any plans to update this HSV to a full fledged Logos Bible format? Meaning it will feature Interlinear and Reverse Interlinear options like the ESV, KJV. Like this was also available in Bibleworks for some Dutch Bibles.
answered in the new thread - https://community.logos.com/forums/p/207561/1208747.aspx#1208747
Director, New Languages & Business Line Management
0 -
It's really nice to have the HSV in Logos, so thanks for that after all this time!
I'm sad to say though that I rather regularly stumble upon issues with it, let me give 2 examples that I noticed 'by accident'.
1. Footnotes are wrong in Luke (they seem off by 1). The following screenshots are from Luke 1 and 2.
---
---
2. Words are missing from Jeremiah 23 (verse 7). I mailed support about this (on July 22nd) but never got a reply.
The effect of this is that I start to doubt the reliability of the text in Logos, which made me, for now, switch back to another default translation.
Just putting this here, not sure how to act upon it.
0 -
Thank you for the report on this. I am having the team look into this and see what might have happened here (I have some suspicions at least for problem 1). Can you confirm that this is limited to Luke, or was this just the first time you've encountered it, but it is more widespread than that?
I apologize for this inconvenience, we are going to take a closer look to see if this is an issue with the data we received or if there was an error in the process.Director, New Languages & Business Line Management
0 -
Glad to help!
I stumbled upon the issue in Luke and hadn't checked anywhere else. Doing that now I see that the problem is also there in Matthew and Mark, but not in Malachi, John, Acts or, for example, Romans. These are the only ones I checked.
0 -
There are more problems with the Logos edition of the Herziene Statenvertaling:
1. In general, poetic text is indented too much, which leads to many (unnecessary) line breaks on a mobile phone or when one uses "multiple resource display" on a desktop.
2. In alphabetic psalms like 25 and 34, the names of the Hebrew letters are put on a separate line after the first colon of the verse. This looks very awkward, as in Hebrew they are the letters with which the verse starts, not letters in between the first and second half of the verse. Moreover, the names of some of the Hebrew letters are capitalized while others are not, and in Psalm 34 some letters are capitalized that are not capitalized in Psalm 25. This all looks rather chaotic.
PS: I use this opportunity to repeat my complaint about the Arabic Van Dyck version that I have tried to get across to Logos in various ways over the years, but that has not yet been addressed until now. Unlike most Logos books, Logos's Arabic Van Dyck is absolutely substandard. An Arabic Bible should have vocalization and proper punctuation, which are both lacking in the Logos edition. There are good electronic editions of the Arabic Van Dyck online (see, e.g., bible.com), so it is really a riddle why Logos sticks to this substandard edition.
As for vocalization: while other Arabic books are usually not vocalized, the Bible and the Quran are always printed/quoted with vocalization.0 -
Willem J. de Wit said:
There are more problems with the Logos edition of the Herziene Statenvertaling:
1. In general, poetic text is indented too much, which leads to many (unnecessary) line breaks on a mobile phone or when one uses "multiple resource display" on a desktop.
2. In alphabetic psalms like 25 and 34, the names of the Hebrew letters are put on a separate line after the first colon of the verse. This looks very awkward, as in Hebrew they are the letters with which the verse starts, not letters in between the first and second half of the verse. Moreover, the names of some of the Hebrew letters are capitalized while others are not, and in Psalm 34 some letters are capitalized that are not capitalized in Psalm 25. This all looks rather chaotic.Thank you for the detail, the team is already exploring the issue (some of the things you mention seem like a pretty clear data issue, but I want to refrain from too much speculating).
Willem J. de Wit said:PS: I use this opportunity to repeat my complaint about the Arabic Van Dyck version that I have tried to get across to Logos in various ways over the years, but that has not yet been addressed until now. Unlike most Logos books, Logos's Arabic Van Dyck is absolutely substandard. An Arabic Bible should have vocalization and proper punctuation, which are both lacking in the Logos edition. There are good electronic editions of the Arabic Van Dyck online (see, e.g., bible.com), so it is really a riddle why Logos sticks to this substandard edition.
As for vocalization: while other Arabic books are usually not vocalized, the Bible and the Quran are always printed/quoted with vocalization.I don't want to ignore the things you mention above, it is absolutely a resource that needs some work, however I do want to call out that we recently released the Ketab El Hayat (NAV) as a more modern translation. In addition to that, we are also adding titles from Dar Manhal Al Hayat to our offering in the coming months (we still have some production questions here). That doesn't mean that your statement above isn't correct and we should and need to return to that, but our decision at this point in time was to focus on newer, modern content.
Director, New Languages & Business Line Management
0 -
Yes, I noticed that Ketab El Hayat (NAV) and titles from Dar Manhal Al Hayat have been added. But hopefully the AVD can get attention soon. It is not the kind of outdated version that is only of interest for historical purposes; on the contrary, it is by far the most widely used and recognized version of the Bible here in Egypt.
0 -
Hi Thomas, I just got the updated version, and the footnotes seem to be fixed. The text in Jeremiah, though, is still missing and who knows which other passages aren’t there that I have not yet stumbled upon.
So… thanks a lot for the fixing the footnotes (!), but I do hope the ticket hasn’t been closed yet.
0 -
-
Er zijn erg veel plekken in de logos HSV waar een woord wordt onderbroken door een koppelteken terwijl dat niet hoort. Bijvoorbeeld Mattheüs 18:16 "op-dat". Ik denk dat dit komt doordat er de lijnbreuk is in de fysieke boek. Hebben anderen dit ook opgemerkt? Kan dit gefixt worden?
0