Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend USFM marker \mi to \mi# #131

Closed
rfpng opened this issue Nov 15, 2021 · 4 comments
Closed

Extend USFM marker \mi to \mi# #131

rfpng opened this issue Nov 15, 2021 · 4 comments

Comments

@rfpng
Copy link

rfpng commented Nov 15, 2021

In August 2018 I made a proposal to the Paratext support group to extend the USFM marker \mi to \mi#. Apparently this is now recorded as PTXS-16994 (The original confirmation I received had the number PTXS-17401).

Unfortunately I never heard if my proposal was considered. The issue is still important to me:
In an NT I typeset, \mi1 and \mi2 was used in the glossary. This worked very well but in electronic publishing this causes problems because the process doesn't know about \mi#.

Here is the structure of a glossary entry:
\li1 - Main Entry Headline
\pi1 - Main Entry Description
\mi1 - Indented non-first-line-indented paragraph

The above works fine, but some of the entries also have sub-entries as follows:
\li2 - Sub Entry Headline
\pi2 - Sub Entry Description
\mi2 - Further indented non-first-line-indented paragraph ← Doesn't exist, and that's the problem!

Many paragraph markers have numbered counterparts, but \mi doesn't. It would be very helpful to me if it did!

Thank you very much for considering this.

PS: I'll gladly send you more information about this if needed.

@rfpng
Copy link
Author

rfpng commented Dec 18, 2023

It's now over 5 years since I first proposed extending the USFM marker \mi to \mi#. Any chance for that?
It's definitely still an issue to me!

PS: The original number was Case 39697. Later it became PTXS-17401, then PTXS-29997. (Note: The address in my first email to Paratext Support is no longer valid.)

@rfpng
Copy link
Author

rfpng commented May 24, 2024

I just looked at this issue again and realized that I had actually reported this as a problem already in February 2015! (Over 9 years ago.)
It's still an issue.
I can't electronically publish our glossary in a decent looking format without \mi#.
Thanks for considering this.

@klassenjm
Copy link
Contributor

Dear @rfpng
I have a made a clone of this issue in the current USFM and USFX working group repository.
usfm-bible/tcdocs#75

I'm sorry you have not received the feedback you have requested.

I don't know what digital tools you are working -- but (for now) if those tools support working with user-generated (non-USFM) markup, you could define and add your own markup such as \zmi#

@klassenjm
Copy link
Contributor

This issue is moved to the usfm-bible/tcdocs repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants