LDHB and LHDOT using different symbol sets
I am looking through the new Discourse Hebrew tools pre-released this week. I realize they are a work in progress, but want to share some observations for the developers.
I am using Logos 4.6 SR2 on a Win7 64-bit computer.
When I compare the glossaries of the Discourse Hebrew Bible to the High Definition Old Testament it appears the LDHB is using the same symbol set as the New Testament equivalent. (see screenshot). I prefer the symbol set on the left.
When I look in the actual LDHB and LHDOT, it appears they both are using the symbol set that I like less. (see screenshot)
I am also a little confused as to why the discourse markers for the two glossaries are not the same. I would think that a Forward-pointing Reference and Target (item 1.2 in LDHB Glossary) and Forward-Pointing Reference and Target (item 2.1 in LHDOT Glossary) would be the same point in the outline and use the same symbols since both resources are supposed to be drawing attention to the linguistics of the Hebrew text.
Making Disciples! Logos Ecosystem = LogosMax on Microsoft Surface Pro 7 (Win11), Android app on tablet, FSB on iPhone & iPad mini, Proclaim (Proclaim Remote on Fire Tablet).
Comments
-
Hey Guys,
We're looking into this issue, and we are currently thinking the problem may exist in the Windows WPF Fontcache. WPF caches our fonts, and the cached version may not be up to date with the current revisions. To attempt to resolve this, please try the steps below to refresh your fontcache.
1.
Go
to Start (XP=Start>Run…) and type: services.msc2.
Open
Services.3.
Locate
and Stop the “Windows Presentation Foundation Font Cache 3.0.0.0” service.4.
Delete
the Fontcache:Deleting the Fontcache File in Vista or Windows 7:
Navigate
to: C:\Windows\ServiceProfiles\LocalService\AppData\LocalDelete
the “FontCache3.0.0.0.dat” file (This file will be rebuilt when Windows
starts)Deleting the Fontcache File in Windows XP:
Navigate
to: C:\Windows\Microsoft.NET\Framework\v3.0\Move the WPF folder
to the DesktopOpen Add/Remove
ProgramsRepair Microsoft
.NET Framework 3.5 SP15. Turn
the WPF Service back on, or Restart the Computer.0 -
We tried it just now on a colleague's computer who had the same
problem and it worked like a charm. Hoping for similar results for
y'all. Post back to let us know how it went.0 -
Mike Bryant (Tech) said:
Deleting the Fontcache File in Vista or Windows 7:
Navigate
to: C:\Windows\ServiceProfiles\LocalService\AppData\LocalI got this far and was able to navigate as deep as LocalService but AppData is not a viewable folder. May it be a hidden folder?
Making Disciples! Logos Ecosystem = LogosMax on Microsoft Surface Pro 7 (Win11), Android app on tablet, FSB on iPhone & iPad mini, Proclaim (Proclaim Remote on Fire Tablet).
0 -
by typing the location into the search bar (rather than drilling down through folders) I was able to do step 4. When I finished Step 5...
IT IS BEAUTIFUL!! THANK YOU LOGOS TEAM, you're the best!
Making Disciples! Logos Ecosystem = LogosMax on Microsoft Surface Pro 7 (Win11), Android app on tablet, FSB on iPhone & iPad mini, Proclaim (Proclaim Remote on Fire Tablet).
0 -
Yeah! Happy reading, but be sure to get to bed at a reasonable hour. [:)]
0 -
David Thomas said:
No, NO, NO!!! Don't these Logos lowbrows know ANYTHING!?!?!?
THIS IS EVIDENCE OF MULTIPLE DOCUMENTARY TRADITIONS (J, E, P, AND D) THAT A REDACTOR (OR MULTIPLE REDACTORS) RATHER INEPTLY JUGGLED INTO PLACE.*
ASUS ProArt x570s Creator, AMD R9 5950x, HyperX 64gb 3600 RAM, ASUS Strix RTX 2080 ti
"The Unbelievable Work...believe it or not." Little children...Biblical prophecy is not Christianity's friend.
0 -
Mike Bryant (Tech) said:
Deleting the Fontcache File in Vista or Windows 7:
Navigate
to: C:\Windows\ServiceProfiles\LocalService\AppData\LocalDelete
the “FontCache3.0.0.0.dat” file (This file will be rebuilt when Windows
starts)This fixed it for me initially, but after a using Logos for a while, suddenly the strange symbols showed up again (without a restart of Logos or Windows!). :-( I repeated the same process, with similar result (only this time it worked fine for about 2 hours).
Any ideas folks what this can be?
0 -
Andre,
I've seen a few cases where the WPF Fontcache doesn't seem to like to update. I'm not really an expert on exactly how Windows manages and caches its fonts, but I have suspected that the old font may be held in Temporary Files, and find its way back into the cache. If this is the case, it may be helpful to run the "Disk Cleanup" utility and clean our your Temporary Files before turning the service back on. It might also help to delete any other files in the fontcache folder (files specifically, not folders), if any extra caches have been generated.
I would also refrain from turning the service on manually, and instead reboot.
Let me know if it helps.
0 -
David Paul said:
No, NO, NO!!! Don't these Logos lowbrows know ANYTHING!?!?!?
THIS IS EVIDENCE OF MULTIPLE DOCUMENTARY TRADITIONS (J, E, P, AND D) THAT A REDACTOR (OR MULTIPLE REDACTORS) RATHER INEPTLY JUGGLED INTO PLACE.*
David maybe it does point to evidence of J,E,P, & D, but that's not the point of these resources. What you see an inept juggling into place of multiple documentary traditions - how is that going to help in sermon preparation - really you are not going to edify the body by saying, well see these repeated words, that's just cause I think the editor was a bit inept. . The editors of this resource have a different explanation, one that can be of practical use in sermon preparation, one that can help draw out what God intended the audience to understand from the text., and one that helps me think more deeply about what's going on in the text. I don't believe God inspired people to produce ineptly edited texts to be the record of his dealings with humanity, his primary source of revelation to those who didn't see the resurrection first hand. But that's just my thoughts.
0 -
Working well for me at this point Mike. Thanks.
0 -
Mike Bryant (Tech) said:
I've seen a few cases where the WPF Fontcache doesn't seem to like to update. I'm not really an expert on exactly how Windows manages and caches its fonts, but I have suspected that the old font may be held in Temporary Files, and find its way back into the cache. If this is the case, it may be helpful to run the "Disk Cleanup" utility and clean our your Temporary Files before turning the service back on. It might also help to delete any other files in the fontcache folder (files specifically, not folders), if any extra caches have been generated.
Hi Mike! I
have followed your instructions, and they work. But every time after restarting
Windows, I’m back to the same odd symbols. I don’t know what else more I can do….
0 -
André Kamphuis said:
Hi Mike! I have followed your instructions, and they work. But every time after restarting Windows, I’m back to the same odd symbols. I don’t know what else more I can do….
Ah! Me too! I thought this was resolved but it is not, it keeps coming back!
0 -
Mike Bryant (Tech) said:
Andre,
I've seen a few cases where the WPF Fontcache doesn't seem to like to update. I'm not really an expert on exactly how Windows manages and caches its fonts, but I have suspected that the old font may be held in Temporary Files, and find its way back into the cache. If this is the case, it may be helpful to run the "Disk Cleanup" utility and clean our your Temporary Files before turning the service back on. It might also help to delete any other files in the fontcache folder (files specifically, not folders), if any extra caches have been generated.
I would also refrain from turning the service on manually, and instead reboot.
Let me know if it helps.
FYI, The original fix that Mike posted worked for me. Having seen Andre's recurrence of the problem I went ahead and followed the above steps just to preclude a problem. So far the old font symbols have never returned for me...YET. [:D]
Making Disciples! Logos Ecosystem = LogosMax on Microsoft Surface Pro 7 (Win11), Android app on tablet, FSB on iPhone & iPad mini, Proclaim (Proclaim Remote on Fire Tablet).
0 -
André Kamphuis said:Mike Bryant (Tech) said:
I've seen a few cases where the WPF Fontcache doesn't seem to like to update. I'm not really an expert on exactly how Windows manages and caches its fonts, but I have suspected that the old font may be held in Temporary Files, and find its way back into the cache. If this is the case, it may be helpful to run the "Disk Cleanup" utility and clean our your Temporary Files before turning the service back on. It might also help to delete any other files in the fontcache folder (files specifically, not folders), if any extra caches have been generated.
Normal
0
21
false
false
false
NL
X-NONE
X-NONEHi Mike! I
have followed your instructions, and they work. But every time after restarting
Windows, I’m back to the same odd symbols. I don’t know what else more I can do….Andre, I noticed the visual filter you have applied in the LDHB. I have a visual filter for verb tense that is based upon AFAT tagging but that visual filter does not appear when I open the 3 overlapping circles symbol in this resource. How did you create the visual filter you have applied in this screenshot? Are the LDHB and HDOT tagged with AFAT? I can use the filter in the regular ESV, but not in this resource.
.I am sorry if I am hijacking this thread into a new direction, but it does deal with the same resources in the original post.
Making Disciples! Logos Ecosystem = LogosMax on Microsoft Surface Pro 7 (Win11), Android app on tablet, FSB on iPhone & iPad mini, Proclaim (Proclaim Remote on Fire Tablet).
0 -
André Kamphuis said:
Hi Mike! I
have followed your instructions, and they work. But every time after restarting
Windows, I’m back to the same odd symbols. I don’t know what else more I can do….Hi Andre,
This is venturing a little beyond Logos and into Windows Font management. I can tell you what I would try, but I'm not familiar enough with how Microsoft manages their fontcache to provide a definite answer. The previous solution should have worked already, based on the documentation Microsoft provides.
Delete the fontcache:
- Per previous instruction, end the WPF Fontcache Service.
- Delete the "Fontcache..." file(s).
Reinstall the Symbols font.
- Open C:\Windows\Fonts.
- Locate and Delete the "LogosSymbolUnicode" font.
- Run the "Disk Cleanup" utility to delete Temporary Files.
- Reboot the computer.
- Reinstall the LogosSymbolUnicode font (you can download it here).
Hopefully that will do it for you.
0 -
Mike, many thanks for your help! This seems to work now. Let's hope it will keep working! [:)]
0 -
David Thomas said:
Andre, I noticed the visual filter you have applied in the LDHB. I have a visual filter for verb tense that is based upon AFAT tagging but that visual filter does not appear when I open the 3 overlapping circles symbol in this resource. How did you create the visual filter you have applied in this screenshot?
Hi David,
This is what I did:
Quite simple, but it works in all my Hebrew texts. Hope this helps. André
0
