Comments (2)
@mvahowe
Here is the UI prototype which appears very numbers focused:
It seems the better way to handle this is showing the verses as strings (with same ID as in the USFM) rather than coercing to numbers. For example we show "1-2" in the case of a verse span. And if we treat the verses as a list we can retain the order that was in the USFM. I would approach chapters similarly.
from bible-reference-rcl.
Notes from Zulip with helpful background info:
Mark Howe:
Bruce McLean said:
- Paragraphs seem to be more formatting tips.
Many translators would say the exact opposite, ie that the biblical narrative is structured in books, pericopes, sentences, phrases... and that chapter/verse is just decoration. I've heard translators say that they'd like to dispense with chapter/verse altogether (although of course, in practice, that's impossible to sell to Joe Christian).
I'm not suggesting navigation by paragraph but, eg, I think the list of verses needs to display verse ranges where there are verse ranges, and it probably needs to display out-of-order verses out of order. And, if we're tackling the deuterocanon (and maybe even if we're not) we need to contend with verses before chapters and the Greek Esther/Daniel problem (where Greek and Hebrew content get mixed up together depending on your tradition).
Mark Howe: The Paratext solution is to use the underlying "standard" versification and then do the letters and repeat chapters as \cp markup. But end users want to see the same chapter numbers/letters as their printed Bible. The problem here is that USFM was designed for typesetting, where chapters are just another block of text (or dropcap, or whatever). The need to say "what goes in Chapter X" or to provide navigation beyond flicking through the pages, is new in digital applications, and I don't think USFM has really caught up. USX 3 has chapter and verse milestones, but this just seems to make things even more confusing, especially as Paratext is a bit random about where it drops the end milestones.
Mark Howe: If you view source on YV (at least last time I looked), the chapters 3, B and 3 are something like 3, 3_1 and 3_2, which reflects the underlying Paratext USFM structure.
Mark Howe: But it feels to me like this is a typically "Bible Consultant" approach, ie it isn't very church (tradition) - centric.
Mark Howe: As I said somewhere above, it's possible that some of these problems can be solved by decree. eg "We don't support translation from the Septuagint"; "We assume a 39-book Hebrew OT" etc. I think that's ok as long as it's ok with your current and future user base, and as long as the list is explicit somewhere.
from bible-reference-rcl.
Related Issues (20)
- It would be nice to be able to resize cards by dragging on any edge HOT 1
- Font sizing does not work on tA, tW, and tQ resources HOT 1
- Font size settings are only persisted for scripture resources HOT 1
- It would be nice to be able to resize cards by dragging on any edge HOT 2
- It would be nice to be able to resize cards by dragging on any edge HOT 1
- There are several differences between the tN columns displayed in tC Create 1.0 and tC Create 2.0 HOT 1
- It would be nice to have tooltips on the chevrons in the navigation bar HOT 1
- Close button(X) required in the feedback form
- Email field in the feedback form is not validated.
- Markdown view not available for translationWords Article
- tWL should be viewable in tsv format HOT 5
- Release 0.9 HOT 1
- Add primitive Undo/Redo support for resource edits
- translation-helps-rcl HOT 1
- Upgrade all dependencies to latest versions HOT 1
- Fix error messages resulting from upgrading to latest versions HOT 1
- [SPIKE] Cypress Recordings are no longer working in GitHub actions. HOT 1
- Fix add TSV when no existing TSV Items
- Fix Add TSV when no existing TSV Items in Resource
- When blank translation question is added, it does not show on Gateway Edit unless question/answer is input
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bible-reference-rcl.