Repository navigation
feat: localize ablation, data card, and split/synthetic check reports - #541
Merged
Merged
Conversation
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR localizes the reports from the data-ablation and LLM-data features into all 40 reporting languages: (1) the
Ablationplan, report, andannotate()notes; (2) data cards fromto_data_card()(both the Hugging Face card and the datasheet); and, (3) thecheck_splits()andcheck_synthetic()reports.A new internal
_report_text.pymodule formats the strings, with numbers for the locale, singular forms where a language has them, and right-to-left layout for Arabic, Hebrew, and Persian.lang=andlocale=are now arguments ofAblation.plan(),Ablation.get_tabular_report(),Validate.to_data_card(),SplitCheck.get_tabular_report(), andSyntheticCheck.get_tabular_report().Ablation and card output use the validation's language by default, and the split and synthetic reports use English. Issues, reprs, and the card's YAML front matter stay in English. A new test checks that every string has every language, with the same fields and markup as English.