<commit_before>error.generic.title: "An error occurred"
error.generic.text: "An unexpected error occurred. Please try again later."
error.403.title: "Access denied"
error.403.text: "You do not have access to this page."
error.404.title:  "Page not found"
error.404.text: "Oops, we were unable to find the page."
entity.delete.title: "Delete entity"
entity.delete.confirmation: "You are about to delete the entity %name%, are you sure?"
entity.list.title: My entities
entity.list.empty: There are no entities configured
entity.list.no_service_selected: Please select a service
entity.list.name: Entity
entity.list.entity_id: Entity ID
entity.list.primary_contact: Primary contact
entity.list.environment: Environment
entity.list.state: State
entity.list.action.view: View
entity.list.action.edit: Edit
entity.list.action.copy: Copy
entity.list.action.delete: Delete
entity.list.action.copy_to_production: Copy to production
entity.edit.error.publish: "Unable to publish the entity, try again later"
entity.edit.error.push: "Unable to publish the entity, try again later"
entity.edit.title: Service Provider registration form
entity.edit.info.title: Info
entity.edit.info.html: "
<p>Documentation about this SP registration form can be found at:
<a href=\"https://wiki.surfnet.nl/x/isZWAw\">https://wiki.surfnet.nl/x/isZWAw</a>.</p>

<p>The registration of your Service Provider consists of two parts. A contractual and technical part. This form covers the technical part. The contractual part will be handled by SURFmarket.
In the following pages we will ask you to submit the necessary information that allows us to create a test connection. With the following details ready we estimate this process will take around 20 minutes to complete. Information we need and collect through this form includes:</p>
<ul>
<li>Various contacts responsible for the entity. Support, administrative and technical
should be present.</li>
<li>Information about SAML 2.0 configuration.</li>
<li>Metadata information including URL, certificate and logo of your entity.</li>
<li>A list of the attributes your Service Provider requires to operate.</li>
</ul>

<p>
<strong>Publish</strong>
When all fields are filled in correctly you can publish the configuration to the SURFconext test environment. The service will be available directly for testing.
</p>

<p>
<strong>Update</strong>
The configuration can be modified whenever you see fit. Just change the fields, press 'update' and 'confirm'. The changes are available instantenously.
</p>


<p>
<strong>Production</strong>
When tests are successful you can request a production connection. Simply press the button 'to production' to initiate this process.
<strong>Note:</strong> your service can get production status only if the required contracts are in place.
</p>

<p>If there are any questions during completion of the form don’t hesitate to mail to <EMAIL>. Please add the ticket number to the subject (CXT-...).</p>
"
entity.edit.general.title: General
entity.edit.general.html: "<p>Enter/edit your contact information below. We will use this information in case we have additional questions.</p>"
entity.edit.metadata.fetch.exception: "Unable to load the metadata from the provided import url."
entity.edit.metadata.html: "Please provide the metadata URL of your entity. The URL will be validated and the fields below will be filled in automatically (when available in the metadata). <strong>If the input is not correct please change the settings in your SAML enabled software.</strong> Note that the fields with a * are required and need to be correctly configured. Check the following page for more information: <a href=\"https://wiki.surfnet.nl/x/vclWAw\">https://wiki.surfnet.nl/x/vclWAw</a>.</p>"
entity.edit.metadata.invalid.exception: "An error occurred while importing the metadata."
entity.edit.metadata.title: Metadata
entity.edit.metadata.parse.exception: "The provided metadata is invalid."
entity.edit.contact_information.title: Contact information
entity.edit.contact_information.html: "
<p>Every service connected to SURFconext requires various types of contact details. Depending on the nature of the issue we will consult the following contact:</p>
<ul>
<li>Administrative</li>
<li>Technical</li>
<li>Support</li>
</ul>
<p>See the question mark for a more extensive description. Possibly some information below already has been filled through the metadata. Please check the fields and edit when necessary.</p>

<p><i>Technical and administrative contact details will not be communicated to end-users.</i></p>
"
entity.edit.attribute_input_placeholder: The service will use this attribute to...
entity.edit.attributes.title: Attributes
entity.edit.attributes.html: "
<p>When an end-user logs in to your SP, SURFconext sends a SAML-assertion to the SP. The SAML-assertion contains statements about the user, including identity and possibly a number of other attributes (see list below). Select the attributes this service requires to operate. For each attribute you request a <strong>valid reason</strong> must be provided which will be reviewed. Note: <strong>every extra attribute you request could complicate the contractual phase</strong>: just one more reason to not select more attributes than you absolutely need. Also note that SURFconext operates with a minimal disclosure principle. This means that only the absolute necessary (personal) information is transferred to a entity. Check this page for more information: <a href=\"https://wiki.surfnet.nl/x/xcpWAw\">https://wiki.surfnet.nl/x/xcpWAw</a>.</p>

<p>Possibly some boxes have already been checked. This information is reused from the metadata.</p>

<p><i>Identity Providers will be informed about the attributes your service requests and must agree to the release of these attributes to your entity.</i></p>
"
entity.edit.comments.title: Comments
entity.edit.comments.html: "<p>If there are any questions regarding your SURFconext connection or this form, please leave them here.</p>"
entity.edit.information.ticketNumber: Text should be set in web translations
entity.edit.information.importUrl: Text should be set in web translations
entity.edit.information.metadataUrl: Text should be set in web translations
entity.edit.information.pastedMetadata: Text should be set in web translations
entity.edit.information.certificate: Text should be set in web translations
entity.edit.information.descriptionNl: Text should be set in web translations
entity.edit.information.descriptionEn: Text should be set in web translations
entity.edit.information.administrativeContact: Text should be set in web translations
entity.edit.information.supportContact: Text should be set in web translations
entity.edit.information.givenNameAttribute: Text should be set in web translations
entity.edit.information.surNameAttribute: Text should be set in web translations
entity.edit.information.commonNameAttribute: Text should be set in web translations
entity.edit.information.displayNameAttribute: Text should be set in web translations
entity.edit.information.emailAddressAttribute: Text should be set in web translations
entity.edit.information.organizationAttribute: Text should be set in web translations
entity.edit.information.organizationTypeAttribute: Text should be set in web translations
entity.edit.information.affiliationAttribute: Text should be set in web translations
entity.edit.information.entitlementAttribute: Text should be set in web translations
entity.edit.information.principleNameAttribute: Text should be set in web translations
entity.edit.information.uidAttribute: Text should be set in web translations
entity.edit.information.preferredLanguageAttribute: Text should be set in web translations
entity.edit.information.personalCodeAttribute: Text should be set in web translations
entity.edit.information.scopedAffiliationAttribute: Text should be set in web translations
entity.edit.information.eduPersonTargetedIDAttribute: Text should be set in web translations
entity.edit.information.comments: Text should be set in web translations
entity.published_production.text.html: "Thanks for publishing \"%entityName%\" to our production environment."
entity.published_production.title: "Successfully published the entity to production"
entity.published_test.text.html: "Thanks for publishing \"%entityName%\" to our test environment."
entity.published_test.title: "Successfully published the entity to test"
privacy.edit.title: GDPR related questions
privacy.edit.introduction.html: "<p><strong>Pellentesque habitant morbi tristique</strong> senectus et netus et malesuada fames ac turpis egestas. Vestibulum tortor quam, feugiat vitae, ultricies eget, tempor sit amet, ante. Donec eu libero sit amet quam egestas semper. <em>Aenean ultricies mi vitae est.</em> Mauris placerat eleifend leo. Quisque sit amet est et sapien ullamcorper pharetra. Vestibulum erat wisi, condimentum sed, <code>commodo vitae</code>, ornare sit amet, wisi. Aenean fermentum, elit eget tincidunt condimentum, eros ipsum rutrum orci, sagittis tempus lacus enim ac dui. <a href=\"#\">Donec non enim</a> in turpis pulvinar facilisis. Ut felis.</p>"
privacy.form.label.accessData: What (kind of) data is processed?
privacy.form.label.certification: "Can you supply a Third Party Memorandum? If not: skip to question 9"
privacy.form.label.certificationFrom: Valid from:
privacy.form.label.certificationLocation: Where can an institution find/request it?
privacy.form.label.certificationTo: Valid to:
privacy.form.label.country: In what country is the data stored?
privacy.form.label.otherInfo: Other data privacy and security information
privacy.form.label.privacyPolicy: "Do you publish your privacy policy? If not: skip to question 14"
privacy.form.label.privacyPolicyUrl: What is the URL?
privacy.form.label.securityMeasures: What security measures have you taken?
privacy.form.label.snDpaWhyNot: What articles pose a problem & why?
privacy.form.label.surfmarketDpaAgreement: "Did you agree a DPA with SURFmarket? If yes: skip to question 12"
privacy.form.label.surfnetDpaAgreement: Are you willing to sign the SURF model DPA? If “Yes” skip to question 12
privacy.form.label.whatData: What (kind of) data is processed?
privacy.information.accessData: Specify which organizations, including your own, and per organization what roles / (groups of) individuals have access to the data (including backups etc). Explain why they need access, and what access exactly each one has (like read only of certain specified data).
privacy.information.certification: Is there an active valid certification, like ISO27001, ISO27002, ISAE3402 etc?
privacy.information.certificationLocation: Where can an institution find (URL) or requestion the certifications and third party memorandum?
privacy.information.country: In what country/countries is the data stored (including copies etc)
privacy.information.otherInfo: What other information do you want to share regarding data security, privacy etc?
privacy.information.privacyPolicy: Do you publish you a privacy policy online?
privacy.information.privacyPolicyUrl: What is the URL to your privacy policy
privacy.information.securityMeasures: What security measures have you taken (remember the encryption during transport and storage)?
privacy.information.snDpaWhyNot: What items of the SURF model Data Processing Agreement would you want to discuss with an institution, and what is your problem with those articles / those items?
privacy.information.surfmarketDpaAgreement: Did you agree a Data Processing Agreement with SURFmarket?
privacy.information.surfnetDpaAgreement: Are you willing to sign the model SURF Data Processing Agreement?
privacy.information.whatData: Describe what (kind of) data is processed in the service, and pay specific attention to possible processing of personal data.
service.create.title: Add new service
service.edit.title: Edit service
mail.confirmation.publish_production.comment: Comments
mail.confirmation.publish_production.entity_id: EntityID
mail.confirmation.publish_production.entity_name_en: Entity name (en)
mail.confirmation.publish_production.service_name: Service name
mail.confirmation.publish_production.publish_date: Publish date
mail.confirmation.publish_production.team_id: Team id
mail.confirmation.publish_production.subject: 'Production connection has been requested (%entityId%)'<commit_msg>Add numbering to question labels<commit_after>error.generic.title: "An error occurred"
error.generic.text: "An unexpected error occurred. Please try again later."
error.403.title: "Access denied"
error.403.text: "You do not have access to this page."
error.404.title:  "Page not found"
error.404.text: "Oops, we were unable to find the page."
entity.delete.title: "Delete entity"
entity.delete.confirmation: "You are about to delete the entity %name%, are you sure?"
entity.list.title: My entities
entity.list.empty: There are no entities configured
entity.list.no_service_selected: Please select a service
entity.list.name: Entity
entity.list.entity_id: Entity ID
entity.list.primary_contact: Primary contact
entity.list.environment: Environment
entity.list.state: State
entity.list.action.view: View
entity.list.action.edit: Edit
entity.list.action.copy: Copy
entity.list.action.delete: Delete
entity.list.action.copy_to_production: Copy to production
entity.edit.error.publish: "Unable to publish the entity, try again later"
entity.edit.error.push: "Unable to publish the entity, try again later"
entity.edit.title: Service Provider registration form
entity.edit.info.title: Info
entity.edit.info.html: "
<p>Documentation about this SP registration form can be found at:
<a href=\"https://wiki.surfnet.nl/x/isZWAw\">https://wiki.surfnet.nl/x/isZWAw</a>.</p>

<p>The registration of your Service Provider consists of two parts. A contractual and technical part. This form covers the technical part. The contractual part will be handled by SURFmarket.
In the following pages we will ask you to submit the necessary information that allows us to create a test connection. With the following details ready we estimate this process will take around 20 minutes to complete. Information we need and collect through this form includes:</p>
<ul>
<li>Various contacts responsible for the entity. Support, administrative and technical
should be present.</li>
<li>Information about SAML 2.0 configuration.</li>
<li>Metadata information including URL, certificate and logo of your entity.</li>
<li>A list of the attributes your Service Provider requires to operate.</li>
</ul>

<p>
<strong>Publish</strong>
When all fields are filled in correctly you can publish the configuration to the SURFconext test environment. The service will be available directly for testing.
</p>

<p>
<strong>Update</strong>
The configuration can be modified whenever you see fit. Just change the fields, press 'update' and 'confirm'. The changes are available instantenously.
</p>


<p>
<strong>Production</strong>
When tests are successful you can request a production connection. Simply press the button 'to production' to initiate this process.
<strong>Note:</strong> your service can get production status only if the required contracts are in place.
</p>

<p>If there are any questions during completion of the form don’t hesitate to mail to <EMAIL>. Please add the ticket number to the subject (CXT-...).</p>
"
entity.edit.general.title: General
entity.edit.general.html: "<p>Enter/edit your contact information below. We will use this information in case we have additional questions.</p>"
entity.edit.metadata.fetch.exception: "Unable to load the metadata from the provided import url."
entity.edit.metadata.html: "Please provide the metadata URL of your entity. The URL will be validated and the fields below will be filled in automatically (when available in the metadata). <strong>If the input is not correct please change the settings in your SAML enabled software.</strong> Note that the fields with a * are required and need to be correctly configured. Check the following page for more information: <a href=\"https://wiki.surfnet.nl/x/vclWAw\">https://wiki.surfnet.nl/x/vclWAw</a>.</p>"
entity.edit.metadata.invalid.exception: "An error occurred while importing the metadata."
entity.edit.metadata.title: Metadata
entity.edit.metadata.parse.exception: "The provided metadata is invalid."
entity.edit.contact_information.title: Contact information
entity.edit.contact_information.html: "
<p>Every service connected to SURFconext requires various types of contact details. Depending on the nature of the issue we will consult the following contact:</p>
<ul>
<li>Administrative</li>
<li>Technical</li>
<li>Support</li>
</ul>
<p>See the question mark for a more extensive description. Possibly some information below already has been filled through the metadata. Please check the fields and edit when necessary.</p>

<p><i>Technical and administrative contact details will not be communicated to end-users.</i></p>
"
entity.edit.attribute_input_placeholder: The service will use this attribute to...
entity.edit.attributes.title: Attributes
entity.edit.attributes.html: "
<p>When an end-user logs in to your SP, SURFconext sends a SAML-assertion to the SP. The SAML-assertion contains statements about the user, including identity and possibly a number of other attributes (see list below). Select the attributes this service requires to operate. For each attribute you request a <strong>valid reason</strong> must be provided which will be reviewed. Note: <strong>every extra attribute you request could complicate the contractual phase</strong>: just one more reason to not select more attributes than you absolutely need. Also note that SURFconext operates with a minimal disclosure principle. This means that only the absolute necessary (personal) information is transferred to a entity. Check this page for more information: <a href=\"https://wiki.surfnet.nl/x/xcpWAw\">https://wiki.surfnet.nl/x/xcpWAw</a>.</p>

<p>Possibly some boxes have already been checked. This information is reused from the metadata.</p>

<p><i>Identity Providers will be informed about the attributes your service requests and must agree to the release of these attributes to your entity.</i></p>
"
entity.edit.comments.title: Comments
entity.edit.comments.html: "<p>If there are any questions regarding your SURFconext connection or this form, please leave them here.</p>"
entity.edit.information.ticketNumber: Text should be set in web translations
entity.edit.information.importUrl: Text should be set in web translations
entity.edit.information.metadataUrl: Text should be set in web translations
entity.edit.information.pastedMetadata: Text should be set in web translations
entity.edit.information.certificate: Text should be set in web translations
entity.edit.information.descriptionNl: Text should be set in web translations
entity.edit.information.descriptionEn: Text should be set in web translations
entity.edit.information.administrativeContact: Text should be set in web translations
entity.edit.information.supportContact: Text should be set in web translations
entity.edit.information.givenNameAttribute: Text should be set in web translations
entity.edit.information.surNameAttribute: Text should be set in web translations
entity.edit.information.commonNameAttribute: Text should be set in web translations
entity.edit.information.displayNameAttribute: Text should be set in web translations
entity.edit.information.emailAddressAttribute: Text should be set in web translations
entity.edit.information.organizationAttribute: Text should be set in web translations
entity.edit.information.organizationTypeAttribute: Text should be set in web translations
entity.edit.information.affiliationAttribute: Text should be set in web translations
entity.edit.information.entitlementAttribute: Text should be set in web translations
entity.edit.information.principleNameAttribute: Text should be set in web translations
entity.edit.information.uidAttribute: Text should be set in web translations
entity.edit.information.preferredLanguageAttribute: Text should be set in web translations
entity.edit.information.personalCodeAttribute: Text should be set in web translations
entity.edit.information.scopedAffiliationAttribute: Text should be set in web translations
entity.edit.information.eduPersonTargetedIDAttribute: Text should be set in web translations
entity.edit.information.comments: Text should be set in web translations
entity.published_production.text.html: "Thanks for publishing \"%entityName%\" to our production environment."
entity.published_production.title: "Successfully published the entity to production"
entity.published_test.text.html: "Thanks for publishing \"%entityName%\" to our test environment."
entity.published_test.title: "Successfully published the entity to test"
privacy.edit.title: GDPR related questions
privacy.edit.introduction.html: "<p><strong>Pellentesque habitant morbi tristique</strong> senectus et netus et malesuada fames ac turpis egestas. Vestibulum tortor quam, feugiat vitae, ultricies eget, tempor sit amet, ante. Donec eu libero sit amet quam egestas semper. <em>Aenean ultricies mi vitae est.</em> Mauris placerat eleifend leo. Quisque sit amet est et sapien ullamcorper pharetra. Vestibulum erat wisi, condimentum sed, <code>commodo vitae</code>, ornare sit amet, wisi. Aenean fermentum, elit eget tincidunt condimentum, eros ipsum rutrum orci, sagittis tempus lacus enim ac dui. <a href=\"#\">Donec non enim</a> in turpis pulvinar facilisis. Ut felis.</p>"
privacy.form.label.accessData: 2. Who can access the data?
privacy.form.label.certification: "5. Can you supply a Third Party Memorandum? If not: skip to question 9"
privacy.form.label.certificationFrom: 7. Valid from:
privacy.form.label.certificationLocation: 6. Where can an institution find/request it?
privacy.form.label.certificationTo: 8. Valid to:
privacy.form.label.country: 3. In what country is the data stored?
privacy.form.label.otherInfo: 14. Other data privacy and security information
privacy.form.label.privacyPolicy: "12. Do you publish your privacy policy? If not: skip to question 14"
privacy.form.label.privacyPolicyUrl: 13. What is the URL?
privacy.form.label.securityMeasures: 4. What security measures have you taken?
privacy.form.label.snDpaWhyNot: 11. What articles pose a problem & why?
privacy.form.label.surfmarketDpaAgreement: "9. Did you agree a DPA with SURFmarket? If yes: skip to question 12"
privacy.form.label.surfnetDpaAgreement: 10. Are you willing to sign the SURF model DPA? If “Yes” skip to question 12
privacy.form.label.whatData: 1. What (kind of) data is processed?
privacy.information.accessData: Specify which organizations, including your own, and per organization what roles / (groups of) individuals have access to the data (including backups etc). Explain why they need access, and what access exactly each one has (like read only of certain specified data).
privacy.information.certification: Is there an active valid certification, like ISO27001, ISO27002, ISAE3402 etc?
privacy.information.certificationLocation: Where can an institution find (URL) or requestion the certifications and third party memorandum?
privacy.information.country: In what country/countries is the data stored (including copies etc)
privacy.information.otherInfo: What other information do you want to share regarding data security, privacy etc?
privacy.information.privacyPolicy: Do you publish you a privacy policy online?
privacy.information.privacyPolicyUrl: What is the URL to your privacy policy
privacy.information.securityMeasures: What security measures have you taken (remember the encryption during transport and storage)?
privacy.information.snDpaWhyNot: What items of the SURF model Data Processing Agreement would you want to discuss with an institution, and what is your problem with those articles / those items?
privacy.information.surfmarketDpaAgreement: Did you agree a Data Processing Agreement with SURFmarket?
privacy.information.surfnetDpaAgreement: Are you willing to sign the model SURF Data Processing Agreement?
privacy.information.whatData: Describe what (kind of) data is processed in the service, and pay specific attention to possible processing of personal data.
service.create.title: Add new service
service.edit.title: Edit service
mail.confirmation.publish_production.comment: Comments
mail.confirmation.publish_production.entity_id: EntityID
mail.confirmation.publish_production.entity_name_en: Entity name (en)
mail.confirmation.publish_production.service_name: Service name
mail.confirmation.publish_production.publish_date: Publish date
mail.confirmation.publish_production.team_id: Team id
mail.confirmation.publish_production.subject: 'Production connection has been requested (%entityId%)'
{'fraction_non_alphanumeric': 0.07491843557417328, 'fraction_numerical': 0.003745921778708664, 'mean_word_length': 5.571731074642668, 'pattern_counts': {'":': 0, '<': 167, '<?xml version=': 0, '>': 167, 'https://': 12, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '23599', 'n_tokens_mistral': 6547, 'n_tokens_neox': 6328, 'n_words': 2804}