-
Notifications
You must be signed in to change notification settings - Fork 18
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Polyglot Phrases Implementation (#96)
* Just some examples of polyglot at work * Test changes for internationalizaton * Internationalization - replaced all plain string occurrences on the website with polyglot phrases * Delete unnecessary comments and tests * Delete localization folder * Completed suggested changes for PR - Polyglot Phrases Implementation * Fix HeaderTabButton onSelected * Added requested changes by David Co-authored-by: dotasek <[email protected]>
- Loading branch information
Showing
26 changed files
with
209 additions
and
123 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,64 @@ | ||
{"Validate": "Validate", "Options": "Options"} | ||
{ | ||
"validate_heading" : "Validate", | ||
"appscreen_validator_major" : "Validate Resources", | ||
"appscreen_validator_minor" : "Manually enter, or upload resources for validation.", | ||
"enter_resources_heading" : "Enter Resource", | ||
"manual_entry_place_holder" : "Enter Resource Manually...", | ||
"manual_entry_title" : "Code", | ||
"manual_entry_error" : "Please enter something to validate.", | ||
"manual_entry_cannot_parse_exception" : "Cannot parse entered text as valid JSON/XML.", | ||
"validate_button" : "Validate", | ||
"upload_resources_heading" : "Upload Resources", | ||
"upload_files_title" : "Uploaded Files", | ||
"upload_button" : "Upload", | ||
"upload_entry_view" : "View", | ||
"upload_entry_delete" : "Delete", | ||
"options_heading" : "Options", | ||
"appscreen_options_major" : "Validation Options", | ||
"appscreen_options_minor" : "Modify setting for validating resources.", | ||
"options_flags_title" : "Flags", | ||
"options_flags_1_title" : "Native Validation (doNative)", | ||
"options_flags_1_description" : "By default, the validation engine only validates using the FHIR structures and profiles. The publication processes also generate a variety of xml, json and RDF schemas. You can ask the validator to validate against these as well using this option. Note that there is nothing in these schemas that is not validated directly by the engine itself anyway, so the main use for this is to see the kind of errors that would be reported from these schemas by other software.", | ||
"options_flags_2_title" : "Must Support (hintAboutMustSupport)", | ||
"options_flags_2_description" : "In some cases (e.g. when creating examples for implementation guides or when checking for potential interoperability issues with a new communication partner), it can be useful to know when data elements are present in an instance when those elements are not \"mustSupport\" in the profile(s) the instance is being validated against. Identifying situations where this occurs might drive a change to the profile or cause a designer to drop an element from the instance. In other cases, the presence of the element can be fine and the information message ignored.", | ||
"options_flags_3_title" : "Assume Valid Rest References (assumeValidRestReferences)", | ||
"options_flags_3_description" : "If the validator can't fetch target resources, it can at least be instructed validate that the target resource is correct. For instance, if the allowed target types are (Patient or RelatedPerson), and the reference is Group/12345, then this would be usually be an error. However this is not actually explicitly stated in the FHIR specification - a reference could be to http://some.server/somewhere - it doesn't need to look like a valid FHIR RESTful reference. In fact, it's not an error even if it happens to. So by default, the validator can assume nothing about the type of resource from the content of the reference itself. However most implementers do follow those rules - a reference to either Group/12345 or http://some-server/somwhere/Group/12345 is definitely to a Group resource. (and it's definitely recommended to follow these rules). The flag assumeValidRestReferences instructs the validator to use the type found in references that look like valid RESTful URLs when validating the type of the reference.", | ||
"options_flags_4_title" : "Extensible Binding Warnings (noExtensibleBindingWarnings)", | ||
"options_flags_4_description" : "When the validator encounters a code that is not part of an extensible binding, it adds a warning to suggest that the code be reviewed. The validator can't determine whether the meaning of the code makes it an inappropriate extension, or not; this requires human review. Hence, the warning. But the code may be valid - that's why extensible is defined - so in some operational uses of the validator, it is appropriate to turn these warnings off", | ||
"options_flags_5_title" : "Show Times (showTimes)", | ||
"options_flags_5_description" : "When the validator encounters a code that is not part of an extensible binding, it adds a warning to suggest that the code be reviewed. The validator can't determine whether the meaning of the code makes it an inappropriate extension, or not; this requires human review. Hence, the warning. But the code may be valid - that's why extensible is defined - so in some operational uses of the validator, it is appropriate to turn these warnings off", | ||
"options_flags_6_title" : "Allow Example URLs (allow-example-urls)", | ||
"options_flags_6_description" : "Some of the examples in the FHIR specification have URLs in them that refer to example.org. By default, the validator will always mark any such references as an error, but this can be overridden with this parameter.", | ||
"options_fhir_title" : "FHIR version", | ||
"options_default_label" : "Version", | ||
"options_fhir_description" : "The validator checks the resource against the base specification. By default, this is specification version 4.0.1.", | ||
"options_ig_title" : "Implementation Guides", | ||
"options_ig_description_1" : "You can validate against one or more published implementation guides. Select IGs using the dropdown menus below and click the ", | ||
"options_ig_description_2" : "Add", | ||
"options_ig_description_3" : " button to include them in your validation.", | ||
"options_ig_dropdown" : "Select IG", | ||
"options_ig_dropdown_hint" : "Search IGS...", | ||
"options_ig_version_dropdown_default" : "No Compatible versions", | ||
"options_ig_version_dropdown_hint" : "Select IG version", | ||
"options_ig_add" : "Add", | ||
"options_ig_selected" : "Selected IGs", | ||
"options_ig_not_supported" : "IG not supported for FHIR version", | ||
"options_settings_title" : "Other Settings", | ||
"options_settings_snomed_title" : "Select SNOMED Version", | ||
"options_settings_snomed_description" : "You can specify which edition of SNOMED CT for the terminology server to use when doing SNOMED CT Validation.", | ||
"options_settings_tm_title" : "Set Terminology Server", | ||
"options_settings_tm_description" : "The validation engine uses a terminology server to validate codes from large external terminologies such as SNOMED CT, LOINC, RxNorm, etc. By default, the terminology server used is tx.fhir.org, which supports most of these terminologies. If you want to use another terminology server, you can specify one here. As a warning, the server will check that the CapabilityStatement of the provided server is set correctly.", | ||
"options_settings_tm_verify" : "Verify", | ||
"options_settings_tm_success" : "Terminology server validated successfully!", | ||
"options_settings_tm_error" : "Terminology server could not be validated!", | ||
"footer_running_version" : "running validator v", | ||
"footer_github" : "view project on github", | ||
"footer_create_issue" : "log an issue with the team", | ||
"footer_download_cli" : "download the latest cli", | ||
"footer_doc" : "view the validator documentation", | ||
"validation_results" : "Results", | ||
"validation_fatals" : "Fatals", | ||
"validation_errors" : "Errors", | ||
"validation_warnings" : "Warnings", | ||
"validation_info" : "Information" | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,11 +1,11 @@ | ||
package model | ||
|
||
enum class AppScreen(val display: String) { | ||
VALIDATOR("Validate"), | ||
SETTINGS("Options"); | ||
enum class AppScreen(val polyglotKey: String) { | ||
VALIDATOR("validate_heading"), | ||
SETTINGS("options_heading"); | ||
|
||
companion object { | ||
private val map = AppScreen.values().associateBy(AppScreen::display) | ||
private val map = AppScreen.values().associateBy(AppScreen::name) | ||
fun fromDisplay(type: String) = map[type] | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.