diff --git a/assets/vanilla-i18n/English.json b/assets/vanilla-i18n/English.json index 21c507a..d4cc2a7 100644 --- a/assets/vanilla-i18n/English.json +++ b/assets/vanilla-i18n/English.json @@ -1 +1 @@ -{"nav": {"home": "Home", "form": "Record New Data", "catalog": "Browse the Catalog", "charter": "Data reuse charter", "team": "The Team", "tools": "Tools", "models": "Models", "actions": "Github Automation"}, "footer": {"team": "Who are the people behind HTR-United?"}, "team": {"title": "Editors", "alix": "I am a PhD student in Digital Humanities, member of the ALMAnaCH team at Inria-Paris and part of the CRIHN at the University of Montreal, enrolled both at the University of Montr\u00e9al and the \u00c9cole Pratique des Hautes \u00c9tudes (Paris). Under the supervision of Laurent Romary, Emmanuel Chateau-Dutier and Michael Sinatra, I work on the appropriation of automatic transcription tools (HTR) by the DH community and by cultural institutions. As a R&D engineer for Inria, I colaborated with numerous projets involving HTR, including LECTAUREP (French national archives), TIME US (ANR) and DAHN.", "thibault": "I am the head of the MA \"Digital Technologies Applied to History\" (Technologies Num\u00e9riques Appliqu\u00e9es \u00e0 l\u2019Histoire) at the \u00c9cole Nationale des Chartes (Paris, France). I am a classicist who served as an engineer both at the Centre for eResearch (Kings College London, UK) and the Humboldt Chair for Digital Humanities (Leipzig, Germany) where I developed the data backbone of the future Perseus 5 (under the CapiTainS.org project). I am a founding member of the Technical Committee for the Distributed Text Services standard ( w3id.org/dts ). The major part of my teaching is dedicated to patrimonial data engineering, namely digital data management, development good practices, standards for communication and programming languages. My research mainly focus on automatically processing ancient languages through deep learning and the distribution of corpora."}, "main": {"desc": {"main": "HTR-United is a catalog of metadata on training datasets (ground truth datasets) available for the creation of transcription or segmentation models. The metadata are provided by the creators of these datasets. 
HTR-United offers a schema to homogenize descriptions of datasets, as well as recommendations on how to organize a data repository, and tools for quality control and continuous documentation. 
HTR-United is an ecosystem relying on a Github organization, transparent and open to all, using minimalistic developments to facilitate its maintenance. 
HTR-United was born from the necessity -for projects- to have access to various types of ground truth to rapidly train models on smaller corpora.", "use": {"p1": "HTR-United is a catalog of datasets and eventually models for (handwritten) text recognition. It takes the form of a YAML file containing metadata essential to identify datasets compatible with your document and to access them. You can download datasets or contact their owner(s), according to the modality they specified.", "p2": "Besides information on how to reach the data, the catalog gathers metadata describing the writings presented in the datasets (temporality, number of hands, features) and the conditions of creation (authority, annotation rules, format).", "p3": "It is also possible to browse through the calalog on this website"}, "provide": "

You can contribute to the HTR-United project by referencing your ground truth dataset in the catalog. No need to load your data onto Github, they can be hosted anywhere you want! You only need to generate the metadata thanks to our form and to add them either in your own repo or in the project's repository, depending on your situation. These metadata will describe your dataset and the conditions of access and reuse.

Your data can originate from any OCR/HTR software, or even from a manual process, and can be shared following various standards (ALTO XML or PAGE XML). To make your dataset useful to other projects, it needs to be composed of at least: images, their transcriptions, and metadata describing among other things the rules set to produce the annotation.

To help you understand which step to follow in order to contribute to the project, check out our scenarios!

", "sc1": "Your data is not yet published. You can then join the HTR-United Github organization and create a new repository dedicated to your data. If your images are hosted somewhere else and can easily be downloaded (e.g. via a IIIF manifest), it is possible to only add the transcription as XML files, along with a file presenting the dataset (README) and a license. You can trigger an update in the catalog's content by adding in your repository an htr-united.yml file containing the metadata generated with our form . A template is offered here: https://github.com/HTR-United/template-htr-united-datarepo . You can take inspiration from the repository template offered here: https://github.com/HTR-United/template-htr-united-datarepo .", "sc2": "Your data are not yet published and you do not wish to publish them within the HTR-United Github organization. No problem! You can publish your data on any platform, for example your own Github space or Zenodo. If your images are hosted somewhere else and can easily be downloaded, your repository can solely contain the transcriptions as XML files, as well as a basic documentation in a README file and a license. Once the repository is ready, you can trigger an update on the catalog by adding a YAML file generated with our form within the catalog folder in HTR-United's main repository.", "sc3": "Your dataset is already published online and freely accessible. Verify that the dataset is associated with an explicit license, that the transcription files follow the accepted formats (ALTO or PAGE), that the image are either published along with the transcription or that they can be easily accessed (via a IIIF manifest for example) and finally that the dataset is sufficiently described (including transcription rules). Then you can generate a structured description with our form and add the YAML file within the catalog folder in HTR-United's main repository. It will trigger an update on the main catalog.", "sc4": "You cannot freely share your data (either the images or the transcriptions) but you still wish to contribute to the HTR-United project. You can create a repository within the HTR-United Github organization only made of a README file dedicated to describing the data. Remember to give any relevant contact information in order to allow future users to request an access to the data. Once the repository is ready, you can generate a structured description with our form and add the YAML file within the catalog folder in HTR-United's main repository. It will trigger an update on the main catalog."}, "title": {"use": "Use data referenced in HTR-United", "provide": "Provide data to HTR-United", "scenarios": "Scenarios", "scenario": "Scenario"}, "btn": {"download": "Download the catalog", "catalog": "Browse the catalog", "cite": "Cite HTR-United", "generate": "Generate a description", "scenarios": "Check out the scenarios", "faq": "Go to FAQ", "use": "Use the data", "provide": "Provide data"}}, "cat": {"title": "Catalog", "nota": "The languages used to introduce the datasets depend on language used by the author(s) of a descripion.", "resultCount": "Number of results", "filters": "Filters", "authors": "Authors", "showGuidelines": "Show Transcription Guidelines", "showCitations": "Show Citation Informations", "descCount": "Statistics about the results", "countUnit": "Unit", "countAmount": "Amount", "countProjects": "Projects with this unit", "countChars": "Characters", "countLine": "Lines", "repository": "Data repository", "link": "Link", "software": "Software", "citationFile": "Citation File (CFF)", "share": "Share", "tweet": "Tweet", "full_record": "Complete record"}, "catalog": {"projectName": "Project", "all": "All projects", "script": "Script", "allLanguage": "All languages", "allScript": "All scripts", "language": "Language", "includeManuscript": "At least half is manuscript", "includePrint": "At least half is printed"}, "tools": {"title": "Tools", "seeDemo": "See demo", "intro": "In order to produce good data and to ensure an easy way to control or quantify the data produced, we offer a certain set of tools with tutorial (upcoming) on how to use them both in a standalone way or in a continuous integration way.", "humg": "HUMGenerator (Htr United Metadata Generator) generates metadata, specifically metrics for your corpora. It's specifically being used to generate the volume key of the catalog schema. It can generate a character count table, to help users choose new kind of ground truth to cover more characters.", "htruc": "HTRUC allows for controlling that the htr-united catalog file is parsable and HTR-United compliant. HTRUC is also meant to offer the tools to parse, augment and compile statistics about catalog file(s). This allows the HTR-United central repository to build a general catalog for everyone's use, see the main catalog. It can also be used with HUMGenerator to update a catalog file with new volumes.", "htrvx": "HTRVX focuses on controlling the quality of the XML. It provides many options in terms of quality control: schema validation (checking that your ALTO or PAGE is okay), empty line or children-less region detection, Segmonto compatibility for segmentation (see Segmonto's Ontology documentation)", "chocomufin": "ChocoMufin focuses on the characters that are used in the ground truth. It can either help you have an overview of the character used, can be used to control which one are used (to avoid having two characters for the same purpose, which can be common with historical documents) or, using a conversion table, it can be used to normalize a whole set of ground-truth."}, "form": {"download": {"dl": "Download", "text": "this file below or copy the content and upload it using this ", "push_link": "link"}, "desc": {"main": "HTR-United is a Github organization without any other form of legal personality. It aims at gathering HTR/OCR models for and transcriptions of all periods and style of writing, mostly but not exclusively in French.
It was born from the mere necessity -for projects- to possess potentiel ground truth to rapidly train models on smaller corpora."}, "steps": {"title": "Steps"}, "step1": {"title": "Fill the form", "desc": "Follow the instructions and examples if necessary. Some items are optional, but you should try to provide as much detail at possible. You can also contact us by opening an issue."}, "step2": {"title": "Click on \"Get formatted metadata\"", "desc": "And copy the output !"}, "step3": {"title": "Add the result to HTR-United's catalog", "desc": "By creating a new file inside our catalog/ folder, following the link provided after you generated the metadata. You can also paste the content in your own htr-united.yml file inside your repository."}, "form": {"head": "Fields followed by a * are the only ones required."}, "title": {"ds": "General information about the dataset", "project": "General information about the project", "data": "General information about the data", "detail": "Detailed information about the data", "generate": "Generate the htr-united.yml file"}, "play": "Play or restart", "field": {"ds_title": "Repository's or dataset's title", "repolink": "Link to repository", "ds_desc": "Short description", "cff": {"link": "Link to a CITATION.cff file", "info": "CITATION.cf files allow for generating quick APA citations or Bibtex ones on github for example. See:"}, "license": "License", "std": "Format Standard", "linepair": "Image-Text line pairs", "project": {"name": "Project's name (if different from the repository/dataset's one)", "link": "Link to project's website"}, "std_info": "This is a non-exhaustive selection of license options.", "software": "Software use to produce the data", "software_placeholder": "You can use the following buttons to populate the field.", "authors": "Authority and role(s)", "member": {"add": "Add a member", "rm": "Remove a member", "name": "Author's first name", "surname": "Author's last name", "transcriber": "Transcription", "aligner": "Alignment", "mainCreator": "Project Manager", "qualityControl": "Quality Control", "digitizer": "Digitization", "support": "Support", "status": "This contributor is an institution", "roles": "Roles"}, "year": {"start": "Source Start-Year", "end": "Source End-Year", "info": "For centuries, please prefer the use of 1200 when a dataset starts in the 13th century and 1299 when it ends in the 13th century. Dates do not need to be precise."}, "languages": {"label": "Language(s)", "helper": "To ease data entry, default values are already selected. Just click on it to deselect the one you don't want."}, "scripts": {"label": "Script", "helper": "To ease data entry, default values are already selected. Just click on it to deselect the one you don't want."}, "scripts-details": {"helper": "Only when necessary, you can add a qualifier to a script. For example: Latf + Kurrent (to designate the German variant to Fraktur)."}, "script": {"type": {"label": "Script type", "select": {"only-manuscript": "Manuscript only", "all": "All", "only-typed": "Typed only", "mainly-manuscript": "Mainly manuscript", "mainly-typed": "Mainly typed", "evenly-mixed": "Evenly typed and manuscript"}}}, "hands": {"label": "Number of hands (or fonts)", "select": {"1perfile": "1 per file", "1perfolder": "1 per folder", "less10": "Less than or equal to 10 (few)", "more10": "More than 10 (many)", "unknown": "Unknown"}}, "prec": {"label": "Precision", "select": {"exact": "Exact value", "estimated": "Estimated value"}}, "guidelines": {"label": "Transcription guidelines", "info": "Guidelines used to transcribe the resources (normalization, resolution of abbreviation, correction of mispelling, etc.)"}, "qual": {"label": "Estimated quantity", "select": {"lines": "Lines", "pages": "Pages", "characters": "Characters", "regions": "Zones", "files": "XML Files"}}, "flags": {"label": "Flags", "automaticallyAligned": {"label": "Automatically aligned", "helper": "This flag is applicable if you used automatically alignment and did not perform a fully manual alignment review"}}, "src": "Sources", "apa": "We prefer APA references, which can look like the following Allport, G. W. (1930\u20131967). Correspondence. Gordon W. Allport Papers (HUG 4118.10), Harvard University Archives, Cambridge, MA, United States., see APA Style, but simpler formats are okay too. The link or the APA reference are sufficient but you can provide both"}, "input": {"reponame": "Repository's title", "repolink": "Link to repository", "cff": "Link to a CITATION.cff file", "projectname": "Project's name", "projectlink": "Link to project's website (if applicable)", "src": "Link to the source or a catalog description", "datebegin": "Example: 1800", "dateend": "Example: 1899", "guidelines": "Transcription guidelines", "quantity": "Example: 200", "apa": "APA Reference for a source"}, "btn": {"get": "Get formatted metadata"}, "finale": {"steps": "Steps to follow", "step1": "(1) Get the content using either method:", "download": "Download", "copy": "Copy", "step2": "(2) Then add it to the HTR-United catalogue via a file c\u0155eation or an issue", "notWorking": "If this doesn't work with the above links, open an issue on the HTR-United repository:", "newFile": "Create the file", "newIssue": "Open an issue"}}, "actions": {"introduction": "Github Actions are a way to run specific code everytime you change your data. The following form will generate a configuration file to use our 4 tools automatically and ensure both complete compatibility with the HTR-United initiative and high quality data. Some options below will focus on controling the data, your cataloging file or simply automatically updating it with the metrics of your choice !", "generalInformations": "General information on your data repository", "htrUnitedFilename": "Filename of your HTR-United metadata file (catalog)", "dataUnixPath": "Path to your XML data (UNIX format)", "branchName": "Main branch name", "activateHTRUC": "Activate", "activateHUMG": "Activate", "updateCatalogFile": "Update the catalog file", "formatGithubUrl": "Address without the github.com domain, only username/repository", "generateBadge": "Generate badges", "gitRelease": "Automatically create a release", "activateHTRVX": "Activate", "activateSegmonto": "Test your compatibility with Segmonto", "activateEmptyLine": "Check for empty lines or childless regions", "activateRaiseEmptyLine": "Raise an error when empty lines or childless regions are found", "activateXSD": "Check XML Schema", "activatechocoMufin": "Activate", "chocoMufinMode": "Mode", "htrUnitedFilenameHelp": "This file should have been generated with the form on this website: it describes your whole repository with metadata, make sure you did that first ! This file is generally named htr-united.yml and should be at the root of your github repository.", "dataUnixPathHelpP1": "This path is the path on your repository. Use * for a filename wildcard, ** for a folder wildcard. You can have a single path, such as ./data/*.xml or multiple, such as ./french/data/*.xml ./english/data/*.xml. If you have a structure such as ./data/a_book/some.xml and ./data/b_book/some.xml, the UNIX path is ./data/**/*.xml", "branchNameHelp": "Generaly main or master.", "dataUnixPathHelpP2": "In the example on the right, if TNAH-2021-Project-Correspondance-Berlioz is the root of your data repository, the path to get all XML would be donnees/**/*.xml", "activateHTRUCHelp": "This will run a test on your htr-united.yml and makes sure it's compliant with the schemas. If the schema evolves, it allows you to ensure your compatibility with it.", "activateHUMGHelp": "This will produces in depth overview of how many characters, zones, lines and pages you have, but also gives you the amount of zone or lines per type if you typed your zones and lines.", "updateCatalogFileHelp": "Using the computed metrics (line, characters, files, zones), update the volume information of the cataloging file automatically.
This automatically pushes new files to your repository. This does not damage your data.", "generateBadgeHelp": "Using this, badges will be generated, such as which you can include in your README file to show how cool you are.
This automatically pushes new files to your repository. This does not damage your data.", "gitReleaseHelp": "Creates a Github release everytime master is changed. Coupled with Zenodo, this will allow you to have long term preservation and DOI (Digital Object Identifier) for your repository !", "activateHTRVXHelp": "This will help you make sure that your XML is valid and follows some other specifications.", "activateSegmontoHelp": "Segmonto is an ontology for typing Zones (sometimes called Regions) and Lines. This ensures you are compatible with it. cf. Publication or Segmonto Guidelines.", "activateEmptyLineHelp": "This will warn you about empty lines or regions without lines, without raising an error: this won't make the test fail !", "activateRaiseEmptyLineHelp": "This is used on top of the former check. This will raise an error if a line has no text or if a region has no lines.", "activateXSDHelp": "This just makes sure you are compatible with the XML schema. This should always be the case if you use a Graphical User Interface such as Transkribus or eScriptorium.", "activatechocoMufinHelp": "This will read the text of each lines and summarize the characters found.", "chocoMufinModeHelp": "In Generate mode, the Actions won't control your characters but will instead list all characters used. In Control mode, you need to provide a file named table.csv to help ChocoMufin control your data. See the tutorial for more details.", "thisUses": "This uses ", "testCatalog": "Test Catalog's File", "testReport": "Generate reports", "testXML": "Test XML files (structure)", "testChars": "Control the characters you use for transcribing", "githubURLHelp": "This should look like https://github.com/htr-united/cremma-medieval or https://github.com/demo-user/demo-repository.", "githubURL": "Github repository's URL", "generate": "Generate the Github Action's file", "steps": "Steps to follow", "step1": "(1) Get the content using either method:", "download": "Download", "copy": "Copy", "step2": "(2) Add this file in your repository in the folder ", "add": "Add the file on ", "edit": "Edit the file if it exists ", "addBadge": "(3) Add the following text to your README.md file if you want to show your badges", "editReadme": "Edit the README.MD on Github"}, "models": {"title": "Models", "p1": "The HTR-United catalog does not directy list transcription models, but rather the data that were used to create such models. You can explore the repositories linked to the datasets in which you are interested in order to find out if they link to a public model.", "p2": "Several collections of public transcription models exist. You can for example browse the Zenodo community called \"OCR/HTR model repository\". It contains several transcription models freely reusable.", "btn": {"zenodo1": "See \"OCR/HTR model repository\" on Zenodo"}}} \ No newline at end of file +{"nav": {"home": "Home", "form": "Record New Data", "catalog": "Browse the Catalog", "charter": "Data reuse charter", "team": "The Team", "tools": "Tools", "models": "Models", "actions": "Github Automation"}, "footer": {"team": "Who are the people behind HTR-United?", "changelog": "Schema changelog", "about": "About"}, "team": {"title": "Editors", "alix": "I am a PhD student in Digital Humanities, member of the ALMAnaCH team at Inria-Paris and part of the CRIHN at the University of Montreal, enrolled both at the University of Montr\u00e9al and the \u00c9cole Pratique des Hautes \u00c9tudes (Paris). Under the supervision of Laurent Romary, Emmanuel Chateau-Dutier and Michael Sinatra, I work on the appropriation of automatic transcription tools (HTR) by the DH community and by cultural institutions. As a R&D engineer for Inria, I colaborated with numerous projets involving HTR, including LECTAUREP (French national archives), TIME US (ANR) and DAHN.", "thibault": "I am the head of the MA \"Digital Technologies Applied to History\" (Technologies Num\u00e9riques Appliqu\u00e9es \u00e0 l\u2019Histoire) at the \u00c9cole Nationale des Chartes (Paris, France). I am a classicist who served as an engineer both at the Centre for eResearch (Kings College London, UK) and the Humboldt Chair for Digital Humanities (Leipzig, Germany) where I developed the data backbone of the future Perseus 5 (under the CapiTainS.org project). I am a founding member of the Technical Committee for the Distributed Text Services standard ( w3id.org/dts ). The major part of my teaching is dedicated to patrimonial data engineering, namely digital data management, development good practices, standards for communication and programming languages. My research mainly focus on automatically processing ancient languages through deep learning and the distribution of corpora."}, "main": {"desc": {"main": "HTR-United is a catalog of metadata on training datasets (ground truth datasets) available for the creation of transcription or segmentation models. The metadata are provided by the creators of these datasets. 
HTR-United offers a schema to homogenize descriptions of datasets, as well as recommendations on how to organize a data repository, and tools for quality control and continuous documentation. 
HTR-United is an ecosystem relying on a Github organization, transparent and open to all, using minimalistic developments to facilitate its maintenance. 
HTR-United was born from the necessity -for projects- to have access to various types of ground truth to rapidly train models on smaller corpora.", "use": {"p1": "HTR-United is a catalog of datasets and eventually models for (handwritten) text recognition. It takes the form of a YAML file containing metadata essential to identify datasets compatible with your document and to access them. You can download datasets or contact their owner(s), according to the modality they specified.", "p2": "Besides information on how to reach the data, the catalog gathers metadata describing the writings presented in the datasets (temporality, number of hands, features) and the conditions of creation (authority, annotation rules, format).", "p3": "It is also possible to browse through the calalog on this website"}, "provide": "

You can contribute to the HTR-United project by referencing your ground truth dataset in the catalog. No need to load your data onto Github, they can be hosted anywhere you want! You only need to generate the metadata thanks to our form and to add them either in your own repo or in the project's repository, depending on your situation. These metadata will describe your dataset and the conditions of access and reuse.

Your data can originate from any OCR/HTR software, or even from a manual process, and can be shared following various standards (ALTO XML or PAGE XML). To make your dataset useful to other projects, it needs to be composed of at least: images, their transcriptions, and metadata describing among other things the rules set to produce the annotation.

To help you understand which step to follow in order to contribute to the project, check out our scenarios!

", "sc1": "Your data is not yet published. You can then join the HTR-United Github organization and create a new repository dedicated to your data. If your images are hosted somewhere else and can easily be downloaded (e.g. via a IIIF manifest), it is possible to only add the transcription as XML files, along with a file presenting the dataset (README) and a license. You can trigger an update in the catalog's content by adding in your repository an htr-united.yml file containing the metadata generated with our form . A template is offered here: https://github.com/HTR-United/template-htr-united-datarepo . You can take inspiration from the repository template offered here: https://github.com/HTR-United/template-htr-united-datarepo .", "sc2": "Your data are not yet published and you do not wish to publish them within the HTR-United Github organization. No problem! You can publish your data on any platform, for example your own Github space or Zenodo. If your images are hosted somewhere else and can easily be downloaded, your repository can solely contain the transcriptions as XML files, as well as a basic documentation in a README file and a license. Once the repository is ready, you can trigger an update on the catalog by adding a YAML file generated with our form within the catalog folder in HTR-United's main repository.", "sc3": "Your dataset is already published online and freely accessible. Verify that the dataset is associated with an explicit license, that the transcription files follow the accepted formats (ALTO or PAGE), that the image are either published along with the transcription or that they can be easily accessed (via a IIIF manifest for example) and finally that the dataset is sufficiently described (including transcription rules). Then you can generate a structured description with our form and add the YAML file within the catalog folder in HTR-United's main repository. It will trigger an update on the main catalog.", "sc4": "You cannot freely share your data (either the images or the transcriptions) but you still wish to contribute to the HTR-United project. You can create a repository within the HTR-United Github organization only made of a README file dedicated to describing the data. Remember to give any relevant contact information in order to allow future users to request an access to the data. Once the repository is ready, you can generate a structured description with our form and add the YAML file within the catalog folder in HTR-United's main repository. It will trigger an update on the main catalog."}, "title": {"use": "Use data referenced in HTR-United", "provide": "Provide data to HTR-United", "scenarios": "Scenarios", "scenario": "Scenario"}, "btn": {"download": "Download the catalog", "catalog": "Browse the catalog", "cite": "Cite HTR-United", "generate": "Generate a description", "scenarios": "Check out the scenarios", "faq": "Go to FAQ", "use": "Use the data", "provide": "Provide data"}}, "cat": {"title": "Catalog", "nota": "The languages used to introduce the datasets depend on language used by the author(s) of a descripion.", "resultCount": "Number of results", "filters": "Filters", "authors": "Authors", "showGuidelines": "Show Transcription Guidelines", "showCitations": "Show Citation Informations", "descCount": "Statistics about the results", "countUnit": "Unit", "countAmount": "Amount", "countProjects": "Projects with this unit", "countChars": "Characters", "countLine": "Lines", "repository": "Data repository", "link": "Link", "software": "Software", "citationFile": "Citation File (CFF)", "share": "Share", "tweet": "Tweet", "full_record": "Complete record"}, "catalog": {"projectName": "Project", "all": "All projects", "script": "Script", "allLanguage": "All languages", "allScript": "All scripts", "language": "Language", "includeManuscript": "At least half is manuscript", "includePrint": "At least half is printed"}, "tools": {"title": "Tools", "seeDemo": "See demo", "intro": "In order to produce good data and to ensure an easy way to control or quantify the data produced, we offer a certain set of tools with tutorial (upcoming) on how to use them both in a standalone way or in a continuous integration way.", "humg": "HUMGenerator (Htr United Metadata Generator) generates metadata, specifically metrics for your corpora. It's specifically being used to generate the volume key of the catalog schema. It can generate a character count table, to help users choose new kind of ground truth to cover more characters.", "htruc": "HTRUC allows for controlling that the htr-united catalog file is parsable and HTR-United compliant. HTRUC is also meant to offer the tools to parse, augment and compile statistics about catalog file(s). This allows the HTR-United central repository to build a general catalog for everyone's use, see the main catalog. It can also be used with HUMGenerator to update a catalog file with new volumes.", "htrvx": "HTRVX focuses on controlling the quality of the XML. It provides many options in terms of quality control: schema validation (checking that your ALTO or PAGE is okay), empty line or children-less region detection, Segmonto compatibility for segmentation (see Segmonto's Ontology documentation)", "chocomufin": "ChocoMufin focuses on the characters that are used in the ground truth. It can either help you have an overview of the character used, can be used to control which one are used (to avoid having two characters for the same purpose, which can be common with historical documents) or, using a conversion table, it can be used to normalize a whole set of ground-truth."}, "form": {"download": {"dl": "Download", "text": "this file below or copy the content and upload it using this ", "push_link": "link"}, "desc": {"main": "HTR-United is a Github organization without any other form of legal personality. It aims at gathering HTR/OCR models for and transcriptions of all periods and style of writing, mostly but not exclusively in French.
It was born from the mere necessity -for projects- to possess potentiel ground truth to rapidly train models on smaller corpora."}, "steps": {"title": "Steps"}, "step1": {"title": "Fill the form", "desc": "Follow the instructions and examples if necessary. Some items are optional, but you should try to provide as much detail at possible. You can also contact us by opening an issue."}, "step2": {"title": "Click on \"Get formatted metadata\"", "desc": "And copy the output !"}, "step3": {"title": "Add the result to HTR-United's catalog", "desc": "By creating a new file inside our catalog/ folder, following the link provided after you generated the metadata. You can also paste the content in your own htr-united.yml file inside your repository."}, "form": {"head": "Fields followed by a * are the only ones required."}, "title": {"ds": "General information about the dataset", "project": "General information about the project", "data": "General information about the data", "detail": "Detailed information about the data", "generate": "Generate the htr-united.yml file"}, "play": "Play or restart", "field": {"ds_title": "Repository's or dataset's title", "repolink": "Link to repository", "ds_desc": "Short description", "cff": {"link": "Link to a CITATION.cff file", "info": "CITATION.cf files allow for generating quick APA citations or Bibtex ones on github for example. See:"}, "license": "License", "std": "Format Standard", "linepair": "Image-Text line pairs", "project": {"name": "Project's name (if different from the repository/dataset's one)", "link": "Link to project's website"}, "std_info": "This is a non-exhaustive selection of license options.", "software": "Software use to produce the data", "software_placeholder": "You can use the following buttons to populate the field.", "authors": "Authority and role(s)", "member": {"add": "Add a member", "rm": "Remove a member", "name": "Author's first name", "surname": "Author's last name", "transcriber": "Transcription", "aligner": "Alignment", "mainCreator": "Project Manager", "qualityControl": "Quality Control", "digitizer": "Digitization", "support": "Support", "status": "This contributor is an institution", "roles": "Roles"}, "year": {"start": "Source Start-Year", "end": "Source End-Year", "info": "For centuries, please prefer the use of 1200 when a dataset starts in the 13th century and 1299 when it ends in the 13th century. Dates do not need to be precise."}, "languages": {"label": "Language(s)", "helper": "To ease data entry, default values are already selected. Just click on it to deselect the one you don't want."}, "scripts": {"label": "Script", "helper": "To ease data entry, default values are already selected. Just click on it to deselect the one you don't want."}, "scripts-details": {"helper": "Only when necessary, you can add a qualifier to a script. For example: Latf + Kurrent (to designate the German variant to Fraktur)."}, "script": {"type": {"label": "Script type", "select": {"only-manuscript": "Manuscript only", "all": "All", "only-typed": "Typed only", "mainly-manuscript": "Mainly manuscript", "mainly-typed": "Mainly typed", "evenly-mixed": "Evenly typed and manuscript"}}}, "hands": {"label": "Number of hands (or fonts)", "select": {"1perfile": "1 per file", "1perfolder": "1 per folder", "less10": "Less than or equal to 10 (few)", "more10": "More than 10 (many)", "unknown": "Unknown"}}, "prec": {"label": "Precision", "select": {"exact": "Exact value", "estimated": "Estimated value"}}, "guidelines": {"label": "Transcription guidelines", "info": "Guidelines used to transcribe the resources (normalization, resolution of abbreviation, correction of mispelling, etc.)"}, "qual": {"label": "Estimated quantity", "select": {"lines": "Lines", "pages": "Pages", "characters": "Characters", "regions": "Zones", "files": "XML Files"}}, "flags": {"label": "Flags", "automaticallyAligned": {"label": "Automatically aligned", "helper": "This flag is applicable if you used automatically alignment and did not perform a fully manual alignment review"}}, "src": "Sources", "apa": "We prefer APA references, which can look like the following Allport, G. W. (1930\u20131967). Correspondence. Gordon W. Allport Papers (HUG 4118.10), Harvard University Archives, Cambridge, MA, United States., see APA Style, but simpler formats are okay too. The link or the APA reference are sufficient but you can provide both"}, "input": {"reponame": "Repository's title", "repolink": "Link to repository", "cff": "Link to a CITATION.cff file", "projectname": "Project's name", "projectlink": "Link to project's website (if applicable)", "src": "Link to the source or a catalog description", "datebegin": "Example: 1800", "dateend": "Example: 1899", "guidelines": "Transcription guidelines", "quantity": "Example: 200", "apa": "APA Reference for a source"}, "btn": {"get": "Get formatted metadata"}, "finale": {"steps": "Steps to follow", "step1": "(1) Get the content using either method:", "download": "Download", "copy": "Copy", "step2": "(2) Then add it to the HTR-United catalogue via a file c\u0155eation or an issue", "notWorking": "If this doesn't work with the above links, open an issue on the HTR-United repository:", "newFile": "Create the file", "newIssue": "Open an issue"}}, "actions": {"introduction": "Github Actions are a way to run specific code everytime you change your data. The following form will generate a configuration file to use our 4 tools automatically and ensure both complete compatibility with the HTR-United initiative and high quality data. Some options below will focus on controling the data, your cataloging file or simply automatically updating it with the metrics of your choice !", "generalInformations": "General information on your data repository", "htrUnitedFilename": "Filename of your HTR-United metadata file (catalog)", "dataUnixPath": "Path to your XML data (UNIX format)", "branchName": "Main branch name", "activateHTRUC": "Activate", "activateHUMG": "Activate", "updateCatalogFile": "Update the catalog file", "formatGithubUrl": "Address without the github.com domain, only username/repository", "generateBadge": "Generate badges", "gitRelease": "Automatically create a release", "activateHTRVX": "Activate", "activateSegmonto": "Test your compatibility with Segmonto", "activateEmptyLine": "Check for empty lines or childless regions", "activateRaiseEmptyLine": "Raise an error when empty lines or childless regions are found", "activateXSD": "Check XML Schema", "activatechocoMufin": "Activate", "chocoMufinMode": "Mode", "htrUnitedFilenameHelp": "This file should have been generated with the form on this website: it describes your whole repository with metadata, make sure you did that first ! This file is generally named htr-united.yml and should be at the root of your github repository.", "dataUnixPathHelpP1": "This path is the path on your repository. Use * for a filename wildcard, ** for a folder wildcard. You can have a single path, such as ./data/*.xml or multiple, such as ./french/data/*.xml ./english/data/*.xml. If you have a structure such as ./data/a_book/some.xml and ./data/b_book/some.xml, the UNIX path is ./data/**/*.xml", "branchNameHelp": "Generaly main or master.", "dataUnixPathHelpP2": "In the example on the right, if TNAH-2021-Project-Correspondance-Berlioz is the root of your data repository, the path to get all XML would be donnees/**/*.xml", "activateHTRUCHelp": "This will run a test on your htr-united.yml and makes sure it's compliant with the schemas. If the schema evolves, it allows you to ensure your compatibility with it.", "activateHUMGHelp": "This will produces in depth overview of how many characters, zones, lines and pages you have, but also gives you the amount of zone or lines per type if you typed your zones and lines.", "updateCatalogFileHelp": "Using the computed metrics (line, characters, files, zones), update the volume information of the cataloging file automatically.
This automatically pushes new files to your repository. This does not damage your data.", "generateBadgeHelp": "Using this, badges will be generated, such as which you can include in your README file to show how cool you are.
This automatically pushes new files to your repository. This does not damage your data.", "gitReleaseHelp": "Creates a Github release everytime master is changed. Coupled with Zenodo, this will allow you to have long term preservation and DOI (Digital Object Identifier) for your repository !", "activateHTRVXHelp": "This will help you make sure that your XML is valid and follows some other specifications.", "activateSegmontoHelp": "Segmonto is an ontology for typing Zones (sometimes called Regions) and Lines. This ensures you are compatible with it. cf. Publication or Segmonto Guidelines.", "activateEmptyLineHelp": "This will warn you about empty lines or regions without lines, without raising an error: this won't make the test fail !", "activateRaiseEmptyLineHelp": "This is used on top of the former check. This will raise an error if a line has no text or if a region has no lines.", "activateXSDHelp": "This just makes sure you are compatible with the XML schema. This should always be the case if you use a Graphical User Interface such as Transkribus or eScriptorium.", "activatechocoMufinHelp": "This will read the text of each lines and summarize the characters found.", "chocoMufinModeHelp": "In Generate mode, the Actions won't control your characters but will instead list all characters used. In Control mode, you need to provide a file named table.csv to help ChocoMufin control your data. See the tutorial for more details.", "thisUses": "This uses ", "testCatalog": "Test Catalog's File", "testReport": "Generate reports", "testXML": "Test XML files (structure)", "testChars": "Control the characters you use for transcribing", "githubURLHelp": "This should look like https://github.com/htr-united/cremma-medieval or https://github.com/demo-user/demo-repository.", "githubURL": "Github repository's URL", "generate": "Generate the Github Action's file", "steps": "Steps to follow", "step1": "(1) Get the content using either method:", "download": "Download", "copy": "Copy", "step2": "(2) Add this file in your repository in the folder ", "add": "Add the file on ", "edit": "Edit the file if it exists ", "addBadge": "(3) Add the following text to your README.md file if you want to show your badges", "editReadme": "Edit the README.MD on Github"}, "models": {"title": "Models", "p1": "The HTR-United catalog does not directy list transcription models, but rather the data that were used to create such models. You can explore the repositories linked to the datasets in which you are interested in order to find out if they link to a public model.", "p2": "Several collections of public transcription models exist. You can for example browse the Zenodo community called \"OCR/HTR model repository\". It contains several transcription models freely reusable.", "btn": {"zenodo1": "See \"OCR/HTR model repository\" on Zenodo"}}, "changelog": {"title": "Schema changelog", "disclaimer": "

"}} \ No newline at end of file diff --git "a/assets/vanilla-i18n/Fran\303\247ais.json" "b/assets/vanilla-i18n/Fran\303\247ais.json" index 386ce59..ef86c8b 100644 --- "a/assets/vanilla-i18n/Fran\303\247ais.json" +++ "b/assets/vanilla-i18n/Fran\303\247ais.json" @@ -1 +1 @@ -{"nav": {"home": "Accueil", "form": "Enregistrer des donn\u00e9es", "catalog": "Explorer le catalogue", "charter": "Charte de r\u00e9utilisation des donn\u00e9es", "team": "L'\u00c9quipe", "tools": "Les Outils", "models": "Mod\u00e8les", "actions": "Automatisation Github"}, "footer": {"team": "Qui est derri\u00e8re HTR-United ?"}, "team": {"title": "\u00c9ditrices-eurs", "alix": "Je suis doctorante en Humanit\u00e9s num\u00e9riques au sein de l'ALMAnaCH du centre Inria de Paris et au sein du CRIHN \u00e0 l'Universit\u00e9 de Montr\u00e9al, en co-tutelle entre l'Universit\u00e9 de Montr\u00e9al et l'\u00c9cole Pratique des Hautes \u00c9tudes. Sous la supervision de Laurent Romary, Emmanuel Chateau-Dutier et Michael Sinatra, je travaille sur l'appropriation des outils de transcription automatique (HTR) par la communaut\u00e9 des humanit\u00e9s num\u00e9riques et par les institutions patrimoniales. En tant qu'ing\u00e9nieure R&D pour Inria, j'ai collabor\u00e9 avec de nombreux projets impliquant l'HTR, dont LECTAUREP (archives nationales), TIME US (ANR), et DAHN.", "thibault": "Je suis responsable du master \u00ab Technologies num\u00e9riques appliqu\u00e9es \u00e0 l\u2019histoire \u00bb de l\u2019\u00c9cole nationale des chartes (Paris, France). J'ai \u00e9t\u00e9 ing\u00e9nieur au Centre for eResearch (Kings College de Londres, Royaume-Uni) et \u00e0 la chaire Humboldt pour les humanit\u00e9s num\u00e9riques (Leipzig, Allemagne), o\u00f9 j'ai travaill\u00e9 sur les fondations de Perseus 5 et du projet CapiTainS.org. Je suis membre fondateur du Technical Committee du standard Distributed Text Services ( w3id.org/dts ). Mes enseignements portent en majeure partie sur l\u2019ing\u00e9nierie des donn\u00e9es patrimoine, qu\u2019il s\u2019agisse de la gestion num\u00e9rique des donn\u00e9es, des bonnes pratiques de d\u00e9veloppement, de standards de communication ou de langages de programmation. Mes recherches portent principalement sur le traitement automatique des langues anciennes \u00e0 travers l\u2019apprentissage profond et sur la mise \u00e0 disposition de corpora."}, "main": {"desc": {"main": "HTR-United est un catalogue de m\u00e9tadonn\u00e9es sur des jeux de donn\u00e9es d\u2019entra\u00eenement (v\u00e9rit\u00e9 de terrain) disponibles pour la cr\u00e9ation de mod\u00e8les de transcription ou de segmentation. Ces m\u00e9tadonn\u00e9es sont transmises par les cr\u00e9ateur\u00b7rices des jeux de donn\u00e9es. 
HTR-United propose un sch\u00e9ma de description pour homog\u00e9n\u00e9iser les signalements des jeux de donn\u00e9es, ainsi que des recommandations pour organiser le r\u00e9pertoire de donn\u00e9es, et des outils de contr\u00f4le qualit\u00e9 et de documentation continue. 
HTR-United est un \u00e9cosyst\u00e8me prenant la forme d\u2019une organisation Github, transparente et ouverte \u00e0 tous\u00b7tes, reposant sur des d\u00e9veloppements minimalistes afin d\u2019en faciliter la maintenance. 
HTR-United est n\u00e9 du simple besoin -pour des projets- d\u2019avoir acc\u00e8s \u00e0 diverses v\u00e9rit\u00e9s de terrain pour entra\u00eener rapidement des mod\u00e8les de transcription sur des petits corpus.", "use": {"p1": "HTR-United est un catalogue de jeux de donn\u00e9es et \u00e9ventuellement de mod\u00e8les pour la reconnaissance automatique d'\u00e9critures. Il prend la forme d'un fichier YAML comprenant les m\u00e9tadonn\u00e9es essentielles pour rep\u00e9rer les jeux de donn\u00e9es compatibles avec vos documents et y acc\u00e9der. Vous pouvez alors directement t\u00e9l\u00e9charger les jeux de donn\u00e9es ou contacter leur(s) propri\u00e9taire(s), selon les modalit\u00e9s de partage d\u00e9finies.", "p2": "Outre des informations sur le mode d'acc\u00e8s aux donn\u00e9es, le catalogue rassemble des m\u00e9tadonn\u00e9es d\u00e9crivant les \u00e9critures repr\u00e9sent\u00e9es dans un jeu de donn\u00e9es (temporalit\u00e9, nombre de mains, caract\u00e9ristiques) et les conditions de cr\u00e9ation des donn\u00e9es (autorit\u00e9, r\u00e8gles d'annotation, format).", "p3": "Il est aussi possible d'explorer le contenu du catalogue depuis ce site."}, "provide": "

Vous pouvez contribuer au projet HTR-United en r\u00e9f\u00e9ren\u00e7ant votre jeu de donn\u00e9es de v\u00e9rit\u00e9 de terrain dans le catalogue. Pas besoin de charger vos donn\u00e9es sur Github, elles peuvent \u00eatre h\u00e9berg\u00e9es n'importe o\u00f9 ! Il suffit de g\u00e9n\u00e9rer les m\u00e9tadonn\u00e9es \u00e0 l'aide de notre formulaire puis de les ajouter dans votre r\u00e9pertoire ou bien dans le r\u00e9pertoire du projet htr-united, en fonction de votre situation. Ces m\u00e9tadonn\u00e9es permettent de d\u00e9crire vos donn\u00e9es et les conditions d'acc\u00e8s et de r\u00e9utilisation.

Vos donn\u00e9es peuvent avoir \u00e9t\u00e9 g\u00e9n\u00e9r\u00e9es avec n'importe quel logiciel d'HTR ou \u00e0 la main et peuvent \u00eatre propos\u00e9es dans plusieurs formats standards (XML ALTO ou XML PAGE). Afin qu'ils puissent \u00eatre utiles \u00e0 d'autres projets, les jeux de donn\u00e9es doivent rassembler \u00e0 minima : des transcriptions associ\u00e9es \u00e0 des images, un lien vers les images, et des m\u00e9tadonn\u00e9es d\u00e9crivant notamment les r\u00e8gles d'annotation suivies.

Pour vous aider \u00e0 comprendre quelles \u00e9tapes suivre pour ajouter vos m\u00e9tadonn\u00e9es au catalogue HTR-United, consultez nos sc\u00e9narios !

", "sc1": "Vos donn\u00e9es ne sont pas encore publi\u00e9s. Vous pouvez alors rejoindre l'organisation Github HTR-United et cr\u00e9er un nouveau r\u00e9pertoire de travail d\u00e9di\u00e9 \u00e0 vos donn\u00e9es. Celles-ci peuvent \u00eatre constitu\u00e9es des fichiers XML seuls si les images sont ais\u00e9ment accessibles par un autre moyen (via un manifeste IIIF par exemple). Ajoutez \u00e9galement un fichier de pr\u00e9sentation du jeu de donn\u00e9es (README) et une licence. Vous pouvez d\u00e9clencher la modification du contenu du catalogue en ajoutant \u00e0 votre r\u00e9pertoire un fichier htr-united.yml contenant les m\u00e9tadonn\u00e9es g\u00e9n\u00e9r\u00e9es \u00e0 l'aide de notre formulaire . Un mod\u00e8le de r\u00e9pertoire vous est propos\u00e9 ici : https://github.com/HTR-United/template-htr-united-datarepo .", "sc2": "Vos donn\u00e9es ne sont pas encore publi\u00e9es et vous ne souhaitez pas les publier dans le cadre de l'organisation Github HTR-United. Aucun probl\u00e8me ! Il vous suffit de les publier sur la plateforme de votre souhait, par exemple Zenodo. Le d\u00e9p\u00f4t peut \u00eatre constitu\u00e9 des fichiers XML seuls si les images sont ais\u00e9ment accessibles par un autre moyen (par exemple via un manifeste IIIF). Pensez \u00e0 associer \u00e0 vos donn\u00e9es une licence et une documentation sous la forme d'un README. Une fois le r\u00e9pertoire en place, pour d\u00e9clencher la modification du contenu du catalogue, ajoutez un fichier YAML g\u00e9n\u00e9r\u00e9 \u00e0 l'aide de notre formulaire dans le dossier catalog du r\u00e9pertoire HTR-United. Vous pouvez vous inspirer du mod\u00e8le de r\u00e9pertoire propos\u00e9 ici : https://github.com/HTR-United/template-htr-united-datarepo .", "sc3": "Vos donn\u00e9es sont d\u00e9j\u00e0 en ligne et librement accessibles. V\u00e9rifiez que le jeu de donn\u00e9es est bien associ\u00e9 \u00e0 une licence explicite, que le format des transcription correspond \u00e0 l'un de ceux attendus (ALTO ou PAGE), que les images sont soit dans le jeu de donn\u00e9es, soit accessile ais\u00e9ment (par exemple par le biais d'un manifeste IIIF) et enfin que le jeu de donn\u00e9es est suffisamment d\u00e9crit (y compris concernant les normes de transcriptions adopt\u00e9es). Il vous suffit ensuite de g\u00e9n\u00e9rer une description structur\u00e9e du jeu \u00e0 l'aide de notre formulaire puis d'ajouter le fichier YAML obtenu dans le dossier catalog du r\u00e9pertoire HTR-United. Cela d\u00e9clenchera la mise \u00e0 jour du contenu du catalogue.", "sc4": "Vous ne pouvez pas librement partager vos donn\u00e9es (images ou transcriptions) mais vous souhaitez tout de m\u00eame contribuer \u00e0 HTR-United. Vous pouvez cr\u00e9er un r\u00e9pertoire au sein de l'organisation HTR-United uniquement d\u00e9di\u00e9 \u00e0 la documentation de vos donn\u00e9es gr\u00e2ce \u00e0 un fichier README. Indiquez alors comment joindre le(s) propri\u00e9taire(s) des donn\u00e9es afin d'en demander l'acc\u00e8s. Une fois ce r\u00e9pertoire en place, vous pouvez g\u00e9n\u00e9rer une description structur\u00e9e \u00e0 l'aide de notre formulaire puis d'ajouter le fichier YAML obtenu dans le dossier catalog du r\u00e9pertoire HTR-United. Cela d\u00e9clenchera la mise \u00e0 jour du contenu du catalogue."}, "title": {"use": "Utiliser les donn\u00e9es d'HTR-United", "provide": "Proposer mes donn\u00e9es avec HTR-United", "scenarios": "Sc\u00e9narios", "scenario": "Sc\u00e9nario"}, "btn": {"download": "T\u00e9l\u00e9charger le catalogue", "catalog": "Explorer le catalogue", "cite": "Citer HTR-United", "generate": "G\u00e9n\u00e9rer une description", "scenarios": "D\u00e9couvrir les sc\u00e9narios", "faq": "Aller \u00e0 la FAQ", "use": "Utiliser les donn\u00e9es", "provide": "Proposer des donn\u00e9es"}}, "cat": {"title": "Catalogue", "nota": "La langue utilis\u00e9e pour la description des jeux de donn\u00e9es correspond \u00e0 celle employ\u00e9e lors du d\u00e9p\u00f4t d'un signalement dans HTR-United.", "resultCount": "Nombre de r\u00e9sultats", "filters": "Filtres", "authors": "Auteur.ice.s", "showGuidelines": "Afficher les normes de transcription", "showCitations": "Afficher les informations de citation", "descCount": "Description statistique des r\u00e9sultats", "countUnit": "Unit\u00e9", "countAmount": "Total", "countProjects": "Projets avec cette unit\u00e9", "countChars": "Caract\u00e8res", "countLine": "Lignes", "repository": "D\u00e9p\u00f4t de donn\u00e9es", "link": "Lien", "software": "Logiciel", "citationFile": "Fichier Citation (CFF)", "share": "Partager", "tweet": "Tweeter", "full_record": "Notice compl\u00e8te"}, "catalog": {"projectName": "Projet", "all": "Tous les projets", "script": "Syst\u00e8me d'\u00e9criture", "allLanguage": "Toutes les langues", "allScript": "Tous les syst\u00e8mes d'\u00e9criture", "language": "Langue", "includeManuscript": "Au moins la moiti\u00e9 de manuscrit", "includePrint": "Au moins la moiti\u00e9 d'imprim\u00e9"}, "tools": {"title": "Outils", "seeDemo": "Voir une d\u00e9monstration", "intro": "Afin de produire de bonnes donn\u00e9es et de garantir un moyen simple de contr\u00f4ler ou de quantifier les donn\u00e9es produites, nous proposons un certain ensemble d'outils avec tutoriel (\u00e0 venir) sur la mani\u00e8re de les utiliser de mani\u00e8re autonome ou de mani\u00e8re continue.", "humg": "HumGenerator (Htr United Metadata Generator) g\u00e9n\u00e8re des m\u00e9tadonn\u00e9es, en particulier des m\u00e9triques pour vos corpus. Il est sp\u00e9cifiquement utilis\u00e9 pour g\u00e9n\u00e9rer la touche volume du sch\u00e9ma de catalogue. Il peut g\u00e9n\u00e9rer une table de comptage de caract\u00e8res afin d'aider les utilisateurs \u00e0 choisir un nouveau type de v\u00e9rit\u00e9 au sol pour couvrir plus de caract\u00e8res.", "htruc": "HTRUC permet de contr\u00f4ler que le fichier de catalogue HTR-United est parsable et conforme. HTRUC est \u00e9galement destin\u00e9 \u00e0 offrir les outils \u00e0 analyser, augmenter et compiler des statistiques sur le ou les fichiers de catalogue. Cela permet au r\u00e9f\u00e9rentiel HTR-United Central de construire un catalogue g\u00e9n\u00e9ral pour tout le monde, voir Le catalogue principal . Il peut \u00e9galement \u00eatre utilis\u00e9 avec HumGenerator pour mettre \u00e0 jour un fichier de catalogue avec de nouveaux volumes.\"\"", "htrvx": "HTRVX se concentre sur le contr\u00f4le de la qualit\u00e9 du XML. Il fournit de nombreuses options en termes de contr\u00f4le de la qualit\u00e9: la validation de sch\u00e9ma (v\u00e9rifiant que votre alto ou votre page est correcte), la d\u00e9tection de la ligne vide ou la r\u00e9gulation sans enfants, la compatibilit\u00e9 Segmonto pour la segmentation (voir Documentation ontology de Segmonto )", "chocomufin": "Chocomufin se concentre sur les personnages utilis\u00e9s dans la v\u00e9rit\u00e9 au sol. Il peut vous aider \u00e0 avoir une vue d'ensemble du personnage utilis\u00e9, peut \u00eatre utilis\u00e9 pour contr\u00f4ler lequel on utilise celui-ci (pour \u00e9viter d'avoir deux caract\u00e8res dans le m\u00eame but, qui peuvent \u00eatre courants avec des documents historiques) ou, en utilisant une table de conversion, il peut \u00eatre utilis\u00e9 pour normaliser un ensemble complet de la v\u00e9rit\u00e9 au sol."}, "form": {"download": {"dl": "T\u00e9l\u00e9chargez", "text": " e fichier ci-dessous et copiez son contenu au bout de ce", "push_link": "lien"}, "desc": {"main": "HTR-United est une organisation Github sans autre forme de personnalit\u00e9 juridique visant \u00e0 mettre en commun des jeux de donn\u00e9es et des mod\u00e8les pour l'HTR/OCR de textes de toutes p\u00e9riodes et de tout style, principalement en fran\u00e7ais mais de mani\u00e8re non restricive. 
Elle est n\u00e9e du simple besoin - pour des projets - d'avoir de potentiels v\u00e9rit\u00e9s de terrain pour entra\u00eener des mod\u00e8les rapidement sur des corpus plus petits."}, "steps": {"title": "\u00c9tapes"}, "step1": {"title": "Remplir le formulaire", "desc": "Suivre les instructions et les exemples si n\u00e9cessaire. Certaines rubriques sont optionnelles mais vous devriez essayer de donner autant de d\u00e9tails que possible. Vous pouvez aussi nous contacter en ouvrant une issue."}, "step2": {"title": "Cliquer sur \"Obtenir les m\u00e9tadonn\u00e9es format\u00e9es", "desc": "Et copier le r\u00e9sultat !"}, "step3": {"title": "Ajouter le r\u00e9sultat au catalogue d'HTR-United", "desc": "En cr\u00e9ant un nouveau fichier \u00e0 l'int\u00e9rieur de notre dossier catalog/, en suivant le lien fourni apr\u00e8s avoir g\u00e9n\u00e9r\u00e9 les m\u00e9tadonn\u00e9es. Vous pouvez aussi copier les m\u00e9tadonn\u00e9es \u00e0 l'int\u00e9rieur de votre propre fichier htr-united.yml au sein de votre r\u00e9pertoire."}, "form": {"head": "Les champs dont le nom est suivi d'un * sont obligatoires."}, "title": {"ds": "Informations g\u00e9n\u00e9rales sur le set de donn\u00e9es", "project": "Informations g\u00e9n\u00e9rales sur le projet", "data": "Informations g\u00e9n\u00e9rales sur les donn\u00e9es", "detail": "Informations d\u00e9taill\u00e9es sur les donn\u00e9es", "generate": "G\u00e9n\u00e9rer le fichier htr-united.yml"}, "play": "Lancer la d\u00e9mo ou la red\u00e9marrer", "field": {"ds_title": "Nom du d\u00e9p\u00f4t / dataset (titre)", "repolink": "Lien vers le d\u00e9p\u00f4t", "ds_desc": "Courte description", "cff": {"link": "Lien vers un fichier CITATION.cff", "info": "Les fichiers CITATION.cff permettent de fournir un mode de citation assez simple sur github par exemple. Lien:"}, "license": "Licence", "std": "Format des donn\u00e9es", "linepair": "Paires de ligne Image-Texte", "project": {"name": "Nom du projet (si diff\u00e9rent du nom du d\u00e9p\u00f4t)", "link": "Lien vers le site du projet"}, "std_info": "Les licences sont ici propos\u00e9es \u00e0 titre indicatif.", "software": "Logiciel(s) utilis\u00e9(s) pour produire les donn\u00e9es", "software_placeholder": "Vous pouvez utiliser les boutons pour remplir plus rapidement le champ.", "authors": "Contributeur-rice-s et r\u00f4le(s)", "member": {"add": "Ajouter une contribution", "rm": "Supprimer cette contribution", "name": "Pr\u00e9nom de la personne", "surname": "Nom de la personne", "transcriber": "Transcription", "aligner": "Alignement", "mainCreator": "Responsable du projet", "qualityControl": "Contr\u00f4le Qualit\u00e9", "digitizer": "Num\u00e9risation", "support": "Assistance", "status": "Cette contribution vient d'une institution", "roles": "R\u00f4les"}, "year": {"start": "Ann\u00e9e de d\u00e9but des sources", "end": "Ann\u00e9e de fin des sources", "info": "Pr\u00e9f\u00e9rez, pour des donn\u00e9es au si\u00e8cle pr\u00e8s, 1200 pour un d\u00e9but au 13e si\u00e8cle et 1299 pour une fin au 13e si\u00e8cle. Les dates n'ont pas besoin d'\u00eatre pr\u00e9cises, cela reste une indication"}, "languages": {"label": "Langue(s)", "helper": "Pour faciliter l'entr\u00e9e de donn\u00e9es, des valeurs par d\u00e9faut sont s\u00e9lectionn\u00e9es. Cliquez dessus pour les d\u00e9s\u00e9lectionner."}, "scripts": {"label": "Syst\u00e8me d'\u00e9criture", "helper": "Pour faciliter l'entr\u00e9e de donn\u00e9es, des valeurs par d\u00e9faut sont s\u00e9lectionn\u00e9es. Cliquez dessus pour les d\u00e9s\u00e9lectionner."}, "scripts-details": {"helper": "Lorsque c'est n\u00e9cessaire seulement, vous pouvez sp\u00e9cifier une sous-cat\u00e9gorie pour le script d\u00e9crit. Par exemple : Latf + Kurrent (pour qualifier la variante allemande de la Fraktur)."}, "script": {"type": {"label": "Type d'\u00e9criture", "select": {"only-manuscript": "Manuscrit uniquement", "all": "Tous", "only-typed": "Imprim\u00e9/dactylographi\u00e9 uniquement", "mainly-manuscript": "Principalement manuscrit", "mainly-typed": "Principalement imprim\u00e9/dactylographi\u00e9", "evenly-mixed": "Egale r\u00e9partition manuscrit/dactylographi\u00e9 et imprim\u00e9"}}}, "hands": {"label": "Nombre de mains (ou de fontes)", "select": {"1perfile": "1 par fichier", "1perfolder": "1 par dossier", "less10": "Inf\u00e9rieur ou \u00e9gal \u00e0 10 (peu)", "more10": "Sup\u00e9rieur \u00e0 10 (beaucoup)", "unknown": "Inconnu"}}, "prec": {"label": "Pr\u00e9cision", "select": {"exact": "Valeur exacte", "estimated": "Estimation"}}, "guidelines": {"label": "Normes de transcription", "info": "Normes de transcriptions utilis\u00e9es (format libre). Peut concerner la r\u00e9solution des abr\u00e9viations, corrections de fautes d'orthographe, l'usage de caract\u00e8res sp\u00e9ciaux, la normalisation, etc."}, "qual": {"label": "Description sommaire des quantit\u00e9s", "select": {"lines": "Lignes", "pages": "Pages", "characters": "Caract\u00e8res", "regions": "Zones", "files": "Fichiers XML"}}, "flags": {"label": "Marqueurs sp\u00e9cifique", "automaticallyAligned": {"label": "Align\u00e9 automatiquement", "helper": "Ce marqueur s'applique si vous avez utilis\u00e9 un alignement automatique mais n'avez pas effectu\u00e9 de v\u00e9rification manuelle compl\u00e8te."}}, "src": "D\u00e9tails des sources transcrites", "apa": "Le format APA est pr\u00e9f\u00e9r\u00e9 pour les citations, ce qui peut donner des r\u00e9f\u00e9rences longues comme Allport, G. W. (1930\u20131967). Correspondence. Gordon W. Allport Papers (HUG 4118.10), Harvard University Archives, Cambridge, MA, United States., cf. APA Style. Des formats plus courts sont autoris\u00e9. Le lien ou la r\u00e9f\u00e9rence APA peuvent suffire."}, "input": {"reponame": "Nom du d\u00e9p\u00f4t", "repolink": "Lien vers le d\u00e9p\u00f4t", "cff": "Lien vers un fichier CITATION.cff", "projectname": "Nom du projet", "projectlink": "Lien vers le site du projet (s'il existe)", "src": "Lien vers le catalogue ou la ressource", "datebegin": "Exemple: 1800", "dateend": "Exemple: 1899", "guidelines": "Normes de transcription", "quantity": "Exemple: 200", "apa": "R\u00e9f\u00e9rence en mode APA"}, "btn": {"get": "Obtenir les m\u00e9tadonn\u00e9es format\u00e9es"}, "finale": {"steps": "\u00c9tapes de mise en place", "step1": "(1) R\u00e9cup\u00e9rez le contenu, au choix:", "download": "T\u00e9l\u00e9chargez", "copy": "Copiez", "step2": "(2) Puis ajoutez le au catalogue HTR-United via une c\u0155eation de fichier ou de ticket", "notWorking": "Si cela ne marche pas avec les liens ci-dessus, ouvrez une issue sur le d\u00e9p\u00f4t HTR-United:", "newFile": "Cr\u00e9er le fichier", "newIssue": "Ouvrir un ticket"}}, "actions": {"introduction": "Les actions Github permettent d'ex\u00e9cuter des scripts \u00e0 chaque fois que vous modifiez vos donn\u00e9es. Le formulaire suivant va g\u00e9n\u00e9rer un fichier de configuration pour utiliser nos 4 outils automatiquement et assurer \u00e0 la fois une compatibilit\u00e9 compl\u00e8te avec l'initiative HTR-United et des donn\u00e9es de haute qualit\u00e9. Certaines options ci-dessous se concentreront sur le contr\u00f4le des donn\u00e9es, votre fichier de catalogage ou simplement la mise \u00e0 jour automatique avec les m\u00e9triques de votre choix !", "generalInformations": "Informations g\u00e9n\u00e9rales sur votre d\u00e9p\u00f4t de donn\u00e9es", "htrUnitedFilename": "Nom de votre fichier HTR-United de m\u00e9tadonn\u00e9es (catalogue)", "dataUnixPath": "Chemin des donn\u00e9es (Format UNIX)", "branchName": "Nom de la branche principale", "activateHTRUC": "Activer", "activateHUMG": "Activer", "updateCatalogFile": "Mettre \u00e0 jour le fichier catalogue", "formatGithubUrl": "Adresse sans la partie github.com, uniquement nomDutilisateur/d\u00e9p\u00f4t", "generateBadge": "G\u00e9n\u00e9rer des badges", "gitRelease": "Produire des versions automatiquement", "activateHTRVX": "Activer", "activateSegmonto": "Tester votre compatibilit\u00e9 avec Segmonto", "activateEmptyLine": "V\u00e9rifier qu'il n'existe pas de lignes ou de r\u00e9gions vides", "activateRaiseEmptyLine": "\u00c9mettre une erreur s'il existe des lignes ou des r\u00e9gions vides", "activateXSD": "V\u00e9rifier votre sch\u00e9ma XML", "activatechocoMufin": "Activer", "chocoMufinMode": "Mode", "htrUnitedFilenameHelp": "Ce fichier aurait d\u00fb \u00eatre g\u00e9n\u00e9r\u00e9 avec le formulaire sur ce site Web: il d\u00e9crit tout votre d\u00e9p\u00f4t avec des m\u00e9tadonn\u00e9es, assurez-vous de le faire en premier! Ce fichier est g\u00e9n\u00e9ralement nomm\u00e9 htr-united.yml et doit \u00eatre \u00e0 la racine de votre d\u00e9p\u00f4t GitHub.", "dataUnixPathHelpP1": "Ce chemin est le chemin de votre r\u00e9f\u00e9rentiel. Utilisez * comme joker pour un nom de fichier, ** pour un dossier. Vous pouvez avoir un seul chemin, tel que ./data/*.xml ou plusieurs, comme ./french/data/*.xml ./english/data/*.xml. Si vous avez une structure telle que ./data/a_book/certains.xml et ./data/b_book/some.xml, le chemin UNIX est ./data/**/*.xmlmain ou master.", "dataUnixPathHelpP2": "Dans l'exemple de droite, si TNAH-2021-Project-Correspondance-Berlioz est la racine de votre r\u00e9f\u00e9rentiel de donn\u00e9es, le chemin d'acc\u00e8s pour l\u2019ensemble des fichiers XML est donnees/**/*. xml.", "activateHTRUCHelp": "Cela effectuera un test sur votre htr-united.yml et garantit qu'il est conforme aux sch\u00e9mas. Si le sch\u00e9ma \u00e9volue, cela vous permet d'assurer votre compatibilit\u00e9 avec lui.", "activateHUMGHelp": "Cela produira une vue d'ensemble de la profondeur du nombre de caract\u00e8res, de zones, de lignes et de pages que vous avez, mais vous donne \u00e9galement la quantit\u00e9 de zone ou de lignes par type si vous avez saisi vos zones et vos lignes.", "updateCatalogFileHelp": "Met \u00e0 jour automatiquement les informations volume du fichier de catalogage avec de nouvelles mesures (ligne, caract\u00e8res, fichiers, zones).
Cela cr\u00e9e automatiquement de nouveaux fichiers dans votre d\u00e9p\u00f4t via un push git. Cela n'endommage pas vos donn\u00e9es.", "generateBadgeHelp": "En utilisant cette option, des badges seront g\u00e9n\u00e9r\u00e9s, tels que que vous pouvez inclure dans votre fichier README afin d\u2019afficher des statistiques et parce que les badges, c\u2019est cool.
Cela cr\u00e9e automatiquement de nouveaux fichiers dans votre d\u00e9p\u00f4t via un push git. Cela n'endommage pas vos donn\u00e9es.", "gitReleaseHelp": "Cr\u00e9e une release (version) Github \u00e0 chaque fois que la branche principale est modifi\u00e9e. Coupl\u00e9 avec Zenodo, cela vous permet d'avoir une conservation \u00e0 long terme et un DOI (identifiant d'objet num\u00e9rique ) pour chacune des \u00e9volutions de votre d\u00e9p\u00f4t !", "activateHTRVXHelp": "Cela vous aidera \u00e0 vous assurer que votre XML est valide et suit quelques autres sp\u00e9cifications.", "activateSegmontoHelp": "Segmonto est une ontologie pour le typage des zones (parfois appel\u00e9es r\u00e9gions) et des lignes. Cela vous assure que vous \u00eates compatible avec cela. cf. la publication ou le site Segmonto .", "activateEmptyLineHelp": "Cela cr\u00e9e des avertissements si des lignes ne contiennent aucun caract\u00e8re ou si des r\u00e9gions sont vides/ Cela ne provoque pas d\u2019erreur!", "activateRaiseEmptyLineHelp": "En compl\u00e9ment de l\u2019option ci-dessus, g\u00e9n\u00e8re une erreur en cas de ligne ou de r\u00e9gion vide.", "activateXSDHelp": "Cela garantit simplement que vous \u00eates compatible avec le sch\u00e9ma XML. Cela devrait toujours \u00eatre le cas si vous utilisez une interface utilisateur telle que Transkribus ou eScriptorium.", "activatechocoMufinHelp": "Apr\u00e8s avoir lu chaque ligne, \u00e9tudie les caract\u00e8res utilis\u00e9s.", "chocoMufinModeHelp": "Avec le mode G\u00e9n\u00e9ration, les actions ne contr\u00f4lent pas vos caract\u00e8res mais listent tous les caract\u00e8res utilis\u00e9s.
(Utilisateurs avanc\u00e9s) En mode Contr\u00f4le, vous devez fournir un fichier nomm\u00e9 table.csv pour aider Chocomufin \u00e0 contr\u00f4ler vos donn\u00e9es. Voir le tutoriel pour plus de d\u00e9tails.", "thisUses": "Utilise", "testCatalog": "Test du fichier de catalogage", "testReport": "G\u00e9n\u00e9ration de rapports", "testXML": "Test des fichiers XML (Structure)", "testChars": "Contr\u00f4le des caract\u00e8res", "githubURLHelp": "La r\u00e9ponse doit ressembler \u00e0 https://github.com/htr-united/cremma-medieval ou https://github.com/demo-user/demo-repository.", "githubURL": "URL Github du d\u00e9p\u00f4t", "generate": "G\u00e9n\u00e9rer le fichier Github action", "steps": "\u00c9tapes de mise en place", "step1": "(1) R\u00e9cup\u00e9rez le contenu, au choix:", "download": "T\u00e9l\u00e9chargez", "copy": "Copiez", "step2": "(2) Ajoutez le \u00e0 votre d\u00e9p\u00f4t en l'ajoutant dans le dossier", "add": "Ajouter la configuration sur", "edit": "\u00c9diter la configuration si elle existe d\u00e9j\u00e0 sur", "addBadge": "(3) Ajoutez le texte suivant \u00e0 votre fichier README si vous voulez afficher les badges", "editReadme": "\u00c9ditez le Readme.md sur Github"}, "models": {"title": "Mod\u00e8les", "p1": "Le catalogue d'HTR-United ne r\u00e9f\u00e9rence pas directement de mod\u00e8les de transcription, mais plut\u00f4t les donn\u00e9es ayant permis d'en produire. Vous pouvez consulter les r\u00e9pertoires des jeux de donn\u00e9es qui vous int\u00e9ressent pour savoir s'ils renvoient vers un mod\u00e8le public.", "p2": "Il existe des collections de mod\u00e8les publiques. Vous pouvez par exemple consulter le groupe nomm\u00e9 \"OCR/HTR model repository\" sur Zenodo qui contient de nombreux mod\u00e8les de transcription librement r\u00e9utilisables.", "btn": {"zenodo1": "Voir \"OCR/HTR model repository\" sur Zenodo"}}} \ No newline at end of file +{"nav": {"home": "Accueil", "form": "Enregistrer des donn\u00e9es", "catalog": "Explorer le catalogue", "charter": "Charte de r\u00e9utilisation des donn\u00e9es", "team": "L'\u00c9quipe", "tools": "Les Outils", "models": "Mod\u00e8les", "actions": "Automatisation Github"}, "footer": {"team": "Qui est derri\u00e8re HTR-United ?", "changelog": "Changelog du sch\u00e9ma", "about": "\u00c0 propos"}, "team": {"title": "\u00c9ditrices-eurs", "alix": "Je suis doctorante en Humanit\u00e9s num\u00e9riques au sein de l'ALMAnaCH du centre Inria de Paris et au sein du CRIHN \u00e0 l'Universit\u00e9 de Montr\u00e9al, en co-tutelle entre l'Universit\u00e9 de Montr\u00e9al et l'\u00c9cole Pratique des Hautes \u00c9tudes. Sous la supervision de Laurent Romary, Emmanuel Chateau-Dutier et Michael Sinatra, je travaille sur l'appropriation des outils de transcription automatique (HTR) par la communaut\u00e9 des humanit\u00e9s num\u00e9riques et par les institutions patrimoniales. En tant qu'ing\u00e9nieure R&D pour Inria, j'ai collabor\u00e9 avec de nombreux projets impliquant l'HTR, dont LECTAUREP (archives nationales), TIME US (ANR), et DAHN.", "thibault": "Je suis responsable du master \u00ab Technologies num\u00e9riques appliqu\u00e9es \u00e0 l\u2019histoire \u00bb de l\u2019\u00c9cole nationale des chartes (Paris, France). J'ai \u00e9t\u00e9 ing\u00e9nieur au Centre for eResearch (Kings College de Londres, Royaume-Uni) et \u00e0 la chaire Humboldt pour les humanit\u00e9s num\u00e9riques (Leipzig, Allemagne), o\u00f9 j'ai travaill\u00e9 sur les fondations de Perseus 5 et du projet CapiTainS.org. Je suis membre fondateur du Technical Committee du standard Distributed Text Services ( w3id.org/dts ). Mes enseignements portent en majeure partie sur l\u2019ing\u00e9nierie des donn\u00e9es patrimoine, qu\u2019il s\u2019agisse de la gestion num\u00e9rique des donn\u00e9es, des bonnes pratiques de d\u00e9veloppement, de standards de communication ou de langages de programmation. Mes recherches portent principalement sur le traitement automatique des langues anciennes \u00e0 travers l\u2019apprentissage profond et sur la mise \u00e0 disposition de corpora."}, "main": {"desc": {"main": "HTR-United est un catalogue de m\u00e9tadonn\u00e9es sur des jeux de donn\u00e9es d\u2019entra\u00eenement (v\u00e9rit\u00e9 de terrain) disponibles pour la cr\u00e9ation de mod\u00e8les de transcription ou de segmentation. Ces m\u00e9tadonn\u00e9es sont transmises par les cr\u00e9ateur\u00b7rices des jeux de donn\u00e9es. 
HTR-United propose un sch\u00e9ma de description pour homog\u00e9n\u00e9iser les signalements des jeux de donn\u00e9es, ainsi que des recommandations pour organiser le r\u00e9pertoire de donn\u00e9es, et des outils de contr\u00f4le qualit\u00e9 et de documentation continue. 
HTR-United est un \u00e9cosyst\u00e8me prenant la forme d\u2019une organisation Github, transparente et ouverte \u00e0 tous\u00b7tes, reposant sur des d\u00e9veloppements minimalistes afin d\u2019en faciliter la maintenance. 
HTR-United est n\u00e9 du simple besoin -pour des projets- d\u2019avoir acc\u00e8s \u00e0 diverses v\u00e9rit\u00e9s de terrain pour entra\u00eener rapidement des mod\u00e8les de transcription sur des petits corpus.", "use": {"p1": "HTR-United est un catalogue de jeux de donn\u00e9es et \u00e9ventuellement de mod\u00e8les pour la reconnaissance automatique d'\u00e9critures. Il prend la forme d'un fichier YAML comprenant les m\u00e9tadonn\u00e9es essentielles pour rep\u00e9rer les jeux de donn\u00e9es compatibles avec vos documents et y acc\u00e9der. Vous pouvez alors directement t\u00e9l\u00e9charger les jeux de donn\u00e9es ou contacter leur(s) propri\u00e9taire(s), selon les modalit\u00e9s de partage d\u00e9finies.", "p2": "Outre des informations sur le mode d'acc\u00e8s aux donn\u00e9es, le catalogue rassemble des m\u00e9tadonn\u00e9es d\u00e9crivant les \u00e9critures repr\u00e9sent\u00e9es dans un jeu de donn\u00e9es (temporalit\u00e9, nombre de mains, caract\u00e9ristiques) et les conditions de cr\u00e9ation des donn\u00e9es (autorit\u00e9, r\u00e8gles d'annotation, format).", "p3": "Il est aussi possible d'explorer le contenu du catalogue depuis ce site."}, "provide": "

Vous pouvez contribuer au projet HTR-United en r\u00e9f\u00e9ren\u00e7ant votre jeu de donn\u00e9es de v\u00e9rit\u00e9 de terrain dans le catalogue. Pas besoin de charger vos donn\u00e9es sur Github, elles peuvent \u00eatre h\u00e9berg\u00e9es n'importe o\u00f9 ! Il suffit de g\u00e9n\u00e9rer les m\u00e9tadonn\u00e9es \u00e0 l'aide de notre formulaire puis de les ajouter dans votre r\u00e9pertoire ou bien dans le r\u00e9pertoire du projet htr-united, en fonction de votre situation. Ces m\u00e9tadonn\u00e9es permettent de d\u00e9crire vos donn\u00e9es et les conditions d'acc\u00e8s et de r\u00e9utilisation.

Vos donn\u00e9es peuvent avoir \u00e9t\u00e9 g\u00e9n\u00e9r\u00e9es avec n'importe quel logiciel d'HTR ou \u00e0 la main et peuvent \u00eatre propos\u00e9es dans plusieurs formats standards (XML ALTO ou XML PAGE). Afin qu'ils puissent \u00eatre utiles \u00e0 d'autres projets, les jeux de donn\u00e9es doivent rassembler \u00e0 minima : des transcriptions associ\u00e9es \u00e0 des images, un lien vers les images, et des m\u00e9tadonn\u00e9es d\u00e9crivant notamment les r\u00e8gles d'annotation suivies.

Pour vous aider \u00e0 comprendre quelles \u00e9tapes suivre pour ajouter vos m\u00e9tadonn\u00e9es au catalogue HTR-United, consultez nos sc\u00e9narios !

", "sc1": "Vos donn\u00e9es ne sont pas encore publi\u00e9s. Vous pouvez alors rejoindre l'organisation Github HTR-United et cr\u00e9er un nouveau r\u00e9pertoire de travail d\u00e9di\u00e9 \u00e0 vos donn\u00e9es. Celles-ci peuvent \u00eatre constitu\u00e9es des fichiers XML seuls si les images sont ais\u00e9ment accessibles par un autre moyen (via un manifeste IIIF par exemple). Ajoutez \u00e9galement un fichier de pr\u00e9sentation du jeu de donn\u00e9es (README) et une licence. Vous pouvez d\u00e9clencher la modification du contenu du catalogue en ajoutant \u00e0 votre r\u00e9pertoire un fichier htr-united.yml contenant les m\u00e9tadonn\u00e9es g\u00e9n\u00e9r\u00e9es \u00e0 l'aide de notre formulaire . Un mod\u00e8le de r\u00e9pertoire vous est propos\u00e9 ici : https://github.com/HTR-United/template-htr-united-datarepo .", "sc2": "Vos donn\u00e9es ne sont pas encore publi\u00e9es et vous ne souhaitez pas les publier dans le cadre de l'organisation Github HTR-United. Aucun probl\u00e8me ! Il vous suffit de les publier sur la plateforme de votre souhait, par exemple Zenodo. Le d\u00e9p\u00f4t peut \u00eatre constitu\u00e9 des fichiers XML seuls si les images sont ais\u00e9ment accessibles par un autre moyen (par exemple via un manifeste IIIF). Pensez \u00e0 associer \u00e0 vos donn\u00e9es une licence et une documentation sous la forme d'un README. Une fois le r\u00e9pertoire en place, pour d\u00e9clencher la modification du contenu du catalogue, ajoutez un fichier YAML g\u00e9n\u00e9r\u00e9 \u00e0 l'aide de notre formulaire dans le dossier catalog du r\u00e9pertoire HTR-United. Vous pouvez vous inspirer du mod\u00e8le de r\u00e9pertoire propos\u00e9 ici : https://github.com/HTR-United/template-htr-united-datarepo .", "sc3": "Vos donn\u00e9es sont d\u00e9j\u00e0 en ligne et librement accessibles. V\u00e9rifiez que le jeu de donn\u00e9es est bien associ\u00e9 \u00e0 une licence explicite, que le format des transcription correspond \u00e0 l'un de ceux attendus (ALTO ou PAGE), que les images sont soit dans le jeu de donn\u00e9es, soit accessile ais\u00e9ment (par exemple par le biais d'un manifeste IIIF) et enfin que le jeu de donn\u00e9es est suffisamment d\u00e9crit (y compris concernant les normes de transcriptions adopt\u00e9es). Il vous suffit ensuite de g\u00e9n\u00e9rer une description structur\u00e9e du jeu \u00e0 l'aide de notre formulaire puis d'ajouter le fichier YAML obtenu dans le dossier catalog du r\u00e9pertoire HTR-United. Cela d\u00e9clenchera la mise \u00e0 jour du contenu du catalogue.", "sc4": "Vous ne pouvez pas librement partager vos donn\u00e9es (images ou transcriptions) mais vous souhaitez tout de m\u00eame contribuer \u00e0 HTR-United. Vous pouvez cr\u00e9er un r\u00e9pertoire au sein de l'organisation HTR-United uniquement d\u00e9di\u00e9 \u00e0 la documentation de vos donn\u00e9es gr\u00e2ce \u00e0 un fichier README. Indiquez alors comment joindre le(s) propri\u00e9taire(s) des donn\u00e9es afin d'en demander l'acc\u00e8s. Une fois ce r\u00e9pertoire en place, vous pouvez g\u00e9n\u00e9rer une description structur\u00e9e \u00e0 l'aide de notre formulaire puis d'ajouter le fichier YAML obtenu dans le dossier catalog du r\u00e9pertoire HTR-United. Cela d\u00e9clenchera la mise \u00e0 jour du contenu du catalogue."}, "title": {"use": "Utiliser les donn\u00e9es d'HTR-United", "provide": "Proposer mes donn\u00e9es avec HTR-United", "scenarios": "Sc\u00e9narios", "scenario": "Sc\u00e9nario"}, "btn": {"download": "T\u00e9l\u00e9charger le catalogue", "catalog": "Explorer le catalogue", "cite": "Citer HTR-United", "generate": "G\u00e9n\u00e9rer une description", "scenarios": "D\u00e9couvrir les sc\u00e9narios", "faq": "Aller \u00e0 la FAQ", "use": "Utiliser les donn\u00e9es", "provide": "Proposer des donn\u00e9es"}}, "cat": {"title": "Catalogue", "nota": "La langue utilis\u00e9e pour la description des jeux de donn\u00e9es correspond \u00e0 celle employ\u00e9e lors du d\u00e9p\u00f4t d'un signalement dans HTR-United.", "resultCount": "Nombre de r\u00e9sultats", "filters": "Filtres", "authors": "Auteur.ice.s", "showGuidelines": "Afficher les normes de transcription", "showCitations": "Afficher les informations de citation", "descCount": "Description statistique des r\u00e9sultats", "countUnit": "Unit\u00e9", "countAmount": "Total", "countProjects": "Projets avec cette unit\u00e9", "countChars": "Caract\u00e8res", "countLine": "Lignes", "repository": "D\u00e9p\u00f4t de donn\u00e9es", "link": "Lien", "software": "Logiciel", "citationFile": "Fichier Citation (CFF)", "share": "Partager", "tweet": "Tweeter", "full_record": "Notice compl\u00e8te"}, "catalog": {"projectName": "Projet", "all": "Tous les projets", "script": "Syst\u00e8me d'\u00e9criture", "allLanguage": "Toutes les langues", "allScript": "Tous les syst\u00e8mes d'\u00e9criture", "language": "Langue", "includeManuscript": "Au moins la moiti\u00e9 de manuscrit", "includePrint": "Au moins la moiti\u00e9 d'imprim\u00e9"}, "tools": {"title": "Outils", "seeDemo": "Voir une d\u00e9monstration", "intro": "Afin de produire de bonnes donn\u00e9es et de garantir un moyen simple de contr\u00f4ler ou de quantifier les donn\u00e9es produites, nous proposons un certain ensemble d'outils avec tutoriel (\u00e0 venir) sur la mani\u00e8re de les utiliser de mani\u00e8re autonome ou de mani\u00e8re continue.", "humg": "HumGenerator (Htr United Metadata Generator) g\u00e9n\u00e8re des m\u00e9tadonn\u00e9es, en particulier des m\u00e9triques pour vos corpus. Il est sp\u00e9cifiquement utilis\u00e9 pour g\u00e9n\u00e9rer la touche volume du sch\u00e9ma de catalogue. Il peut g\u00e9n\u00e9rer une table de comptage de caract\u00e8res afin d'aider les utilisateurs \u00e0 choisir un nouveau type de v\u00e9rit\u00e9 au sol pour couvrir plus de caract\u00e8res.", "htruc": "HTRUC permet de contr\u00f4ler que le fichier de catalogue HTR-United est parsable et conforme. HTRUC est \u00e9galement destin\u00e9 \u00e0 offrir les outils \u00e0 analyser, augmenter et compiler des statistiques sur le ou les fichiers de catalogue. Cela permet au r\u00e9f\u00e9rentiel HTR-United Central de construire un catalogue g\u00e9n\u00e9ral pour tout le monde, voir Le catalogue principal . Il peut \u00e9galement \u00eatre utilis\u00e9 avec HumGenerator pour mettre \u00e0 jour un fichier de catalogue avec de nouveaux volumes.\"\"", "htrvx": "HTRVX se concentre sur le contr\u00f4le de la qualit\u00e9 du XML. Il fournit de nombreuses options en termes de contr\u00f4le de la qualit\u00e9: la validation de sch\u00e9ma (v\u00e9rifiant que votre alto ou votre page est correcte), la d\u00e9tection de la ligne vide ou la r\u00e9gulation sans enfants, la compatibilit\u00e9 Segmonto pour la segmentation (voir Documentation ontology de Segmonto )", "chocomufin": "Chocomufin se concentre sur les personnages utilis\u00e9s dans la v\u00e9rit\u00e9 au sol. Il peut vous aider \u00e0 avoir une vue d'ensemble du personnage utilis\u00e9, peut \u00eatre utilis\u00e9 pour contr\u00f4ler lequel on utilise celui-ci (pour \u00e9viter d'avoir deux caract\u00e8res dans le m\u00eame but, qui peuvent \u00eatre courants avec des documents historiques) ou, en utilisant une table de conversion, il peut \u00eatre utilis\u00e9 pour normaliser un ensemble complet de la v\u00e9rit\u00e9 au sol."}, "form": {"download": {"dl": "T\u00e9l\u00e9chargez", "text": " e fichier ci-dessous et copiez son contenu au bout de ce", "push_link": "lien"}, "desc": {"main": "HTR-United est une organisation Github sans autre forme de personnalit\u00e9 juridique visant \u00e0 mettre en commun des jeux de donn\u00e9es et des mod\u00e8les pour l'HTR/OCR de textes de toutes p\u00e9riodes et de tout style, principalement en fran\u00e7ais mais de mani\u00e8re non restricive. 
Elle est n\u00e9e du simple besoin - pour des projets - d'avoir de potentiels v\u00e9rit\u00e9s de terrain pour entra\u00eener des mod\u00e8les rapidement sur des corpus plus petits."}, "steps": {"title": "\u00c9tapes"}, "step1": {"title": "Remplir le formulaire", "desc": "Suivre les instructions et les exemples si n\u00e9cessaire. Certaines rubriques sont optionnelles mais vous devriez essayer de donner autant de d\u00e9tails que possible. Vous pouvez aussi nous contacter en ouvrant une issue."}, "step2": {"title": "Cliquer sur \"Obtenir les m\u00e9tadonn\u00e9es format\u00e9es", "desc": "Et copier le r\u00e9sultat !"}, "step3": {"title": "Ajouter le r\u00e9sultat au catalogue d'HTR-United", "desc": "En cr\u00e9ant un nouveau fichier \u00e0 l'int\u00e9rieur de notre dossier catalog/, en suivant le lien fourni apr\u00e8s avoir g\u00e9n\u00e9r\u00e9 les m\u00e9tadonn\u00e9es. Vous pouvez aussi copier les m\u00e9tadonn\u00e9es \u00e0 l'int\u00e9rieur de votre propre fichier htr-united.yml au sein de votre r\u00e9pertoire."}, "form": {"head": "Les champs dont le nom est suivi d'un * sont obligatoires."}, "title": {"ds": "Informations g\u00e9n\u00e9rales sur le set de donn\u00e9es", "project": "Informations g\u00e9n\u00e9rales sur le projet", "data": "Informations g\u00e9n\u00e9rales sur les donn\u00e9es", "detail": "Informations d\u00e9taill\u00e9es sur les donn\u00e9es", "generate": "G\u00e9n\u00e9rer le fichier htr-united.yml"}, "play": "Lancer la d\u00e9mo ou la red\u00e9marrer", "field": {"ds_title": "Nom du d\u00e9p\u00f4t / dataset (titre)", "repolink": "Lien vers le d\u00e9p\u00f4t", "ds_desc": "Courte description", "cff": {"link": "Lien vers un fichier CITATION.cff", "info": "Les fichiers CITATION.cff permettent de fournir un mode de citation assez simple sur github par exemple. Lien:"}, "license": "Licence", "std": "Format des donn\u00e9es", "linepair": "Paires de ligne Image-Texte", "project": {"name": "Nom du projet (si diff\u00e9rent du nom du d\u00e9p\u00f4t)", "link": "Lien vers le site du projet"}, "std_info": "Les licences sont ici propos\u00e9es \u00e0 titre indicatif.", "software": "Logiciel(s) utilis\u00e9(s) pour produire les donn\u00e9es", "software_placeholder": "Vous pouvez utiliser les boutons pour remplir plus rapidement le champ.", "authors": "Contributeur-rice-s et r\u00f4le(s)", "member": {"add": "Ajouter une contribution", "rm": "Supprimer cette contribution", "name": "Pr\u00e9nom de la personne", "surname": "Nom de la personne", "transcriber": "Transcription", "aligner": "Alignement", "mainCreator": "Responsable du projet", "qualityControl": "Contr\u00f4le Qualit\u00e9", "digitizer": "Num\u00e9risation", "support": "Assistance", "status": "Cette contribution vient d'une institution", "roles": "R\u00f4les"}, "year": {"start": "Ann\u00e9e de d\u00e9but des sources", "end": "Ann\u00e9e de fin des sources", "info": "Pr\u00e9f\u00e9rez, pour des donn\u00e9es au si\u00e8cle pr\u00e8s, 1200 pour un d\u00e9but au 13e si\u00e8cle et 1299 pour une fin au 13e si\u00e8cle. Les dates n'ont pas besoin d'\u00eatre pr\u00e9cises, cela reste une indication"}, "languages": {"label": "Langue(s)", "helper": "Pour faciliter l'entr\u00e9e de donn\u00e9es, des valeurs par d\u00e9faut sont s\u00e9lectionn\u00e9es. Cliquez dessus pour les d\u00e9s\u00e9lectionner."}, "scripts": {"label": "Syst\u00e8me d'\u00e9criture", "helper": "Pour faciliter l'entr\u00e9e de donn\u00e9es, des valeurs par d\u00e9faut sont s\u00e9lectionn\u00e9es. Cliquez dessus pour les d\u00e9s\u00e9lectionner."}, "scripts-details": {"helper": "Lorsque c'est n\u00e9cessaire seulement, vous pouvez sp\u00e9cifier une sous-cat\u00e9gorie pour le script d\u00e9crit. Par exemple : Latf + Kurrent (pour qualifier la variante allemande de la Fraktur)."}, "script": {"type": {"label": "Type d'\u00e9criture", "select": {"only-manuscript": "Manuscrit uniquement", "all": "Tous", "only-typed": "Imprim\u00e9/dactylographi\u00e9 uniquement", "mainly-manuscript": "Principalement manuscrit", "mainly-typed": "Principalement imprim\u00e9/dactylographi\u00e9", "evenly-mixed": "Egale r\u00e9partition manuscrit/dactylographi\u00e9 et imprim\u00e9"}}}, "hands": {"label": "Nombre de mains (ou de fontes)", "select": {"1perfile": "1 par fichier", "1perfolder": "1 par dossier", "less10": "Inf\u00e9rieur ou \u00e9gal \u00e0 10 (peu)", "more10": "Sup\u00e9rieur \u00e0 10 (beaucoup)", "unknown": "Inconnu"}}, "prec": {"label": "Pr\u00e9cision", "select": {"exact": "Valeur exacte", "estimated": "Estimation"}}, "guidelines": {"label": "Normes de transcription", "info": "Normes de transcriptions utilis\u00e9es (format libre). Peut concerner la r\u00e9solution des abr\u00e9viations, corrections de fautes d'orthographe, l'usage de caract\u00e8res sp\u00e9ciaux, la normalisation, etc."}, "qual": {"label": "Description sommaire des quantit\u00e9s", "select": {"lines": "Lignes", "pages": "Pages", "characters": "Caract\u00e8res", "regions": "Zones", "files": "Fichiers XML"}}, "flags": {"label": "Marqueurs sp\u00e9cifique", "automaticallyAligned": {"label": "Align\u00e9 automatiquement", "helper": "Ce marqueur s'applique si vous avez utilis\u00e9 un alignement automatique mais n'avez pas effectu\u00e9 de v\u00e9rification manuelle compl\u00e8te."}}, "src": "D\u00e9tails des sources transcrites", "apa": "Le format APA est pr\u00e9f\u00e9r\u00e9 pour les citations, ce qui peut donner des r\u00e9f\u00e9rences longues comme Allport, G. W. (1930\u20131967). Correspondence. Gordon W. Allport Papers (HUG 4118.10), Harvard University Archives, Cambridge, MA, United States., cf. APA Style. Des formats plus courts sont autoris\u00e9. Le lien ou la r\u00e9f\u00e9rence APA peuvent suffire."}, "input": {"reponame": "Nom du d\u00e9p\u00f4t", "repolink": "Lien vers le d\u00e9p\u00f4t", "cff": "Lien vers un fichier CITATION.cff", "projectname": "Nom du projet", "projectlink": "Lien vers le site du projet (s'il existe)", "src": "Lien vers le catalogue ou la ressource", "datebegin": "Exemple: 1800", "dateend": "Exemple: 1899", "guidelines": "Normes de transcription", "quantity": "Exemple: 200", "apa": "R\u00e9f\u00e9rence en mode APA"}, "btn": {"get": "Obtenir les m\u00e9tadonn\u00e9es format\u00e9es"}, "finale": {"steps": "\u00c9tapes de mise en place", "step1": "(1) R\u00e9cup\u00e9rez le contenu, au choix:", "download": "T\u00e9l\u00e9chargez", "copy": "Copiez", "step2": "(2) Puis ajoutez le au catalogue HTR-United via une c\u0155eation de fichier ou de ticket", "notWorking": "Si cela ne marche pas avec les liens ci-dessus, ouvrez une issue sur le d\u00e9p\u00f4t HTR-United:", "newFile": "Cr\u00e9er le fichier", "newIssue": "Ouvrir un ticket"}}, "actions": {"introduction": "Les actions Github permettent d'ex\u00e9cuter des scripts \u00e0 chaque fois que vous modifiez vos donn\u00e9es. Le formulaire suivant va g\u00e9n\u00e9rer un fichier de configuration pour utiliser nos 4 outils automatiquement et assurer \u00e0 la fois une compatibilit\u00e9 compl\u00e8te avec l'initiative HTR-United et des donn\u00e9es de haute qualit\u00e9. Certaines options ci-dessous se concentreront sur le contr\u00f4le des donn\u00e9es, votre fichier de catalogage ou simplement la mise \u00e0 jour automatique avec les m\u00e9triques de votre choix !", "generalInformations": "Informations g\u00e9n\u00e9rales sur votre d\u00e9p\u00f4t de donn\u00e9es", "htrUnitedFilename": "Nom de votre fichier HTR-United de m\u00e9tadonn\u00e9es (catalogue)", "dataUnixPath": "Chemin des donn\u00e9es (Format UNIX)", "branchName": "Nom de la branche principale", "activateHTRUC": "Activer", "activateHUMG": "Activer", "updateCatalogFile": "Mettre \u00e0 jour le fichier catalogue", "formatGithubUrl": "Adresse sans la partie github.com, uniquement nomDutilisateur/d\u00e9p\u00f4t", "generateBadge": "G\u00e9n\u00e9rer des badges", "gitRelease": "Produire des versions automatiquement", "activateHTRVX": "Activer", "activateSegmonto": "Tester votre compatibilit\u00e9 avec Segmonto", "activateEmptyLine": "V\u00e9rifier qu'il n'existe pas de lignes ou de r\u00e9gions vides", "activateRaiseEmptyLine": "\u00c9mettre une erreur s'il existe des lignes ou des r\u00e9gions vides", "activateXSD": "V\u00e9rifier votre sch\u00e9ma XML", "activatechocoMufin": "Activer", "chocoMufinMode": "Mode", "htrUnitedFilenameHelp": "Ce fichier aurait d\u00fb \u00eatre g\u00e9n\u00e9r\u00e9 avec le formulaire sur ce site Web: il d\u00e9crit tout votre d\u00e9p\u00f4t avec des m\u00e9tadonn\u00e9es, assurez-vous de le faire en premier! Ce fichier est g\u00e9n\u00e9ralement nomm\u00e9 htr-united.yml et doit \u00eatre \u00e0 la racine de votre d\u00e9p\u00f4t GitHub.", "dataUnixPathHelpP1": "Ce chemin est le chemin de votre r\u00e9f\u00e9rentiel. Utilisez * comme joker pour un nom de fichier, ** pour un dossier. Vous pouvez avoir un seul chemin, tel que ./data/*.xml ou plusieurs, comme ./french/data/*.xml ./english/data/*.xml. Si vous avez une structure telle que ./data/a_book/certains.xml et ./data/b_book/some.xml, le chemin UNIX est ./data/**/*.xmlmain ou master.", "dataUnixPathHelpP2": "Dans l'exemple de droite, si TNAH-2021-Project-Correspondance-Berlioz est la racine de votre r\u00e9f\u00e9rentiel de donn\u00e9es, le chemin d'acc\u00e8s pour l\u2019ensemble des fichiers XML est donnees/**/*. xml.", "activateHTRUCHelp": "Cela effectuera un test sur votre htr-united.yml et garantit qu'il est conforme aux sch\u00e9mas. Si le sch\u00e9ma \u00e9volue, cela vous permet d'assurer votre compatibilit\u00e9 avec lui.", "activateHUMGHelp": "Cela produira une vue d'ensemble de la profondeur du nombre de caract\u00e8res, de zones, de lignes et de pages que vous avez, mais vous donne \u00e9galement la quantit\u00e9 de zone ou de lignes par type si vous avez saisi vos zones et vos lignes.", "updateCatalogFileHelp": "Met \u00e0 jour automatiquement les informations volume du fichier de catalogage avec de nouvelles mesures (ligne, caract\u00e8res, fichiers, zones).
Cela cr\u00e9e automatiquement de nouveaux fichiers dans votre d\u00e9p\u00f4t via un push git. Cela n'endommage pas vos donn\u00e9es.", "generateBadgeHelp": "En utilisant cette option, des badges seront g\u00e9n\u00e9r\u00e9s, tels que que vous pouvez inclure dans votre fichier README afin d\u2019afficher des statistiques et parce que les badges, c\u2019est cool.
Cela cr\u00e9e automatiquement de nouveaux fichiers dans votre d\u00e9p\u00f4t via un push git. Cela n'endommage pas vos donn\u00e9es.", "gitReleaseHelp": "Cr\u00e9e une release (version) Github \u00e0 chaque fois que la branche principale est modifi\u00e9e. Coupl\u00e9 avec Zenodo, cela vous permet d'avoir une conservation \u00e0 long terme et un DOI (identifiant d'objet num\u00e9rique ) pour chacune des \u00e9volutions de votre d\u00e9p\u00f4t !", "activateHTRVXHelp": "Cela vous aidera \u00e0 vous assurer que votre XML est valide et suit quelques autres sp\u00e9cifications.", "activateSegmontoHelp": "Segmonto est une ontologie pour le typage des zones (parfois appel\u00e9es r\u00e9gions) et des lignes. Cela vous assure que vous \u00eates compatible avec cela. cf. la publication ou le site Segmonto .", "activateEmptyLineHelp": "Cela cr\u00e9e des avertissements si des lignes ne contiennent aucun caract\u00e8re ou si des r\u00e9gions sont vides/ Cela ne provoque pas d\u2019erreur!", "activateRaiseEmptyLineHelp": "En compl\u00e9ment de l\u2019option ci-dessus, g\u00e9n\u00e8re une erreur en cas de ligne ou de r\u00e9gion vide.", "activateXSDHelp": "Cela garantit simplement que vous \u00eates compatible avec le sch\u00e9ma XML. Cela devrait toujours \u00eatre le cas si vous utilisez une interface utilisateur telle que Transkribus ou eScriptorium.", "activatechocoMufinHelp": "Apr\u00e8s avoir lu chaque ligne, \u00e9tudie les caract\u00e8res utilis\u00e9s.", "chocoMufinModeHelp": "Avec le mode G\u00e9n\u00e9ration, les actions ne contr\u00f4lent pas vos caract\u00e8res mais listent tous les caract\u00e8res utilis\u00e9s.
(Utilisateurs avanc\u00e9s) En mode Contr\u00f4le, vous devez fournir un fichier nomm\u00e9 table.csv pour aider Chocomufin \u00e0 contr\u00f4ler vos donn\u00e9es. Voir le tutoriel pour plus de d\u00e9tails.", "thisUses": "Utilise", "testCatalog": "Test du fichier de catalogage", "testReport": "G\u00e9n\u00e9ration de rapports", "testXML": "Test des fichiers XML (Structure)", "testChars": "Contr\u00f4le des caract\u00e8res", "githubURLHelp": "La r\u00e9ponse doit ressembler \u00e0 https://github.com/htr-united/cremma-medieval ou https://github.com/demo-user/demo-repository.", "githubURL": "URL Github du d\u00e9p\u00f4t", "generate": "G\u00e9n\u00e9rer le fichier Github action", "steps": "\u00c9tapes de mise en place", "step1": "(1) R\u00e9cup\u00e9rez le contenu, au choix:", "download": "T\u00e9l\u00e9chargez", "copy": "Copiez", "step2": "(2) Ajoutez le \u00e0 votre d\u00e9p\u00f4t en l'ajoutant dans le dossier", "add": "Ajouter la configuration sur", "edit": "\u00c9diter la configuration si elle existe d\u00e9j\u00e0 sur", "addBadge": "(3) Ajoutez le texte suivant \u00e0 votre fichier README si vous voulez afficher les badges", "editReadme": "\u00c9ditez le Readme.md sur Github"}, "models": {"title": "Mod\u00e8les", "p1": "Le catalogue d'HTR-United ne r\u00e9f\u00e9rence pas directement de mod\u00e8les de transcription, mais plut\u00f4t les donn\u00e9es ayant permis d'en produire. Vous pouvez consulter les r\u00e9pertoires des jeux de donn\u00e9es qui vous int\u00e9ressent pour savoir s'ils renvoient vers un mod\u00e8le public.", "p2": "Il existe des collections de mod\u00e8les publiques. Vous pouvez par exemple consulter le groupe nomm\u00e9 \"OCR/HTR model repository\" sur Zenodo qui contient de nombreux mod\u00e8les de transcription librement r\u00e9utilisables.", "btn": {"zenodo1": "Voir \"OCR/HTR model repository\" sur Zenodo"}}, "changelog": {"title": "Changelog du sch\u00e9ma", "disclaimer": "

Pour des raisons de simplicit\u00e9, le contenu de cette page n'est pas disponible en fran\u00e7ais.

"}} \ No newline at end of file