Open ch-sander opened 2 years ago
Maybe also |F142| can be interpretated more easily if put |p. 142| ?
And somethings seems to be wrong with the link F141 I don't get the canvas to be displayed in the bottom frame...
Angled brackets crossing column or pages is a data problem. It needs to be corrected in the source text. The app is just showing what is there.
I didn't have any problem with F141:
You can show me next time we meet if it persists.
Okay! But can't the view "interpret" linebreaks and display a different character? Or do you suggest find&replace in data source? If I remember correctly, in the data angled dashes (not brackets...I mean ¬) are used throughout.
As for F141, I now get this view:
click on "toggle show text lines" and it will toggle back to full page view.
(The buttons in the image viewer are confusing and need to be redone (someday!))
Thnx. A lot of space between the buttons and the canvas, though (in my browser)
Okay! But can't the view "interpret" linebreaks and display a different character? Or do you suggest find&replace in data source? If I remember correctly, in the data angled dashes (not brackets...I mean ¬) are used throughout.
Data has break="no"
within <lb>
right?
If a word breaks across two pages, we still have an angled dash instead of the regular character.
Open in BrowserStack
Submitted from Netlify Deploy Preview #113