SAFETAG - Revision history

Ariel at 15:40, 23 September 2025

2025-09-23T15:40:38Z

← Older revision		Revision as of 15:40, 23 September 2025
Line 31:		Line 31:

	Languages that are sufficiently translated need to be manually switched on. Coordinate with Localization Lab or email info@safetag.org to plan to have new language versions enabled publicly.		Languages that are sufficiently translated need to be manually switched on. Coordinate with Localization Lab or email info@safetag.org to plan to have new language versions enabled publicly.

	If these priority resources reach the 50% threshold in a certain language, it will be eligible for release.		If these priority resources reach the 50% threshold in a certain language, it will be eligible for release.

Ariel at 15:40, 23 September 2025

2025-09-23T15:40:22Z

← Older revision		Revision as of 15:40, 23 September 2025
Line 31:		Line 31:

	Languages that are sufficiently translated need to be manually switched on. Coordinate with Localization Lab or email info@safetag.org to plan to have new language versions enabled publicly.		Languages that are sufficiently translated need to be manually switched on. Coordinate with Localization Lab or email info@safetag.org to plan to have new language versions enabled publicly.
			If these priority resources reach the 50% threshold in a certain language, it will be eligible for release.

	'''Retain the markdown in the original strings:'''		'''Retain the markdown in the original strings:'''

Ariel at 15:37, 23 September 2025

2025-09-23T15:37:24Z

@@ Line 21: / Line 21: @@
 '''Do not translate the following terms:'''
 * SAFETAG
 '''Retain the markdown in the original strings:'''

Ariel: /* Translation Guidelines */

2024-07-12T11:07:34Z

Translation Guidelines

← Older revision		Revision as of 11:07, 12 July 2024
Line 37:		Line 37:

	:Anyone can add to or change the glossary however, so the terms listed are not always 100% vetted. If you have doubts or disagree with a term, consult with other contributors to solidify the translation.		:Anyone can add to or change the glossary however, so the terms listed are not always 100% vetted. If you have doubts or disagree with a term, consult with other contributors to solidify the translation.
	* '''Use the "tags" filter.''' Use the "tags" filter in the Transifex editor to exclude strings that don't need to be translated ("notranslate" tag) or to filter by section of the SAFETAG guide (ex: "introduction")		* '''Use the "tags" filter.''' Use the "tags" filter in the Transifex editor to exclude strings that don't need to be translated ("notranslate" tag) or to filter by section of the SAFETAG guide (e.g.: "introduction")

	==Style Guidelines==		==Style Guidelines==

Ariel: /* About */

2024-07-12T11:05:25Z

About

← Older revision		Revision as of 11:05, 12 July 2024
Line 7:		Line 7:
	<br>		<br>
	:'''What does it do?'''<br>		:'''What does it do?'''<br>
	:"SAFETAG is based upon a set of principles, activities, and best practices to allow digital security auditors to best support at-risk organizations by working with them to '''''identify the risks they face, the next steps they need to take to address them, and guidance on how to seek out support in the future.'''''"		:SAFETAG is based upon a set of principles, activities, and best practices to allow digital security auditors to best support at-risk organizations by working with them to '''''identify the risks they face, the next steps they need to take to address them, and guidance on how to seek out support in the future.'''''
	<br>		<br>
	:'''Who is it for?'''<br>		:'''Who is it for?'''<br>
	:"SAFETAG audits are targeted at serving '''''small scale civil society organizations or independent media houses''''' who have strong digital security concerns but do not have the funds to afford a traditional digital security audit. The traditional security-audit framework is based upon the assumption that an organization has the time, money, and capacity to aim for as close to perfect security as possible. Low-income at-risk groups have none of these luxuries. These audits are both far too expensive, and often produce output that is too complex for these organizations to act upon."		:SAFETAG audits are targeted at serving '''''small scale civil society organizations or independent media houses''''' who have strong digital security concerns but do not have the funds to afford a traditional digital security audit. The traditional security-audit framework is based upon the assumption that an organization has the time, money, and capacity to aim for as close to perfect security as possible. Low-income at-risk groups have none of these luxuries. These audits are both far too expensive, and often produce output that is too complex for these organizations to act upon.
	<br>		<br>
	'''Website:''' https://safetag.org/<br>		'''Website:''' https://safetag.org/<br>
	'''Contributing:''' SAFETAG welcomes community contribution. Edits and new content can be submitted using the CMS at https://safetag.org/admin (sign in with a GitHub account). For general discussion about SAFETAG or to discuss edits or new content or to join the SAFETAG Slack reach out to info [at] safetag.org. <br>		'''Contributing:''' SAFETAG welcomes community contribution. Edits and new content can be submitted using the CMS at https://safetag.org/admin (sign in with a GitHub account). For general discussion about SAFETAG or to discuss edits or new content or to join the SAFETAG Slack reach out to info [at] safetag.org. <br>


	=[https://www.transifex.com/otf/safetag-overview/dashboard/ Translate SAFETAG]=		=[https://www.transifex.com/otf/safetag-overview/dashboard/ Translate SAFETAG]=

Ariel at 11:04, 12 July 2024

2024-07-12T11:04:38Z

← Older revision		Revision as of 11:04, 12 July 2024
Line 3:		Line 3:
	=About=		=About=
	<div style="float:left; margin-right:1.0em">[[File:SAFETAG.png\|75px\|center\|SAFETAG Logo]]</div>		<div style="float:left; margin-right:1.0em">[[File:SAFETAG.png\|75px\|center\|SAFETAG Logo]]</div>
	"The '''''Security Auditing Framework and Evaluation Template for Advocacy Groups (SAFETAG)''''' is a professional audit framework that adapts traditional penetration testing and risk assessment methodologies to be relevant to small, non-profit, human rights organizations ~~based or operating in the developing world~~."		The '''''Security Auditing Framework and Evaluation Template for Advocacy Groups (SAFETAG)''''' is a professional audit framework that adapts traditional penetration testing and risk assessment methodologies to be relevant to small/medium, non-profit, human rights or independent media organizations.
	<br>		<br>
	<br>		<br>
Line 10:		Line 10:
	<br>		<br>
	:'''Who is it for?'''<br>		:'''Who is it for?'''<br>
	:"SAFETAG audits are targeted at serving '''''small scale civil society organizations or independent media houses''''' who have strong digital security concerns but do not have the funds to afford a traditional digital security audit. The traditional security-audit framework is based upon the assumption that an organization has the time, money, and capacity to aim for as close to perfect security as possible. Low-income at-risk groups have none of these luxuries. These audits are both far too expensive, and produce output that is too complex for these organizations to act upon."		:"SAFETAG audits are targeted at serving '''''small scale civil society organizations or independent media houses''''' who have strong digital security concerns but do not have the funds to afford a traditional digital security audit. The traditional security-audit framework is based upon the assumption that an organization has the time, money, and capacity to aim for as close to perfect security as possible. Low-income at-risk groups have none of these luxuries. These audits are both far too expensive, and often produce output that is too complex for these organizations to act upon."
	<br>		<br>
	'''Website:''' https://safetag.org/<br>		'''Website:''' https://safetag.org/<br>
	'''~~Read/Download SAFETAG~~:''' SAFETAG ~~Overview ([~~https://~~github~~.~~com~~/~~SAFETAG/SAFETAG/releases/download/v0~~.4/SAFETAG~~.Overview.English.pdf PDF]),~~ SAFETAG ~~Full Guide (~~[~~https://~~safetag.org~~/index~~.~~html#process PDF])~~		'''Contributing:''' SAFETAG welcomes community contribution. Edits and new content can be submitted using the CMS at https://safetag.org/admin (sign in with a GitHub account). For general discussion about SAFETAG or to discuss edits or new content or to join the SAFETAG Slack reach out to info [at] safetag.org. <br>


	=[https://www.transifex.com/otf/safetag-overview/dashboard/ Translate SAFETAG]=		=[https://www.transifex.com/otf/safetag-overview/dashboard/ Translate SAFETAG]=
Line 49:		Line 50:
	For example, in English the use of the singular "they" as a replacement for "he" and "she" is now widely accepted.		For example, in English the use of the singular "they" as a replacement for "he" and "she" is now widely accepted.

	If there are realistic gender neutral options that you can use, please consider using them in this translation. You can contact [mailto:~~erinm~~@localizationlab.org ~~erinm~~] to be put in touch with other translators working on the guide in your language so that you can gain consensus as a group.		If there are realistic gender neutral options that you can use, please consider using them in this translation. You can contact [mailto:maja@localizationlab.org Maja] to be put in touch with other translators working on the guide in your language so that you can gain consensus as a group.

	=Localization References=		=Localization References=

	=Contact=		=Contact=
	If you are interested in working on this project, please contact ~~[mailto:erinm@localizationlab.org erinm]~~ directly so that you can be put in touch with other contributors to the project.		If you are interested in working on this project, please contact Localization Lab directly so that you can be put in touch with other contributors to the project.

Erin: /* Translation Guidelines */

2018-12-12T12:31:34Z

Translation Guidelines

← Older revision		Revision as of 12:31, 12 December 2018
Line 37:		Line 37:

	:Anyone can add to or change the glossary however, so the terms listed are not always 100% vetted. If you have doubts or disagree with a term, consult with other contributors to solidify the translation.		:Anyone can add to or change the glossary however, so the terms listed are not always 100% vetted. If you have doubts or disagree with a term, consult with other contributors to solidify the translation.
			* '''Use the "tags" filter.''' Use the "tags" filter in the Transifex editor to exclude strings that don't need to be translated ("notranslate" tag) or to filter by section of the SAFETAG guide (ex: "introduction")

	==Style Guidelines==		==Style Guidelines==

Erin: /* Translation Guidelines */

2018-12-12T12:29:58Z

Translation Guidelines

← Older revision		Revision as of 12:29, 12 December 2018
Line 31:		Line 31:

	'''Helpful Tips:'''		'''Helpful Tips:'''
	* '''Use the "Concordance" Search.''' The concordance search allows you to search for terms and phrases across all of the projects in the Localization Lab Hub. For example, if you need to translate the title of a chapter in the SAFETAG guide, you will want to make sure the translation you use is exactly the same in every instance. Searching the title in the Concordance search will pull up every instance of that title in the project for you to reference.		* '''Use the "Concordance" Search.''' The concordance search allows you to search for terms and phrases across all of the projects in the Localization Lab Hub.
	* '''Use the Glossary.''' Reference the glossary and add to it to ensure the same terms are being used across the entire project. Anyone can add to or change the glossary however, so the terms listed are not always 100% vetted. If you have doubts or disagree with a term, consult with other contributors to solidify the translation.
			:For example, if you need to translate the title of a chapter in the SAFETAG guide, you will want to make sure the translation you use is exactly the same in every instance. Searching the title in the Concordance search will pull up every instance of that title in the project for you to reference.
			* '''Use the Glossary.''' Reference the glossary and add to it to ensure the same terms are being used across the entire project.

			:Anyone can add to or change the glossary however, so the terms listed are not always 100% vetted. If you have doubts or disagree with a term, consult with other contributors to solidify the translation.

	==Style Guidelines==		==Style Guidelines==

Erin: /* Translation Guidelines */

2018-12-12T12:29:10Z

Translation Guidelines

← Older revision		Revision as of 12:29, 12 December 2018
Line 29:		Line 29:
	* <span style="color:#FF009F">'''![...](...)'''</span> is replaced by an image in markdown. Copy the full string and only translate the image alt text, the contents of the square brackets '[...]'		* <span style="color:#FF009F">'''![...](...)'''</span> is replaced by an image in markdown. Copy the full string and only translate the image alt text, the contents of the square brackets '[...]'
	* <span style="color:#FF009F">'''^[^...]'''</span> creates a footnote in markdown. Do not change the carrots, square brackets or edit the contents within the square brackets.		* <span style="color:#FF009F">'''^[^...]'''</span> creates a footnote in markdown. Do not change the carrots, square brackets or edit the contents within the square brackets.

			'''Helpful Tips:'''
			* '''Use the "Concordance" Search.''' The concordance search allows you to search for terms and phrases across all of the projects in the Localization Lab Hub. For example, if you need to translate the title of a chapter in the SAFETAG guide, you will want to make sure the translation you use is exactly the same in every instance. Searching the title in the Concordance search will pull up every instance of that title in the project for you to reference.
			* '''Use the Glossary.''' Reference the glossary and add to it to ensure the same terms are being used across the entire project. Anyone can add to or change the glossary however, so the terms listed are not always 100% vetted. If you have doubts or disagree with a term, consult with other contributors to solidify the translation.

	==Style Guidelines==		==Style Guidelines==

Erin: /* Contact */ Added contact note

2018-12-12T12:22:56Z

Contact: Added contact note

← Older revision		Revision as of 12:22, 12 December 2018
Line 45:		Line 45:

	=Contact=		=Contact=
			If you are interested in working on this project, please contact [mailto:erinm@localizationlab.org erinm] directly so that you can be put in touch with other contributors to the project.