Translate Toolkit & Pootle pootle

pootle:adding_a_terminology_project

Fri, 13 Feb 2009 11:25:05 +0000

1189426649		current
Line 1:		Line 1:

-	Pootle can perform real-time semi-fuzzy look-up in a glossary created by the project manager. This glossary is a standard PO file with a specific name. The naming format is "<project>-terminology.po". Pootle recognises this file automatically, if it exists. In the absence of a project-specific glossary, a project will query the glossary named "pootle-terminology.po", if it exists.	+	Pootle can perform real-time semi-fuzzy look-up in a glossary created by the project manager. This glossary is a standard PO file with a specific name. The file must be called "pootle-terminology.po". Pootle recognises this file automatically, if it exists. In the absence of a project-specific glossary, a project will query all files in the project called "terminology", if it exists.

-	Ideally, the source term should be the shortest, simplest form of a word. Therefore cat, dog, house are good, but cats, dogged and housing are bad. Context indicators are allowed in the source text, in brackets after the term, but keep them short, eg (noun), (verb), etc.	+	Ideally, the source term should be the shortest, simplest form of a word. Therefore cat, dog, house are good, but cats, dogged and housing are bad. Context indicators are allowed in the source text, in brackets after the term, but keep them short, eg. (noun), (verb), etc.

-	The latest version of Pootle has the ability to insert the target term into the text. The ideal is therefore that the target term be something that you'd like the translator to be able to insert... but strictly speaking the target text can be anything, including an definition.	+	The latest version of Pootle has the ability to insert the target term into the text. The ideal is therefore that the target term be something that you'd like the translator to be able to insert... but strictly speaking the target text can be anything, including a definition.

-	If the PO file has comments, it will be displayed as a tooltip in Pootle, but the glossary format wasn't really designed for supporting glossary comments.	+	If the PO file has comments, it will be displayed as a tooltip in Pootle.

pootle:admin_account

Wed, 18 Nov 2009 11:29:04 +0000

1156755146		current
Line 1:		Line 1:
	====== Pootle administrator account ======		====== Pootle administrator account ======
-	In the default installation, Pootle does not have any user or administrator accounts defined. To enable the first site administrator, edit your users.prefs file to include a line
-	rights.siteadmin = True
-	for a user that exists. You can uncomment the example there, or add the administrator line to an existing user. Please note that leaving the example user enabled will compromise your Pootle setup, since the password is predictable. That is why it is best to add that line to a user account that already exists on your server. If you don't yet have a registered user, you can simply create one similarly to the example. If you have a registered user who's account is not yet activated, set the "activated" field to "1" to activate the user. Remember to restart the server for manual changes to the preference files to take effect.

		+	In default Pootle installations, an ''admin'' account (the password matches the username) is created with superuser privileges which can be used to administer the whole site.
		+
		+	<note>It's highly recommended that you change the password for the default ''admin'' account on your first login, or even delete the account and assign superuser rights to another user.</note>
		+
		+	===== Administration scope =====
		+
		+	Users with administration privileges will have an extra ''Administrate'' element within the main navigation bar, which gives direct access to the administration functions of the site.
		+
		+	Administrators can change the general settings for the site (such as the server title or description), as well as add, edit, and remove users, languages, and translation projects. They are also able to define the default permissions that will apply to the whole site unless otherwise noted.
		+
		+	Apart from that, administrators have full rights over all the translation projects, so they can do whatever can be done: translate, suggest, upload new files, update VCS checkouts, ...
		+
		+	===== Adding new site administrators =====
		+
		+	If you want to assign site administration permissions to an already existing user, just go to the ''Users'' tab within the ''Administration'' page, check the ''Superuser status'' checkbox for the user you want to make administrator and click on ''Save Changes''. That's all!

pootle:admin_guide

Mon, 28 Aug 2006 08:32:27 +0000

	current
Line 1:	Line 1:
	+	====== Pootle administration ======
	+	* [[admin_account\|Creating the administrator]]
	+	* [[permissions\|Assigning permissions]]

pootle:alternative_source_language

Tue, 17 Nov 2009 09:47:06 +0000

1258450993		current
Line 5:		Line 5:
	Pootle has the ability to display alternative source languages while translating. Thus, translators who know another language better than English can take part in the translation project. Also, it provides a way to dissambiguate terminology seeing how other languages have translated the same translation unit.		Pootle has the ability to display alternative source languages while translating. Thus, translators who know another language better than English can take part in the translation project. Also, it provides a way to dissambiguate terminology seeing how other languages have translated the same translation unit.

-	{{:pootle:pootle_altsrc.jpg?580\|Pootle displaying Catalan and Spanish as alternative source languages while translating into Basque.}}	+	{{:pootle:pootle_altsrc.png?580\|Pootle displaying Catalan and Spanish as alternative source languages while translating into Basque.}}

	===== Setup =====		===== Setup =====

pootle:apache

Fri, 20 Nov 2009 01:04:08 +0000

1258678871		current
Line 13:		Line 13:
	==== mod_wsgi ====		==== mod_wsgi ====
	<code>		<code>
		+	# point at the wsgi loader script
	WSGIScriptAlias /pootle /var/www/Pootle/wsgi.py		WSGIScriptAlias /pootle /var/www/Pootle/wsgi.py

		+	# directly serve static files like css and images, no need to go through mod_wsgi and django
	Alias /pootle/html /var/www/Pootle/html		Alias /pootle/html /var/www/Pootle/html
	<Directory /var/www/Pootle/html>		<Directory /var/www/Pootle/html>
Line 20:		Line 22:
	Allow from all		Allow from all
	</Directory>		</Directory>
-	</code>

-	[[http://docs.djangoproject.com/en/1.0/howto/deployment/modwsgi/\|more info]]	+	# Allow downloading translation files directly
		+	Alias /pootle/export /var/www/Pootle/po
		+	<Directory /var/www/Pootle/po>
		+	Order deny,allow
		+	Allow from all
		+	</Directory>
		+	</code>
		+	[[http://docs.djangoproject.com/en/dev/howto/deployment/modwsgi/\|more info]]

	==== mod_python ====		==== mod_python ====

pootle:assigning

Tue, 17 Nov 2009 16:03:53 +0000

1230644437		current
Line 1:		Line 1:
	====== Assigning ======		====== Assigning ======
		+
		+	<note>This information is about an old Pootle version. Pootle 2.0 doesn't have assigning functionality but it may be added in the future.</note>

	When different team members want to work on the same project, Pootle allows the project administrator to assign work to different people. Different files from the same project can be assigned, or even a single file can be split between different people.		When different team members want to work on the same project, Pootle allows the project administrator to assign work to different people. Different files from the same project can be assigned, or even a single file can be split between different people.

pootle:cachdung

Sat, 05 Jan 2008 18:09:47 +0000

1205138831		current
Line 7:		Line 7:
	==== Đăng ký ====		==== Đăng ký ====

-	8-) Người dùng mới cần [[http://pootle.wordforge.org/register.html\|đăng ký]] với Pootle	+	8-) Người dùng mới cần [[http://pootle.locamotion.org/register.html\|đăng ký]] với Pootle

	Bạn sẽ nhận thư chứa mã kích hoạt: chỉ cần nhấn vào liên kết trong thư, rồi nhập mã (thủ tục này chặn việc đăng lý rác). Nếu bạn gặp khó khăn nào trong việc đăng ký, bạn viết thư cho [[Translate-pootle@lists.sourceforge.net\|hộp thư chung Pootle]] (đăng ký ở [[https://lists.sourceforge.net/lists/listinfo/translate-pootle\|trang này]]) hoặc cho tôi <clytie@riverland.net.au>.		Bạn sẽ nhận thư chứa mã kích hoạt: chỉ cần nhấn vào liên kết trong thư, rồi nhập mã (thủ tục này chặn việc đăng lý rác). Nếu bạn gặp khó khăn nào trong việc đăng ký, bạn viết thư cho [[Translate-pootle@lists.sourceforge.net\|hộp thư chung Pootle]] (đăng ký ở [[https://lists.sourceforge.net/lists/listinfo/translate-pootle\|trang này]]) hoặc cho tôi <clytie@riverland.net.au>.

pootle:characters

Mon, 28 May 2007 17:58:13 +0000

1158822468		current
Line 1:		Line 1:
	====== Special characters ======		====== Special characters ======
-	Since version 0.10.1, Pootle can display clickable characters to help people insert characters which might be difficult to type. Earlier Pootle versions only displayed the special characters. This page allows people to specify which characters might be useful for translators.	+
		+	Pootle can display clickable characters to help people insert characters which might be difficult to type. Earlier Pootle versions only displayed the special characters. This page allows people to specify which characters might be useful for translators.

	For many languages this does not really help much, but we realise that many languages using the Latin alphabet with diacritics, this could help a lot. Well supported languages like French fall in this category, I guess that most French users probably have no input problems in general. If you think that this feature could help some members of your community on some pootle servers, you can also include your requests here.		For many languages this does not really help much, but we realise that many languages using the Latin alphabet with diacritics, this could help a lot. Well supported languages like French fall in this category, I guess that most French users probably have no input problems in general. If you think that this feature could help some members of your community on some pootle servers, you can also include your requests here.
Line 37:		Line 38:
	You could prioritize by excluding the characters covered by the Latin-1 codeset, which are available via most standard keyboards.		You could prioritize by excluding the characters covered by the Latin-1 codeset, which are available via most standard keyboards.
	Since Vietnamese is mostly composed of accented vowels as above, the priority should be to help users acquire the appropriate input systems and keyboard layouts. Relying on clicking each character from a palette would slow down translation severely. However, it would make translation possible in the short term for those who can't yet input our language, or for those accessing computers which for some reason won't use the correct input software.		Since Vietnamese is mostly composed of accented vowels as above, the priority should be to help users acquire the appropriate input systems and keyboard layouts. Relying on clicking each character from a palette would slow down translation severely. However, it would make translation possible in the short term for those who can't yet input our language, or for those accessing computers which for some reason won't use the correct input software.
-
-

pootle:checks

Tue, 17 Nov 2009 09:51:57 +0000

1258451450		current
Line 7:		Line 7:
	To review the quality checks you need to have translation rights for the project. To find the results, click on the "Review" tab. Clicking on the name of a test will step you through the translations that fail the test.		To review the quality checks you need to have translation rights for the project. To find the results, click on the "Review" tab. Clicking on the name of a test will step you through the translations that fail the test.

-	To understand the meaning of each test, read the detailed descriptions the [[toolkit:pofilter tests]].	+	To understand the meaning of each test, Pootle displays the running tests on the top-right corner of the translation page with a link to the online documentation. You can also read the detailed descriptions of the [[toolkit:pofilter tests]].

pootle:configure_version_control_authentication

Sat, 26 Jan 2008 21:24:32 +0000

1168817037		current
Line 22:		Line 22:
	- make sure, that the //pootle// user has write access for //~/.subversion/// to store authentication tokens		- make sure, that the //pootle// user has write access for //~/.subversion/// to store authentication tokens
	- do a real //svn commit// with the uid //pootle// in order to:		- do a real //svn commit// with the uid //pootle// in order to:
-	* (possibly) import an SSL certificate	+	* (possibly) import an SSL certificate
-	* store the username and password in the subversion authentication cache (by default, the option //store-passwords// is enabled in //~/.subversion/config//)	+	* store the username and password in the subversion authentication cache (by default, the option //store-passwords// is enabled in //~/.subversion/config//)
		+	- If you start Pootle from an init script, make sure that all necessary environment variables are set. $HOME will be needed to obtain your cached authentication information, for example.

	From now on, //pootle// should use these stored access credentials when uploading commits for this repository.		From now on, //pootle// should use these stored access credentials when uploading commits for this repository.

pootle:copyright

Tue, 19 Jun 2007 12:17:13 +0000

1154433226		current
Line 1:		Line 1:
	====== Copyright ======		====== Copyright ======

-	Pootle documentation (everything which is included with Pootle software and/or is under the pootle/ namespace on the wiki) is released under the [[http://www.gnu.org/licenses/gpl.html\|GNU General Public License]] (GPL).	+	Pootle documentation (everything which is included with Pootle software or is under the pootle/ namespace on the wiki) is released under the [[http://www.gnu.org/licenses/gpl.html\|GNU General Public License]] (GPL).

pootle:developer_guide

Fri, 12 Dec 2008 10:41:20 +0000

1224602227		current
Line 1:		Line 1:
	====== Pootle developer guide ======		====== Pootle developer guide ======
		+
		+	<note warning>The current trunk version of Pootle is unstable,
		+	since we are in the process of porting Pootle to Django. If you are interested in helping, consult [[developers:The Great Pootle Migration]].</note>
		+
	This is a collection of links and pages for people interested in Pootle development. People interested in development or related issues will want to join our mailing lists. Translate-devel is the development mailing list (more geared towards the toolkit) and translate-pootle is more geared towards Pootle users and Pootle related issues.		This is a collection of links and pages for people interested in Pootle development. People interested in development or related issues will want to join our mailing lists. Translate-devel is the development mailing list (more geared towards the toolkit) and translate-pootle is more geared towards Pootle users and Pootle related issues.

pootle:django_migration

Fri, 12 Dec 2008 11:09:42 +0000

1199555889		current
Line 1:		Line 1:
	If you change this page, pleas notify me on IRC (hruske), or better yet, write your comments in mail and I'll add them here. (Zejn)		If you change this page, pleas notify me on IRC (hruske), or better yet, write your comments in mail and I'll add them here. (Zejn)
		+
		+	<note warning>The information on this page is kept for historical
		+	interest. Pootle is in the process of being ported to Django. See
		+	[[developers:The Great Pootle Migration]].</note>

	====== Django migration ======		====== Django migration ======

pootle:features

Wed, 18 Nov 2009 12:15:17 +0000

1258546380		current
Line 16:		Line 16:
	* Authentication using LDAP is possible.		* Authentication using LDAP is possible.
	* In [[suggestions\|suggestion mode]] contributions can be checked by competent translators before being accepted, ideal for bug reporting		* In [[suggestions\|suggestion mode]] contributions can be checked by competent translators before being accepted, ideal for bug reporting
-	* Teams can set [[goals]] (not available in version 2.0)
-	* [[assigning\|Assign work]] to various translators (not available in version 2.0)
	* [[permissions\|Assign permissions]] to various translators to perform different functions		* [[permissions\|Assign permissions]] to various translators to perform different functions
	* Uses Unicode throughout so will work with any target language		* Uses Unicode throughout so will work with any target language
		+	* <del>Teams can set [[goals]]</del> (not available in version 2.0)
		+	* <del>[[assigning\|Assign work]] to various translators</del> (not available in version 2.0)
	* Editor		* Editor
	* A web-based translation editor means you can translate anywhere online		* A web-based translation editor means you can translate anywhere online
Line 33:		Line 33:
	* Can use suggestions from a translation memory. See [[updatetm]].		* Can use suggestions from a translation memory. See [[updatetm]].
	* Clickable [[characters]] to help users who can't type all the characters of their languages		* Clickable [[characters]] to help users who can't type all the characters of their languages
-	* Enables translators to use an [[alternative source language]] while translating. (from version 1.2)	+	* Enables translators to use [[alternative source language]]s while translating.

	==== Always Improving ====		==== Always Improving ====

	Pootle has been built on the contributions of the free-software translation community. We are [[:pootle/ui_ideas\|discussing]] how to improve the Pootle UI. Come and share your ideas!		Pootle has been built on the contributions of the free-software translation community. We are [[:pootle/ui_ideas\|discussing]] how to improve the Pootle UI. Come and share your ideas!

pootle:goals

Tue, 17 Nov 2009 16:04:50 +0000

1182581955		current
Line 1:		Line 1:
	====== Creating goals ======		====== Creating goals ======
		+
		+	<note>This information is about an old Pootle version. Pootle 2.0 doesn't have goals functionality but it may be added in the future.</note>
		+
	In a translation project in Pootle, you can create goals to organise and prioritise files. Creating goals is also necessary for [[assigning]] work to people.		In a translation project in Pootle, you can create goals to organise and prioritise files. Creating goals is also necessary for [[assigning]] work to people.

pootle:important_changes

Tue, 17 Nov 2009 14:52:53 +0000

1258469304		current
Line 11:		Line 11:

	===== 2.0 =====		===== 2.0 =====
-	* Pootle now uses the Django framework and data that previously was stored in flat files (projects, languages, users and permissions) is now stored in a database.	+	* Pootle now uses the Django framework and data that previously was stored in flat files (projects, languages, users and permissions) is now stored in a database. [[migration\|Migration]] scripts are provided.

	===== 1.2.0 =====		===== 1.2.0 =====

pootle:index

Thu, 19 Nov 2009 14:18:38 +0000

1258630860		current
Line 9:		Line 9:
	===== About Pootle =====		===== About Pootle =====

-	* [[What's in a name?]]
	* [[Features]]		* [[Features]]
		+	* [[What's in a name?]]
	* [[Copyright]]		* [[Copyright]]

pootle:indexing

Thu, 19 Nov 2009 21:03:42 +0000

1258628044		current
Line 4:		Line 4:

	For now the current indexing engines are supported:		For now the current indexing engines are supported:
-	* [[http://xapian.org\|Xapian]] (v1.0 or higher). Note that you need at least version 1.0.16 to run under Apache with mod_wsgi or mod_python.	+	* [[http://xapian.org\|Xapian]] (v1.0 or higher). Note that you need at least *[[http://svn.xapian.org/checkout/tags/1.0.13/xapian-bindings/NEWS\|*version 1.0.13]] to run under Apache with mod_wsgi or mod_python.
	* [[http://lucene.apache.org/\|Lucene]]		* [[http://lucene.apache.org/\|Lucene]]

pootle:installation

Wed, 25 Nov 2009 08:39:25 +0000

1259138310		current
Line 1:		Line 1:
		+
		+	<note>This page refers to an old Pootle version. For those willing to try the latest version, please follow [[pootle/installation_1.3beta\|these installation instructions]].</note>
		+
	====== System requirements ======		====== System requirements ======

pootle:installation_1.3beta

Fri, 20 Nov 2009 00:55:28 +0000

1258678066		current
Line 70:		Line 70:
	By default ''setup.py'' will use the directory ''/var/lib/pootle'' for translation files, databases and other working files Pootle might use. The user running will need to have write permissions on this directory and all it's descendant files and subdirectories.		By default ''setup.py'' will use the directory ''/var/lib/pootle'' for translation files, databases and other working files Pootle might use. The user running will need to have write permissions on this directory and all it's descendant files and subdirectories.

-	==== Manually Setting up your database ====	+	==== Manually Updating Statistics ====

-	If Pootle complains about weird things, try deleting your database.	+	If you've made major changes to Pootle's translation files outside of pootle (from shell or version control) some statistics will be out of date, and visits to front page might be slow while it recalculates the stats.

-	Change your directory to //inside// your Pootle directory (that is, ''cd /my/installation/path/Pootle''). Now, execute the following commands:	+	To avoid this you can recalculate statistics and indexes for existing translation projects. it will detected deleted and new files as all.

-	First delete the existing database	+	PootleServer --refreshstats
-	rm ./dbs/pootle.db	+

-	Then initialize the database and build pootle tables, it'll ask you to create an admin account.	+	Might be a good idea to rerun the refresh_stats command after adding new translation projects.
-		+
-	./manage.py syncdb	+
-		+
-	Next load default Pootle data into the database, if no admin user was created at the syncdb step a default one will be created with username 'admin' and password 'admin'.	+
-		+
-	./manage.py initdb	+
-		+
-	Finally precalculate statistics and indexes for existing translation projects. This step is not strictly required, but without it Pootle will feel a bit sluggish and slow when visiting accessing a page for the first time.	+
-		+
-	./manage.py refresh_stats	+
-		+
-	Rerun the refresh_stats command after adding new translation projects.	+
-		+
-	The database is placed in the //dbs// subdirectory.	+

pootle:live_servers

Sat, 31 Oct 2009 13:59:32 +0000

1247682335		current
Line 105:		Line 105:
	* [[http://kondosyokai.org\|Kondo Syokai Group]]		* [[http://kondosyokai.org\|Kondo Syokai Group]]
	* [[http://translate.exb.de/\|ExB Communication Systems GmbH]]		* [[http://translate.exb.de/\|ExB Communication Systems GmbH]]
		+	* [[http://www.hitmeister.de\|Hitmeister]] - we are using Pootle to translate our public API documentation from German to English. Coming next - the whole website

	===== Temporary Pootle Servers =====		===== Temporary Pootle Servers =====

pootle:locking

Tue, 30 May 2006 13:50:38 +0000

1148654697		current
Line 30:		Line 30:
	=== recommended plan: ===		=== recommended plan: ===
	* <del>temporarily remove suggestions feature</del>		* <del>temporarily remove suggestions feature</del>
-	* find simpler more standard way to store stats (bdb? xml? simple database?)	+	* <del>separate out stats / assigns into separate interface</del> (may do more here)
		+	* find simpler more standard way to store stats (simple database)
	* find simpler more standard way to store assigns (as above)		* find simpler more standard way to store assigns (as above)
-	* separate out stats / assigns into separate interface?
	* add tests for concurrent access (maybe benchmarks too...)		* add tests for concurrent access (maybe benchmarks too...)
	* introduce generic pessimistic locking		* introduce generic pessimistic locking
Line 54:		Line 54:
	* write properties / methods		* write properties / methods
	* setunquotedmsgstr		* setunquotedmsgstr
		+
		+	== pootlestatistics ==
		+	* file system interaction
		+	* getstats - checks modtimes, calls readstats, readpendingfile, calcstats, savestats
		+	* readstats
		+	* savestats
		+	* update methods (no new data, just refresh)
		+	* reclassifyelement
		+	* reclassifysuggestions
		+
		+	== pootleassigns ==
		+	* file system interaction
		+	* getassigns / readassigns
		+	* saveassigns
		+	* write properties / methods
		+	* assignto
		+	* unassign

	== pootlefile ==		== pootlefile ==
Line 63:		Line 80:
	* readpendingfile		* readpendingfile
	* savependingfile		* savependingfile
-	* getstats - checks modtimes, calls readstats, readpendingfile, calcstats, savestats
-	* readstats
-	* savestats
-	* getassigns / readassigns
-	* saveassigns
	* read properties / methods		* read properties / methods
	* getoutput		* getoutput
	* getsuggestions		* getsuggestions
	* iteritems (updates stats)		* iteritems (updates stats)
-	* update methods (no new data, just refresh)
-	* reclassifyelement
-	* reclassifysuggestions
	* write properties / methods		* write properties / methods
-	* assignto
-	* unassign
	* setmsgstr		* setmsgstr
	* addsuggestion		* addsuggestion
Line 83:		Line 90:
	* mergeitem		* mergeitem
	* mergefile		* mergefile
-

pootle:logstats

Tue, 17 Nov 2009 16:12:19 +0000

1185548454		current
Line 1:		Line 1:
		+
		+	<note>This information is about an old Pootle version. Pootle 2.0 supports user contribution statistics so this is not needed anymore.</note>

	Here is a script that can analise a Pootle log file and print some basic statistics about the number of contributions each user has made.		Here is a script that can analise a Pootle log file and print some basic statistics about the number of contributions each user has made.

pootle:metadata

Fri, 09 Jun 2006 09:09:59 +0000

pootle:migration

Mon, 23 Nov 2009 11:52:30 +0000

1258635689		current
Line 32:		Line 32:

	Lastly, if your setup is fine, you can access Pootle using your web browser. Please note that the first time you try to access the main page Pootle needs to calculate all the stats so this may take some time. This only happens on the first time.		Lastly, if your setup is fine, you can access Pootle using your web browser. Please note that the first time you try to access the main page Pootle needs to calculate all the stats so this may take some time. This only happens on the first time.
		+
		+	<note>Once your migration is done, you can delete all the files ending with ''.prefs'' extension. Those files are not used anymore because that information now resides in the database.</note>

	===== Known issues =====		===== Known issues =====

pootle:news

Wed, 28 Oct 2009 09:17:36 +0000

	current
Line 1:	Line 1:
	+	====== News ======
	+	Since version 2, Pootle provides the ability to access useful information about your language and projects. These can be read on Pootle, or through your RSS reader.

	+	Project administrators can write notices, and Pootle will also generate entries automatically for these events:
	+
	+	* new languages
	+	* new projects
	+	* new projects added to languages
	+	* project updated from version control
	+	* project updated to templates
	+	* file committed to version control
	+	* file uploaded to project
	+	* archive uploaded to project
	+	* file reached 100%

pootle:nginx

Wed, 18 Nov 2009 11:52:05 +0000

1258544731		current
Line 1:		Line 1:
-	<note>This information is about an old Pootle version so it may not strictly apply to the current version of Pootle.</note>	+	<note>This information is about an old Pootle version and it may not strictly apply to the current version of Pootle.</note>

	A Pootle Web-translation server is made up of static and dynamic content. By default Pootle serves all content, for low-latency purposes it is better to get other webserver (like Apache, Lighttpd or Nginx in this example) to serve the content that does not change, the static content. It is just the issue of low latency and making the translation experience more interactive that calls you to proxy through Nginx. The following steps show you how to setup Pootle to proxy through Nginx.		A Pootle Web-translation server is made up of static and dynamic content. By default Pootle serves all content, for low-latency purposes it is better to get other webserver (like Apache, Lighttpd or Nginx in this example) to serve the content that does not change, the static content. It is just the issue of low latency and making the translation experience more interactive that calls you to proxy through Nginx. The following steps show you how to setup Pootle to proxy through Nginx.

pootle:no_install

Fri, 20 Oct 2006 08:28:35 +0000

1161332785		current
Line 4:		Line 4:
	- Check out / update the sources		- Check out / update the sources
	- Ensure you have the depencies		- Ensure you have the depencies
-	- Run setuppath from the src/ directory of the source tree (this only needs to be done once for each of your local directories - look at the script setpath that is created by setuppath for this)	+	- Run setuppath from the src/ directory of the source tree (this only needs to be done once for each of your local directories - look at the script setpath that is created by setuppath for this). If you change the full path where the source tree is, you need to rerun this, otherwise you won't need to rerun it.
	- Include or source setpath into your environment with (running it won't work). This includes the toolkit and Pootle sources in the PYTHONPATH of your current shell only and also puts most of the executables of the toolkit in your PATH.		- Include or source setpath into your environment with (running it won't work). This includes the toolkit and Pootle sources in the PYTHONPATH of your current shell only and also puts most of the executables of the toolkit in your PATH.

pootle:notifications

Tue, 17 Nov 2009 11:58:00 +0000

1258458896		current
Line 20:		Line 20:
	* Archive uploaded to project		* Archive uploaded to project
	* File reached 100%		* File reached 100%
		+
		+	===== Known issues =====
		+	It's still not possible to report users registering with a specific language or translation project. For more information, see [[bug>1159\|bug 1159]].

pootle:official_server

Thu, 06 Mar 2008 13:54:53 +0000

1204811693		current
Line 3:		Line 3:
	====== Pootle server ======		====== Pootle server ======

-	This page has information about our [[http://pootle.wordforge.org\|official Pootle server]]. This server is the place for translations of the Pootle interface, as well as some other projects. Please keep your translations of the Pootle interface up to date!	+	This page has information about our [[http://pootle.locamotion.org\|official Pootle server]]. This server is the place for translations of the Pootle interface, as well as some other projects. Please keep your translations of the Pootle interface up to date!

	===== Contact =====		===== Contact =====

pootle:performance

Fri, 26 May 2006 22:00:34 +0000

1148653669		current
Line 18:		Line 18:
	* Reindexing / altering some entries in a file		* Reindexing / altering some entries in a file
	* Overall initial startup		* Overall initial startup
		+
		+	{Friedel sê: Page generation for a big directory (like openoffice)}

	==== Ideas ====		==== Ideas ====

pootle:permissions

Wed, 18 Nov 2009 14:37:23 +0000

1258554967		current
Line 44:		Line 44:
	<note>A user with administrative rights can remove his own administrative rights.</note>		<note>A user with administrative rights can remove his own administrative rights.</note>

-	===== Implementation detail =====
-	The permissions are stored in .prefs file in the project directory. To retain your settings if you move you po files to a new server, these files should be copied along with your PO files.

-	An example rights section could look like this:
-	<code>
-	rights:
-	default = u'view, suggest, translate, review, archive, pocompile'
-	nobody = u'view, suggest, translate'
-	nelson = u'view, suggest, translate, overwrite, review, archive, pocompile, assign, admin, commit'
-	</code>

pootle:quotes

Wed, 16 Sep 2009 15:16:41 +0000

1249294762		current
Line 63:		Line 63:

	The application looks very nice and featureful. Good work!		The application looks very nice and featureful. Good work!
		+
		+	----
		+	A Zikula developer in IRC about Pootle:
		+
		+	(11:58:27) drak: by the way.. I made a crazy video to sell Pootle to our community
		+
		+	(11:58:27) drak: http://zikula.org/tutorials/thecat/thecat.html
		+
		+	(11:58:27) drak: honestly we LOVE Pootle.

pootle:running_under_apache

Mon, 06 Jul 2009 14:49:47 +0000

1246891359		current
Line 1:		Line 1:
-	====== Running Pootle 1.3 under Apache ======	+	Please refer to the [[pootle:apache\|Apache wiki page]].
-		+
-	Running Pootle under Apache requires [[http://www.modpython.org/\|mod_python]] or [[http://code.google.com/p/modwsgi/\|mod_wsgi]].	+
-		+
-	You need to extract Pootle in a directory accessible to the apache user.	+
-		+
-	Prepare the Pootle database as described in [[pootle/installation_1.3beta]]	+
-		+
-	make sure Apache has read access to all of Pootle's files and write access to the //dbs// and //po// subdirectories.	+
-		+
-	depending on which apache module you'll use to deploy pootle, you need to add the relevant portion to your apache's configuration	+
-		+
-	==== mod_wsgi ====	+
-	<code>	+
-	WSGIScriptAlias /pootle /var/www/Pootle/wsgi.py	+
-		+
-	Alias /pootle/html /var/www/Pootle/html	+
-	<Directory /var/www/Pootle/html>	+
-	Order deny,allow	+
-	Allow from all	+
-	</Directory>	+
-	</code>	+
-		+
-	[[http://docs.djangoproject.com/en/1.0/howto/deployment/modwsgi/\|more info]]	+
-		+
-	==== mod_python ====	+
-	<code>	+
-	<Location "/pootle">	+
-	SetHandler python-program	+
-	PythonHandler django.core.handlers.modpython	+
-	SetEnv DJANGO_SETTINGS_MODULE pootle.settings	+
-	PythonOption django.root /pootle	+
-	PythonPath "['/var/www/Pootle'] + sys.path"	+
-	PythonInterpreter pootle	+
-	PythonDebug On	+
-	</Location>	+
-		+
-	<Location "/pootle/html">	+
-	SetHandler None	+
-	</Location>	+
-		+
-	<Directory /var/www/Pootle/html>	+
-	Order deny,allow	+
-	Allow from all	+
-	</Directory>	+
-	</code>	+
-		+
-	[[http://docs.djangoproject.com/en/1.0/howto/deployment/modpython/\|more info]]	+

pootle:searching

Thu, 19 Nov 2009 10:52:29 +0000

1218802243		current
Line 1:		Line 1:
	====== Searching in Pootle ======		====== Searching in Pootle ======
-	Pootle provides a basic searching functionality that allows translators / reviewers to search for some text. The search box is shown on the side of the gray navigation area oposite the language/project path currently viewed.	+	Pootle provides a basic searching functionality that allows translators / reviewers to search for some text. The search box is shown next to the language/project path currently viewed.

	===== Search domain =====		===== Search domain =====

pootle:service_scripts

Wed, 18 Nov 2009 15:14:54 +0000

1245500720		current
Line 1:		Line 1:
	====== Service Scripts ======		====== Service Scripts ======
		+
		+	<note>These scripts refer to Pootle versions up to 1.2. Since version 2.0 [[Apache]] is the recommended way to deploy Pootle installations.</note>

	If you are serious about hosting a Pootle server for any length of time you probably want to implement service scripts that allow you to start and stop Pootle using your systems convention for service scripts.		If you are serious about hosting a Pootle server for any length of time you probably want to implement service scripts that allow you to start and stop Pootle using your systems convention for service scripts.

pootle:setting_up_a_simple_pootle_server

Mon, 08 Jan 2007 08:22:29 +0000

	current
Line 1:	Line 1:
	+	====== Setting up a simple Pootle server ======

	+	FIXME This is not complete yet
	+
	+	The following will take you through the simple step of setting up a Pootle server for a number of languages on a Pootle server that serves one project. We assume that there are existing translation held in version control. It is a simple setup so we will not look at service scripts, proxing or security.
	+
	+	* Setup the software
	+	* Edit pootle.prefs
	+	* Add the project
	+	* Enable the languages
	+	* Enable startup user
	+	* Start PootleServer

pootle:site_administrator_s_guide

Mon, 08 Jan 2007 08:06:03 +0000

1159956306		current
Line 15:		Line 15:
	* Checking file permissions		* Checking file permissions
	* Disk space		* Disk space
-	* Tracebacks	+	* [[Tracebacks]]

	===== Bugs =====		===== Bugs =====

	* Pootle eats memory		* Pootle eats memory

pootle:startup_options

Thu, 19 Nov 2009 11:34:51 +0000

1258469098		current
Line 1:		Line 1:
	====== PootleServer ======		====== PootleServer ======

-	<note>This information is about an old Pootle version. Since version 2.0 Pootle is recommended to be used with Apache.</note>	+	<note>This information is about an old Pootle version. Since version 2.0 Pootle is recommended to be used with [[Apache]].</note>

	PootleServer provides the translation management system called Pootle and the web-based translation editor.		PootleServer provides the translation management system called Pootle and the web-based translation editor.

pootle:statistics

Mon, 02 Jun 2008 14:54:09 +0000

		current
Line 1:		Line 1:
		+	Next to each project and file link, Pootle shows the number of translated, fuzzy and untranslated strings. It also displays a graph showing the proportion of untranslated strings in red, the proportion of fuzzy strings in grey and the proportion of translated strings in green.

pootle:suggestions

Tue, 17 Nov 2009 11:14:31 +0000

1258456228		current
Line 9:		Line 9:

	===== Reviewing suggestions =====		===== Reviewing suggestions =====
-	In order to review suggestions, users must have reviewing privileges. There are two ways for reviewing suggestions: going through all of them, or reviewing while translating (available since 1.2).	+	In order to review suggestions, users must have privileges to translate. There are two ways for reviewing suggestions: going through all of them, or reviewing while translating.

-	To go through all of them, the reviewer must click on "Review Suggestions" from the edition functions of the project. This would guide her/him through all the suggestions available for the current view.	+	To go through all of them, the reviewer must click on "Review Suggestions" within the "Review" tab of the project. This would guide her/him through all the suggestions available for the current view.

	The second method is straightforward, since suggestions are shown throughout the translation process. Additionally, buttons for accepting and rejecting the suggestions are displayed.		The second method is straightforward, since suggestions are shown throughout the translation process. Additionally, buttons for accepting and rejecting the suggestions are displayed.
Line 17:		Line 17:
	While reviewing a suggestion, a coloured difference between the current translation and the suggestion is displayed. If available, the username is provided of the user that gave the suggestion.		While reviewing a suggestion, a coloured difference between the current translation and the suggestion is displayed. If available, the username is provided of the user that gave the suggestion.

-	In current Pootle versions, accepting and rejecting suggestions is only available when the "Review Suggestions" action is taken and normal input buttons are displayed to accept and reject suggestions. Accepting and rejecting suggestions have effect on single suggestions, so accepting a suggestions won't reject the remaining ones.\\	+	A click on the green tick icon approves the selected suggestion while the red cross rejects the selected suggestion. A suggestion approval doesn't imply the rejection of the remaining suggestions.
-	Since Pootle 1.2 this behaviour has changed: accepting a suggestion for a specific unit rejects all the remaining suggestions. Also, instead of the input buttons two icons are displayed -- a tick approves, and a cross discards. Added to this, no page reload is needed since all the requests are done using AJAX methods.	+	No page reload is needed since all the requests are done using AJAX methods.

	===== PO projects =====		===== PO projects =====

pootle:terminology

Fri, 09 Jun 2006 09:13:53 +0000

1149843715		current
Line 1:		Line 1:
	====== Pootle Terminology =====		====== Pootle Terminology =====

		+	The underlying toolkit [[toolkit:base classes]] define these concepts:
	* A TranslationStore is a file that stores translations (e.g. a PO file) - although it could also be used to refer to other ways of storing translations.		* A TranslationStore is a file that stores translations (e.g. a PO file) - although it could also be used to refer to other ways of storing translations.
	* A TranslationStore contains a number of TranslationUnits which contain messages		* A TranslationStore contains a number of TranslationUnits which contain messages
Line 6:		Line 7:
	* Note that monolingual formats (like .properties, OpenOffice SDF, DTD, HTML, etc.) only contain a source string.		* Note that monolingual formats (like .properties, OpenOffice SDF, DTD, HTML, etc.) only contain a source string.
	* However when handling plurals the source may actually contain different variants of a message for different plural forms (e.g. in English, the singular and plural), and the target as well (the number of variants in source and target strings are often different because different languages handle plurals differently).		* However when handling plurals the source may actually contain different variants of a message for different plural forms (e.g. in English, the singular and plural), and the target as well (the number of variants in source and target strings are often different because different languages handle plurals differently).
-	* In Pootle we have Languages, Projects, and TranslationProjects (which are a set of translation stores translating a project into a language)	+
		+	In Pootle we have:
		+	* Languages referring to the languages translated into
		+	* Projects referring to the different programs / sets of messages we translate
		+	* TranslationProjects (which are a set of translation stores translating a project into a language)

pootle:terminology_matching

Thu, 08 Oct 2009 07:37:41 +0000

1254987286		current
Line 19:		Line 19:

	If these limits prove too restrictive, feel free to point out use cases where this is not sufficient.		If these limits prove too restrictive, feel free to point out use cases where this is not sufficient.
		+
		+	Since the terminology matching is performed in real-time, you might want to keep an eye on the size of your terminology project to ensure that performance is not affected too greatly by having too many terms. This is highly dependent on your server abilities and the nature of what you are translating.

pootle:testing

Tue, 21 Oct 2008 15:45:06 +0000

	current
Line 1:	Line 1:
	+	====== Testing Pootle ======

	+	This page contains notes about Pootle's unit tests and how they should be used, interpreted and expanded.
	+
	+
	+	===== The Basics =====
	+	As with the [[toolkit:index\|Translate Toolkit]], Pootle's unit tests are written for use with [[http://codespeak.net/py/dist/test.html\|py.test]]. They are conventionally named ''test_//unit//.py'', indicating that it is a file containing tests for ''//unit//.py''.
	+
	+	Warning: For some inexplicable reason the tests seem very unstable and unreliable, //especially// when run together with other tests (ie. running ''py.test'' in the Pootle directory without specifying any test-files). The ''--boxed'' option seems to help, although not in all cases. It is recommended that you run the tests for a particular test file by itself (ie. ''py.test test_//unit//.py'').
	+
	+	Each section below discusses a particular test file.
	+
	+
	+	===== test_client.py =====
	+	This file contains tests for all the basic Pootle features available. It is the most important of all the test files, because these tests define the behaviour of Pootle in most cases.
	+
	+	===== test_cmdlineserver.py =====
	+
	+	===== test_create.py =====
	+
	+	===== test_indexing.py =====
	+
	+	===== test_init.py =====
	+
	+	===== test_pootlefile.py =====

pootle:tips_from_the_trench

Wed, 18 Nov 2009 15:18:07 +0000

1213868552		current
Line 1:		Line 1:
	====== Tips from the trench ======		====== Tips from the trench ======
		+
		+	<note>These tips have been written with Pootle versions up to 1.2 in mind and things might not be the same in newer versions of Pootle.</note>

	===== Easy term searches in Opera =====		===== Easy term searches in Opera =====

pootle:tracebacks

Mon, 08 Jan 2007 09:35:53 +0000

1168244208		current
Line 6:		Line 6:
	\| [[toolkit:--errorlevel=ERRORLEVEL\|--logerrors=ERRORLEVEL]] \| level of errors to send to log: none, message, exception, traceback \|		\| [[toolkit:--errorlevel=ERRORLEVEL\|--logerrors=ERRORLEVEL]] \| level of errors to send to log: none, message, exception, traceback \|

-	If you use ''--browseerrors'' then the traceback will be sent to the web browser. This is useful if you are debugging locally, but is probably a problem if this is a live Pootle site as you might not want people to see the traceback. Using ''--logerrors'' will output the errors to the log, this is probably the best option for a live Pootle server.	+	If you use ''--browsererrors'' then the traceback will be sent to the web browser. This is useful if you are debugging locally, but is probably a problem if this is a live Pootle site as you might not want people to see the traceback. Using ''--logerrors'' will output the errors to the log, this is probably the best option for a live Pootle server.

	We suggest that you use ''--logerrors=traceback'' on a live server and add ''--browsererrors=traceback'' when debugging.		We suggest that you use ''--logerrors=traceback'' on a live server and add ''--browsererrors=traceback'' when debugging.

pootle:ui_ideas

Tue, 17 Nov 2009 09:07:29 +0000

1258448780		current
Line 170:		Line 170:
	* Have a Tip of the Month or Version Tip, e.g. "Pootle supports the gettext msgctxt feature: add contextual information to your strings to ensure more accurate translations."		* Have a Tip of the Month or Version Tip, e.g. "Pootle supports the gettext msgctxt feature: add contextual information to your strings to ensure more accurate translations."

-	==== UI clarity ====

-	=== Problem 1 ===
-	Some parts of the page don't stand out as clearly from others as they should. Links don't show if they have been visited or not.
-
-	=== Fix ===
-
-	* Enclose key areas in a different coloured ribbon (eg with a light green background), for example the command box or corner menu box.
-	* (HIG) Adapt CSS to show visited links
-
-	=== Problem 2 ===
-	Links wrap, so multiple-word links are split on different lines.
-
-	=== Fix ===
-	Use non-breaking spaces in the link names so that they don't wrap.
-
-	=== Problem 3 ===
-	It's not really a problem, but the GNOME iconset used on Pootle is a little bit outdated. Also, some links seem to be kind of naked (my account, admin, projects).
-
-	=== Fix ===
-	Update the iconset (e.g. [[http://tango.freedesktop.org\|Tango]]) and use more icons for certain links. Each project could have a logo (uploaded by the project admin) to easily distinguish between other projects, too.

	==== Community ====		==== Community ====

pootle:updatetm

Tue, 19 Aug 2008 09:11:37 +0000

1219136859		current
Line 3:		Line 3:
	updatetm is a tool in the Pootle package to generate suggestions from a translation memory to aid translators. This is done by writing .tm files for Pootle to use. Pootle has the ability to show related translations in the translate page. Although related terminology can be suggested in real time from the terminology project, currently suggested translations from a translation memory have to be generated before translation to ensure that performance is not affected too severely.		updatetm is a tool in the Pootle package to generate suggestions from a translation memory to aid translators. This is done by writing .tm files for Pootle to use. Pootle has the ability to show related translations in the translate page. Although related terminology can be suggested in real time from the terminology project, currently suggested translations from a translation memory have to be generated before translation to ensure that performance is not affected too severely.

-	Whereas terminology matching look for certain keywords in the translation like "file", "network", etc. updatetm rather looks for complete translations that are similar in the translation memory. So for a translation like	+	Whereas [[terminology matching]] look for certain keywords in the translation like "file", "network", etc. updatetm rather looks for complete translations that are similar in the translation memory. So for a translation like
	"Please enter the name:"		"Please enter the name:"
	it might give suggestions like		it might give suggestions like
Line 53:		Line 53:
	The script to use is called updatetm, not updatetm.py. To run it, you have to prepend it with "python.exe" so that MS Windows knows to use Python to run it.		The script to use is called updatetm, not updatetm.py. To run it, you have to prepend it with "python.exe" so that MS Windows knows to use Python to run it.

-	===== Bugs =====	+	===== Issues =====

	* updatetm does not yet support XLIFF files		* updatetm does not yet support XLIFF files
	* The default value of --length up to version 1.1 was far too small (50)		* The default value of --length up to version 1.1 was far too small (50)
		+	* Remember that installing [[https://sourceforge.net/project/showfiles.php?group_id=91920&package_id=260161/&abmode=1\|python-levenshtein]] will speed up the TM matching substantially. It should function without it, though.

pootle:using_mysql

Fri, 20 Nov 2009 01:00:42 +0000

1252056697		current
Line 2:		Line 2:

	mysql -u root -p		mysql -u root -p
-	> create database pootle;	+	> CREATE DATABASE pootle CHARACTER SET = 'utf8;
-	> grant all privileges on pootle.* to pootle@localhost identified by 'pootlepassword';	+	> GRANT ALL PRIVILEGES ON pootle.* TO pootle@localhost IDENTIFIED BY 'pootlepassword';
-	> flush privileges;	+	> FLUSH PRIVILEGES;

	Next edit the /etc/pootle/localsettings.py file (found under the main Pootle directory if running from checkout) and modify the DATABASE_* options to use your newly created database		Next edit the /etc/pootle/localsettings.py file (found under the main Pootle directory if running from checkout) and modify the DATABASE_* options to use your newly created database
Line 17:		Line 17:
	</code>		</code>

-	You need to initialize the database using the same commands described in [[pootle/installation_1.3beta]]	+	As described in [[pootle/installation_1.3beta]] database tables and initial data will be created on the first visit to Pootle
-		+
-	./manage.py syncdb	+
-	./manage.py initdb	+

pootle:version_control

Tue, 17 Nov 2009 16:08:04 +0000

1213963324		current
Line 65:		Line 65:
	Possible ways of configuring non-interactive authentication are described in [[configure version control authentication]].		Possible ways of configuring non-interactive authentication are described in [[configure version control authentication]].

-	Feature suggestions:	+	===== Feature suggestions =====
-	* provide user interface for personal authentication (e.g. password or keyfile upload) for one-time use or permanent storage (attached to this specific Pootle user)	+	* Provide user interface for personal authentication (e.g. password or keyfile upload) for one-time use or permanent storage (attached to this specific Pootle user)

pootle:what_s_in_a_name

Wed, 21 Nov 2007 08:10:12 +0000

pootle:xliff_support

Wed, 10 Oct 2007 10:40:30 +0000

1192001871		current
Line 1:		Line 1:
	====== XLIFF support in Pootle ======		====== XLIFF support in Pootle ======

-	Pootle supports hosting XLIFF files since version 1.0. The file suffix should be .xlf. Fhis is the recommendation by LISA.	+	Pootle supports hosting XLIFF files since version 1.0. The file suffix should be .xlf. This is the recommendation by LISA.

	There is a configuration option to specify if a project is using PO or XLIFF.		There is a configuration option to specify if a project is using PO or XLIFF.

1149844005		current
Line 1:		Line 1:
	====== Pootle Metadata Storage =====		====== Pootle Metadata Storage =====

-	This is an attempt to crystallize some of the discussions we have had recently on improving the Pootle architecture.	+	This is an attempt to crystallize some of the discussions we have had recently on improving the Pootle architecture. If you have a different idea for how things should work, discussion on the mailing list is the right place, but clarifications etc are welcome in this page.
-	Let me outline briefly some of the interacting issues:	+
		+	These are some of the interacting issues we need to consider in parallel:
	- Scaling to multiple processes (e.g. when running under Apache) requires better [[locking]] of our file interaction, changes etc		- Scaling to multiple processes (e.g. when running under Apache) requires better [[locking]] of our file interaction, changes etc
	- Scaling to larger numbers of files (e.g. 180000 for Debian) will probably require [[performance\|faster]] statistics generation etc (in general, translation metadata)		- Scaling to larger numbers of files (e.g. 180000 for Debian) will probably require [[performance\|faster]] statistics generation etc (in general, translation metadata)
	- Moving to generic API for translation storage (the [[toolkit:base classes]] we use for PO, XLIFF, etc, etc) requires reworking our storage interaction		- Moving to generic API for translation storage (the [[toolkit:base classes]] we use for PO, XLIFF, etc, etc) requires reworking our storage interaction

-	Locking and Base Classes are already being worked on in the Pootle-locking-branch. In addition because of Base Classes I have been factoring out the statistics generation etc which was horribly intertwined with PO file interaction.	+	Locking and Base Classes are already being worked on in the Pootle-locking-branch. In addition because of Base Classes we have been factoring out the statistics generation etc which was horribly intertwined with PO file interaction.

	It may be helpful to review the terms used in the [[toolkit:base classes]] - they are outlined under [[terminology]]		It may be helpful to review the terms used in the [[toolkit:base classes]] - they are outlined under [[terminology]]
Line 14:		Line 15:

	==== Information Stored ====		==== Information Stored ====
-	When I say metadata I include the following information that we currently store/use that is either not stored in the PO file, or is summary information:	+	Metadata here sinclude the following information that we currently store/use that is either not stored in the PO file, or is summary information:
	- Counts of translation units (messages) in translation stores including		- Counts of translation units (messages) in translation stores including
	* Number of strings in a translation store, and number of translated/untranslated strings		* Number of strings in a translation store, and number of translated/untranslated strings
Line 63:		Line 64:
	===== Plan for Relational Database =====		===== Plan for Relational Database =====

-	I am proposing that we now move to storing all of the above metadata (Counts, Checks, Quick Statistics, Assignment, Goals, Rights and User information), to a backend relational database.	+	This is a proposal to move to storing all of the above metadata (Counts, Checks, Quick Statistics, Assignment, Goals, Rights and User information), to a backend relational database.
	This move would also give us an opportunity to clean up exactly what metadata we need to store, how it interacts with changes and locking, etc, etc.		This move would also give us an opportunity to clean up exactly what metadata we need to store, how it interacts with changes and locking, etc, etc.

Line 72:		Line 73:
	* Discussions about whether we should store all the translations in the database as well rather than the current file-based system		* Discussions about whether we should store all the translations in the database as well rather than the current file-based system

-	I mention these two issues first because they are the easiest things for people to suggest, without getting into the nitty-gritty of solving problems. Hence I would like to defer all discussions of the above to points to a later time, or at least a separate thread. Reasons for this:	+	These are the easiest things for people to suggest, without getting into the nitty-gritty of solving problems. Discussion of these should take place separately to this discussion and planning. Reasons for this:
	* Database Support is really up to the developers who actually implement this, although it is important that the right choice is made and we could give criteria here		* Database Support is really up to the developers who actually implement this, although it is important that the right choice is made and we could give criteria here
	* Storing all translations in the Database basically amounts to a redesign of Pootle, if proposed as the only way of storing translations. There are also complex issues that relate to synchronising with version control, allowing download/upload of files etc. And it is a great advantage of Pootle that you can currently just run it on a bunch of translation files. As has been pointed out on the debian list, it makes more sense to later consider implementing TranslationStores that use the database as a backend, if anything.		* Storing all translations in the Database basically amounts to a redesign of Pootle, if proposed as the only way of storing translations. There are also complex issues that relate to synchronising with version control, allowing download/upload of files etc. And it is a great advantage of Pootle that you can currently just run it on a bunch of translation files. As has been pointed out on the debian list, it makes more sense to later consider implementing TranslationStores that use the database as a backend, if anything.

-	We can only handle so much change at one time and we already have 3 or 4 major changes going on, so I'd like to make sure some of our current improvements land before we take up too much time in discussing the above.	+	We can only handle so much change at one time and we already have 3 or 4 major changes going on, so lets make sure some of our current improvements land before we take up too much time in discussing the above.

	==== Other options considered ====		==== Other options considered ====
Line 88:		Line 89:
	* An Object DB / Python Persistence engine - not as standard, not necessarily as open to other tools		* An Object DB / Python Persistence engine - not as standard, not necessarily as open to other tools

-	In the end it comes down to this is the kind of thing relational databases were designed for, so I think this is a clear choice	+	In the end it comes down to this is the kind of thing relational databases were designed for, so it seems a clear choice

	==== Issues for Design ====		==== Issues for Design ====

1154432675		current
Line 1:		Line 1:
	====== What's in a name? ======		====== What's in a name? ======

-	How did we arrive at such a strange name? There are of course more imnpolite ways of phrasing that question but the answer is always the same, "Yes we know that its sounds similar to that Spanish word". We followed the American tradition (with all of us being African that was of course easy, since it was nice to make sweeping assumptions about another country for a change) which is to find a word and create and acronym.	+	How did we arrive at such a strange name? There are of course more impolite ways of phrasing that question but the answer is always the same, "Yes we know that its sounds similar to that Spanish word". We followed the American tradition (with all of us being African that was of course easy, since it was nice to make sweeping assumptions about another country for a change) which is to find a word and create and acronym.

-	The word Pootle comes from this 1970's BBC TV Childrens program called [[http://www.thechestnut.com/flumps.htm\|The Flumps]]. The memories of which proved funnier then watching it 30 years later. Although the bit about Pootle keeping a secret and having to own secrets was quite funny for an Open Source coder. [[http://www.translate.org.za/blogs/david/\|David Fraser's]] wife Danielle, a British lass and thus with experience on all things British, especially BBC Childrens TV, chose the name. Pootle is the cute and fluffy baby Flump in the series so in sometimes Open Source tradition of cure and fluffy mascots, like Tux the penguin, Pootle stuck.	+	The word Pootle comes from this 1970's BBC TV Children's program called [[http://www.thechestnut.com/flumps.htm\|The Flumps]]. The memories of which proved funnier then watching it 30 years later. Although the bit about Pootle keeping a secret and having to own secrets was quite funny for an Open Source coder. [[http://www.translate.org.za/blogs/david/\|David Fraser's]] wife Danielle, a British lass and thus with experience on all things British, especially BBC Childrens TV, chose the name. Pootle is the cute and fluffy baby Flump in the series so in sometimes Open Source tradition of cure and fluffy mascots, like Tux the penguin, Pootle stuck.

-	So now that we had the name and accidently a mascot, we now needed the words for the acronym. That proved much harder. Well not really. The accronum Pootle is derived from PO-based Online Translation / Localization Engine. With a move to XLIFF we might need to create //Xlotle//.	+	So now that we had the name and accidentally a mascot, we now needed the words for the acronym. That proved much harder. Well not really. The acronym Pootle is derived from PO-based Online Translation / Localization Engine. With a move to XLIFF we might need to create //Xlotle//.

-	Pootle the character has gone through some changes. You'll notice that mst improvements and due to an improved diet now that Pootle is a true celebrety, not some kids TV series bit part player. But the core secret is that Pootle semi secretly took part in the //[[http://www.bodyforlife.com\|Body-for-Life]](tm)// program.	+	Pootle the character has gone through some changes. You'll notice that most improvements and due to an improved diet now that Pootle is a true celebrity, not some kids TV series bit part player. But the core secret is that Pootle semi secretly took part in the //[[http://www.bodyforlife.com\|Body-for-Life]](tm)// program.

	===== Pootle through the ages =====		===== Pootle through the ages =====

-	Or how I lost fat and gained mustle by getting my own Graphic Designer.	+	Or how I lost fat and gained muscle by getting my own Graphic Designer.

	Pootle when he was newly born. //Bound to be copyright the BBC but somehow can't find any copyright information.//		Pootle when he was newly born. //Bound to be copyright the BBC but somehow can't find any copyright information.//
Line 17:		Line 17:
	{{pootle:pootle-0-baby.jpg}}		{{pootle:pootle-0-baby.jpg}}

-	Pootle then realised that be might be contravening some copyright law saw he had to be handdrawn. You can see from the shaky lines that Pootle, or at least some prgorammer, respects copyright law.	+	Pootle then realised that be might be contravening some copyright law saw he had to be hand drawn. You can see from the shaky lines that Pootle, or at least some programmer, respects copyright law.

	{{pootle:pootle-1-handdrawn.jpg}}		{{pootle:pootle-1-handdrawn.jpg}}

-	A kind volunteer, who had probably dicovered some new SVG drawring tool, made us this nice version. This one guarded the gate for easy online translation for quite some time.	+	A kind volunteer, who had probably discovered some new SVG drawing tool, made us this nice version. This one guarded the gate for easy online translation for quite some time.

	{{pootle:pootle-2-smoothie.jpg}}		{{pootle:pootle-2-smoothie.jpg}}