sillsdev / sillsdev/ptx2pdf

Trying to use the DoulosSILCipher font to add music notation to liturgy material

Open
#1,048 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
33
Forks
15
PR merge metrics
No merged PRs in 30d

Description

Indonesia (and China and maybe other places) use numeric music notation. The font DoulosSILCipher was developed to allow that to be done in LibreOffice. The font also works in Paratext by copying and pasting from our LibreOffice hymnal:

Image

But when I send the text through PTXprint, the PDF converter mangles the output even if set to use the DoulosSILCipher font:

Image

But if I send the same text through the Export to RTF in LibreOffice, I get this:

Image

And that exported to PDF gets me this:

Image

So it looks like there is something happening in the PTXprint conversion.

Here is the archive:

SLU-PublikasiLiturgiSelaruPTXprintArchive.zip

Thanks for looking into this.

NB: you will notice the lyrics don't align with the notes. This is because Paratext sucks out all the multiple spaces. Any clues for converting those spaces into something that won't be deleted when we paste the songs in?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the conversion using SLU-PublikasiLiturgiSelaruPTXprintArchive.zip and compare the PTXprint PDF with the LibreOffice-exported PDF. Start by tracing PTXprint's font handling for DoulosSILCipher and the generated XeTeX output. Done means the numeric music notation renders correctly; the lyric-spacing question is a separate follow-up.

Written by the indexing model from the issue text.

Assessment

Tech stack
latex, python
Domain
desktop, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.