Internationalization best practices - Revision history

Dspayne at 16:31, 15 May 2013

2013-05-15T16:31:31Z

← Older revision		Revision as of 16:31, 15 May 2013
Line 2:		Line 2:

	From a technical perspective, the scriptural mandate to take the gospel to all nations depends on our ability to create products that work for all nations. '''The goal of this project is to document internationalization (I18N) best practices for the designers, developers and testers engaged in creating technical solutions for the Church.''' Just click on the links to the right and begin helping to capture and document best practices. The outline is already there.		From a technical perspective, the scriptural mandate to take the gospel to all nations depends on our ability to create products that work for all nations. '''The goal of this project is to document internationalization (I18N) best practices for the designers, developers and testers engaged in creating technical solutions for the Church.''' Just click on the links to the right and begin helping to capture and document best practices. The outline is already there.

	It will help if you have some internationalization expertise in design, development, or QA. We're using [https://docs.google.com/spreadsheet/ccc?key=0ArlSWAUXOyMedFd5VWxuOWh5cnZaZTctVmg3a19tVWc <u>this spreadsheet</u>] to track our progress.

Dspayne at 22:01, 3 April 2012

2012-04-03T22:01:20Z

← Older revision		Revision as of 22:01, 3 April 2012
Line 1:		Line 1:
	{{internationalization}}Welcome!		{{internationalization}}Welcome!

	From a technical perspective, the scriptural mandate to take the gospel to all nations depends on our ability to create products that work for all nations. '''The goal of this project is to document internationalization (I18N) best practices for the designers, developers and testers engaged in creating technical solutions for the Church.''' Just click on the links to the right and begin helping to capture and document best practices. The ~~skeleton~~ is already there.		From a technical perspective, the scriptural mandate to take the gospel to all nations depends on our ability to create products that work for all nations. '''The goal of this project is to document internationalization (I18N) best practices for the designers, developers and testers engaged in creating technical solutions for the Church.''' Just click on the links to the right and begin helping to capture and document best practices. The outline is already there.

	It will help if you have some internationalization expertise in design, development, or QA. We're using [https://docs.google.com/spreadsheet/ccc?key=0ArlSWAUXOyMedFd5VWxuOWh5cnZaZTctVmg3a19tVWc <u>this spreadsheet</u>] to track our progress.		It will help if you have some internationalization expertise in design, development, or QA. We're using [https://docs.google.com/spreadsheet/ccc?key=0ArlSWAUXOyMedFd5VWxuOWh5cnZaZTctVmg3a19tVWc <u>this spreadsheet</u>] to track our progress.

Dspayne at 16:50, 3 April 2012

2012-04-03T16:50:21Z

← Older revision		Revision as of 16:50, 3 April 2012
Line 1:		Line 1:
	{{internationalization}}From a technical perspective, the scriptural mandate to take the gospel to all nations depends on our ability to create products with appropriate linguistic and cultural support. This project will work to prioritize and document internationalization (I18N) best practices for the designers, developers and testers engaged in creating technical solutions for the Church. Just click on the links to the right and begin helping to capture and document best practices. The skeleton is already there.		{{internationalization}}Welcome!

	~~For~~ the ~~2012 LDSTECH Conference~~, up to ~~5 participants are invited~~ to ~~help~~. ~~You~~ will ~~need to~~ have some internationalization expertise in design, development, or QA. We'~~ll use~~ [https://docs.google.com/spreadsheet/ccc?key=0ArlSWAUXOyMedFd5VWxuOWh5cnZaZTctVmg3a19tVWc this spreadsheet] to track our progress.		From a technical perspective, the scriptural mandate to take the gospel to all nations depends on our ability to create products that work for all nations. '''The goal of this project is to document internationalization (I18N) best practices for the designers, developers and testers engaged in creating technical solutions for the Church.''' Just click on the links to the right and begin helping to capture and document best practices. The skeleton is already there.

			It will help if you have some internationalization expertise in design, development, or QA. We're using [https://docs.google.com/spreadsheet/ccc?key=0ArlSWAUXOyMedFd5VWxuOWh5cnZaZTctVmg3a19tVWc <u>this spreadsheet</u>] to track our progress.

Dspayne at 16:30, 29 March 2012

2012-03-29T16:30:23Z

← Older revision		Revision as of 16:30, 29 March 2012
Line 1:		Line 1:
	{{internationalization}}From a technical perspective, the scriptural mandate to take the gospel to all nations depends on our ability to create products with appropriate linguistic and cultural support. This project will work to prioritize and document internationalization (I18N) best practices for the designers, developers and testers engaged in creating technical solutions for the Church. Just click on the links to the right and begin helping to capture and document best practices. The skeleton is already there.		{{internationalization}}From a technical perspective, the scriptural mandate to take the gospel to all nations depends on our ability to create products with appropriate linguistic and cultural support. This project will work to prioritize and document internationalization (I18N) best practices for the designers, developers and testers engaged in creating technical solutions for the Church. Just click on the links to the right and begin helping to capture and document best practices. The skeleton is already there.

	For the 2012 ~~LDSTech~~ Conference, up to 5 participants are invited to help. You will need to have some internationalization expertise in design, development, or QA. We'll use [https://docs.google.com/spreadsheet/ccc?key=0ArlSWAUXOyMedFd5VWxuOWh5cnZaZTctVmg3a19tVWc this spreadsheet] to track our progress.		For the 2012 LDSTECH Conference, up to 5 participants are invited to help. You will need to have some internationalization expertise in design, development, or QA. We'll use [https://docs.google.com/spreadsheet/ccc?key=0ArlSWAUXOyMedFd5VWxuOWh5cnZaZTctVmg3a19tVWc this spreadsheet] to track our progress.

Dspayne at 16:18, 29 March 2012

2012-03-29T16:18:47Z

← Older revision		Revision as of 16:18, 29 March 2012
Line 1:		Line 1:
	{{internationalization}}From a technical perspective, the scriptural mandate to take the gospel to all nations depends on our ability to create products with appropriate linguistic and cultural support. This project will work to prioritize and document internationalization (I18N) best practices for the designers, developers and testers engaged in creating technical solutions for the Church. Just click on the links to the right and begin helping to capture and document best practices. The skeleton is already there.		{{internationalization}}From a technical perspective, the scriptural mandate to take the gospel to all nations depends on our ability to create products with appropriate linguistic and cultural support. This project will work to prioritize and document internationalization (I18N) best practices for the designers, developers and testers engaged in creating technical solutions for the Church. Just click on the links to the right and begin helping to capture and document best practices. The skeleton is already there.

	For the 2012 LDSTech Conference, up to 5 participants are invited to help. You will need to have some internationalization expertise in design, development, or QA.		For the 2012 LDSTech Conference, up to 5 participants are invited to help. You will need to have some internationalization expertise in design, development, or QA. We'll use [https://docs.google.com/spreadsheet/ccc?key=0ArlSWAUXOyMedFd5VWxuOWh5cnZaZTctVmg3a19tVWc this spreadsheet] to track our progress.

Dspayne at 20:13, 28 March 2012

2012-03-28T20:13:36Z

← Older revision		Revision as of 20:13, 28 March 2012
Line 1:		Line 1:
	{{internationalization}}From a technical perspective, the scriptural mandate to take the gospel to all nations depends on our ability to create products with appropriate linguistic and cultural support. ~~Starting with a vision statement, principles, and a list of potential practices, this~~ project will work to prioritize and document internationalization (I18N) ~~and localizability~~ best practices for the designers, developers and testers engaged in creating technical solutions for the Church. ~~Participants (~~up to 5~~) should~~ have internationalization expertise in design, development, or QA.		{{internationalization}}From a technical perspective, the scriptural mandate to take the gospel to all nations depends on our ability to create products with appropriate linguistic and cultural support. This project will work to prioritize and document internationalization (I18N) best practices for the designers, developers and testers engaged in creating technical solutions for the Church. Just click on the links to the right and begin helping to capture and document best practices. The skeleton is already there.

			For the 2012 LDSTech Conference, up to 5 participants are invited to help. You will need to have some internationalization expertise in design, development, or QA.

Johnsonth: added template

2012-03-27T19:41:14Z

added template

← Older revision		Revision as of 19:41, 27 March 2012
Line 1:		Line 1:
	From a technical perspective, the scriptural mandate to take the gospel to all nations depends on our ability to create products with appropriate linguistic and cultural support. Starting with a vision statement, principles, and a list of potential practices, this project will work to prioritize and document internationalization (I18N) and localizability best practices for the designers, developers and testers engaged in creating technical solutions for the Church. Participants (up to 5) should have internationalization expertise in design, development, or QA.		{{internationalization}}From a technical perspective, the scriptural mandate to take the gospel to all nations depends on our ability to create products with appropriate linguistic and cultural support. Starting with a vision statement, principles, and a list of potential practices, this project will work to prioritize and document internationalization (I18N) and localizability best practices for the designers, developers and testers engaged in creating technical solutions for the Church. Participants (up to 5) should have internationalization expertise in design, development, or QA.

Johnsonth: added description

2012-03-27T19:40:58Z

added description

← Older revision		Revision as of 19:40, 27 March 2012
Line 1:		Line 1:
	~~Content coming~~		From a technical perspective, the scriptural mandate to take the gospel to all nations depends on our ability to create products with appropriate linguistic and cultural support. Starting with a vision statement, principles, and a list of potential practices, this project will work to prioritize and document internationalization (I18N) and localizability best practices for the designers, developers and testers engaged in creating technical solutions for the Church. Participants (up to 5) should have internationalization expertise in design, development, or QA.

Johnsonth: moved Internationalization guidelines to Internationalization best practices: project manager was asked to use "best practices" instead of "guidelines"

2012-03-27T18:56:04Z

moved Internationalization guidelines to Internationalization best practices: project manager was asked to use "best practices" instead of "guidelines"

← Older revision	Revision as of 18:56, 27 March 2012
(No difference)

Dspayne: Created page with 'Content coming'

2012-03-26T21:14:14Z

Created page with 'Content coming'

New page

Content coming