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

Update bios.py #1

Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open

Conversation

chhotii-alex
Copy link

Did Zambia change how it decides whom to list in PubBio.csv? We are seeing people listed who aren't even attending this year. Changed this to suppress printing any participant with no sessions.

chhotii-alex and others added 6 commits January 9, 2020 15:44
Did Zambia change how it decides whom to list in PubBio.csv? We are seeing people listed who aren't even attending this year. Changed this to suppress printing any participant with no sessions.
On a Macintosh, InDesign's interpretation of ASCII-WIN formatted tagged text is wacko. Special characters (curved quotes, dashes) become various accented letters. I tried using UNICODE for tagged text but that was a complete nightmare. Then I found documentation giving a way to insert various special characters into tagged text as tags.
Much snazzier and pythonic now. Rather than special-case listing a small number of known troublesome punctuation characters, encode EVERYTHING other than the most consistently encoded ASCII characters using the <0xnnnn> where nnnn is the code point number in hex. Limited testing with ä, ö, ü suggests that this works generally for both our troublesome special punctuation and accented letters, maybe for all Unicode characters. Of course, if a foreign character has no glyph in the current font, you may still be SOL, I would guess. But we should be able to deal with reasonably common accented versions of Roman characters correctly now.
An actually interesting and useful warning to be issued while parsing PubsBio.py! A comma in a participant's name completely confuses the formatting of the list of participants of a session. The work-around (from Paul) is to put the participant in the [participant change name] of the .cfg file. However, it would be good to know what names require this attention, before proofreading the whole pocket program.
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

Successfully merging this pull request may close these issues.

1 participant