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

Speaker identification as default templated curly bracket parsing #6

Open
lmmx opened this issue Nov 22, 2020 · 1 comment
Open

Speaker identification as default templated curly bracket parsing #6

lmmx opened this issue Nov 22, 2020 · 1 comment

Comments

@lmmx
Copy link
Member

lmmx commented Nov 22, 2020

  • Default interpretation of curly brackets set by template, but for most current purposes it will be speaker identification
    • -{abbrev ⠶ full name, role} or -{full name ⠶ abbrev} (should probably standardise this, oops)
      • [usually alongside first speech]
    • -Name {abbrev}-..metadata attachment format
      • usually multiple listed together, prefacing speech as 'dramatis personae'
@lmmx
Copy link
Member Author

lmmx commented Mar 3, 2021

Currently not parsed, e.g. see Q&A lines

-{BJ}
-:Thanks, Beth
-Look, I just really repeat the point I made to Laura.

This should use a Q&A template and the curly bracketed line will be some sort of block-level prefix, making the line "Thanks, Beth" become the 'first line' of the block, therefore triggering a search for the preceding question to tie the answer to

  • Note that this clashes with the interpretation of the config setting
    ALLOW_LIST_WITHOUT_SUFFIX_INIT (True) in tokens.py.
  • This clash should be worked out somehow, as usually it's only fair to tag questions to answers at the block level (and this is consecutive blocks)
    • Perhaps it'd be sufficient to just rely on a question mark suffix on the line (or a 'conjoined' line), but I have not yet implemented logic to indicate 'conjoined' nodes

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

1 participant