-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
fix #572: [FR] Tweak handling of the 'composé de' template #617
Conversation
Sourcery Code Quality Report✅ Merging this PR will increase code quality in the affected files by 0.27%.
Here are some functions in these files that still need a tune-up:
Legend and ExplanationThe emojis denote the absolute quality of the code:
The 👍 and 👎 indicate whether the quality has improved or gotten worse with this pull request. Please see our documentation here for details on how these metrics are calculated. We are actively working on this report - lots more documentation and extra metrics to come! Let us know what you think of it by mentioning @sourcery-ai in a comment. |
b = b1 + b2 + b3 + b4 | ||
is_derived = b == "1000" or b == "0100" or b == "1020" | ||
|
||
def word_tr_sens(w: str, tr: str, sens: str) -> str: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This function could be out of the render_compose_de
function and be reused in other templates such as etyl.
However, it's a hack regarding the italic handling. The right way to do it it's to check if each char of the words are "Latin", "Common" or "Inherited" in the script ranges from https://fr.wiktionary.org/wiki/Module:donn%C3%A9es_Unicode/data/script_ranges
I tried another way in render_etyl but it's not working for d’ (not the apostrophe...)
@BoboTiG WDYT ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could move the function and handle unicode chars correctly, yes. It could be done in another PR to keep this one as-is (already quite complex).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What an horrible template to handle :)
Yes... it could be made more "python" I guess, but I also see some value in being close to the wikicode... |
I was not talking about the code ;) Anyway, good work 👍 :) |
./check.sh
run and eventual issues fixed.