Bug: Apocalypse of Baruch (Syriac)
I want to copy a location from the Leiden Peshitta edition of the Apocalypse of Baruch, but every time I try to do this Logos crashes immediately.
Edit: I can copy the location as an url without any problems, but with all other formats (html/wiki/rl) Logos will crash.
Comments
-
H.-J.van der Wal said:
I want to copy a location from the Leiden Peshitta edition of the Apocalypse of Baruch, but every time I try to do this Logos crashes immediately.
Edit: I can copy the location as an url without any problems, but with all other formats (html/wiki/rl) Logos will crash.
can you share the url for adventurous fellow users and Logos personnel to recreate? And some info regarding your system and the version you're running?
Best would be to crosspost in a Logos-version dependant forum, or Desktop beta, since Logos personnel don't roam General as often as those other forums.
Have joy in the Lord!
0 -
NB.Mick said:
can you share the url for adventurous fellow users and Logos personnel to recreate? And some info regarding your system and the version you're running?
logosres:lpesh;ref=BiblePESH.ApocalypseofBaruch
NB.Mick said:Best would be to crosspost in a Logos-version dependant forum, or Desktop beta, since Logos personnel don't roam General as often as those other forums.
Danke für den guten Rat!
Edit: Crosspost - http://community.logos.com/forums/p/75063/524925.aspx#524925
0 -
I can reproduce this and have filed a bug.
0 -
I've added this info to the dev ticket, but as a work-around, the link seems to be missing underscores. The following link does parse:
logosres:lpesh;ref=BiblePESH.Apocalypse_of_Baruch
0 -
Yes, this works.Vincent Setterholm said:I've added this info to the dev ticket, but as a work-around, the link seems to be missing underscores. The following link does parse:
logosres:lpesh;ref=BiblePESH.Apocalypse_of_Baruch
george
gfsomselיְמֵי־שְׁנוֹתֵינוּ בָהֶם שִׁבְעִים שָׁנָה וְאִם בִּגְבוּרֹת שְׁמוֹנִים שָׁנָה וְרָהְבָּם עָמָל וָאָוֶן
0 -
This has been fixed for a future release.
0 -
Chris Robbers (Logos) said:
This has been fixed for a future release.
This should be fixed in 5.2 Beta 3.
0