-
Notifications
You must be signed in to change notification settings - Fork 13
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
Bad line-breaks in long words, consider breaking at hyphenation #51
Comments
This ought to close sanger-pathogens#51, not sure if it should be used on all qualifiers or (as implemented) just the product?
According to https://docs.python.org/2/library/textwrap.html the Adding
This passes the ENA validation tool, although it isn't quite as strict as the Prokka Genbank wrapping. Pull request to follow... |
Could you reopen this issue as discussed on #68 please? |
It seems that That's generally fine, but we have a problem if the hyphenated term itself is about 60+ characters, meaning even when put on a line on its own once the 21 character The "about" is because things are much tighter if this is the first word as you also have the prefix Sadly if we stick with the default of |
Thanks for filing the python bug. This format is a royal pain in the modern age. |
e.g. Prokka GFF file containing this in column 9:
The EMBL file from converting the GFF gave:
Notice this has inserted the line-break mid-word, which is bad.
The Prokka GBK file had:
Notice it broke on the hyphen, which is much better.
The text was updated successfully, but these errors were encountered: