Wiki Recent Changes

Syndicate content Translate Toolkit & Pootle
Updated: 1 year 21 weeks ago

developers:projects:ajax-editor - Filtering units by status

26. August 2010 - 13:09
1282808289currentLine 46: Line 46: ===== UI mockups ===== ===== UI mockups =====  +  +==== General Overview ==== {{:developers:projects:ajax_editor_mockup.png?580|Rough mockup of the design}} {{:developers:projects:ajax_editor_mockup.png?580|Rough mockup of the design}}  +  +==== Filtering by Status ====  +  +{{:developers:projects:ajax_editor_filter.png?580|Filtering units by status}} ===== Ways of implementation ===== ===== Ways of implementation =====
Categories: Documentation

developers:django-pootle

26. August 2010 - 12:04
1282816932currentLine 1: Line 1: This page tracks immediate tasks related to upcoming release of Pootle. for a more long term view check the [[developers/Pootle Roadmap]]. This page tracks immediate tasks related to upcoming release of Pootle. for a more long term view check the [[developers/Pootle Roadmap]]. -Help us test [[http://translate.sourceforge.net/snapshots/Pootle-2.1.0-beta1/Pootle-2.1.0-beta1.tar.bz2|latest beta]] by playing with the [[http://fish.locamotion.org|test server]] and by running through these [[developers/pootle/common tasks]]+Help us test [[http://translate.sourceforge.net/snapshots/Pootle-2.1.0-beta1/Pootle-2.1.0-beta1.tar.bz2|latest beta]] by running through these [[developers/pootle/common tasks]] ====== Outstanding Tasks ====== ====== Outstanding Tasks ======   * Packaging   * Packaging
Categories: Documentation

pootle:live_servers

26. August 2010 - 11:02
1282649052currentLine 99: Line 99:   * http://pootle.projecthq.biz/ (2.0)   * http://pootle.projecthq.biz/ (2.0)   * http://pootle.lakapps.lk/   * http://pootle.lakapps.lk/ -  * https://translate.icinga.org/pootle/+  * https://translate.icinga.org/pootle/ (2.0.3)   * http://pootle.openscope.org/pootle/ (2.0)   * http://pootle.openscope.org/pootle/ (2.0)   * http://preklad.magento.iguru.eu/ (2.0)   * http://preklad.magento.iguru.eu/ (2.0)
Categories: Documentation

toolkit:formats - Add links to info on Trados .txt

26. August 2010 - 10:21
1282810519currentLine 87: Line 87:   * Trados:   * Trados:     * .tmw     * .tmw -    * .txt (You can interchange using TMX)+    * .txt (You can interchange using TMX) [[http://uk.dir.groups.yahoo.com/group/Tradosuser/message/2318?o=1&d=-1|Format explanation]] and [[http://translate.google.com/translate?js=y&prev=_t&hl=en&ie=UTF-8&layout=1&eotf=1&u=http%3A%2F%2Fwww.diemohrs.de%2Ftipps2_neu.html&sl=auto&tl=en|2]] with some [[http://slaci.komarom.net/roli/Trados/TRADOS%206.5.5.439%20Freelance%20+%20TRADOS%20MultiTerm%20iX%206.0.1.209/TRADOS%206.5.5.439%20Freelance/Program%20Files/TRADOS/T65_FL/Samples/TW4Win/|examples]]. ===== Unlikely to be supported ===== ===== Unlikely to be supported =====
Categories: Documentation

pootle:pages:ui - Spelling corrections

26. August 2010 - 9:55
1282809231currentLine 7: Line 7: In between the content changes depending on which action the user is engaged with. But common UI elements shared among different pages include: In between the content changes depending on which action the user is engaged with. But common UI elements shared among different pages include: -  * **Translation Statistics** this is a bar graph showing the percentage of each object that is [[pootle/glossary#translated]] (green), [[pootle/glossary#fuzzy]] (purple) or [[pootle/glossary#untranslated]] (red). Objects that can have translation statistics include ([[pootle/glossary#language]], [[pootle/glossary#project]], [[pootle/glossary#translationproject|translation project]] (aka language/project pair) [[pootle/glossary#directory]], [[pootle/glossary#file]]). Hovering over the bargraph will show a tooltip with the percentage of words translated. and clicking on the object name will navigate to that object's page. +  * **Translation Statistics**: This is a bar graph showing the percentage of each object that is [[pootle/glossary#translated]] (green), [[pootle/glossary#fuzzy]] (purple) or [[pootle/glossary#untranslated]] (red). Objects that can have translation statistics include ([[pootle/glossary#language]], [[pootle/glossary#project]], [[pootle/glossary#translationproject|translation project]] (aka language/project pair) [[pootle/glossary#directory]], [[pootle/glossary#file]]). Hovering over the bar graph will show a tooltip with the percentage of words translated, and clicking on the object name will navigate to that object's page.  -  * **Top Contributors** this table shows users who made the highest number of [[pootle/glossary#submissions]] and [[pootle/glossary#suggestions]] and users who [[pootle/glossary#reviews|reviewed]] the highest number of suggestions. When displayed at the bottom of the [[frontpage]] it will display top contributors for the whole server. under [[language]], [[project]] and [[translationproject|translation project]] pages it will display top contributors for the corresponding [[pootle/glossary#language]], [[pootle/glossary#project]] or [[pootle/glossary#translationproject|translation project]] (aka language/project pair). +  * **Top Contributors**: This table shows users who made the highest number of [[pootle/glossary#submissions]] and [[pootle/glossary#suggestions]] and users who [[pootle/glossary#reviews|reviewed]] the highest number of suggestions. When displayed at the bottom of the [[frontpage]] it will display top contributors for the whole server. Under [[language]], [[project]] and [[translationproject|translation project]] pages it will display top contributors for the corresponding [[pootle/glossary#language]], [[pootle/glossary#project]] or [[pootle/glossary#translationproject|translation project]] (aka language/project pair). - +
Categories: Documentation

pootle:pages:language - Add title

26. August 2010 - 9:53
1282808725currentLine 1: Line 1:  +====== Language page ======  + Only users with view rights for the language can access the language page. Server level permissions are used if no language specific permissions exist. Only users with view rights for the language can access the language page. Server level permissions are used if no language specific permissions exist.
Categories: Documentation

pootle:pages:project - Add title

26. August 2010 - 9:53
1282808893currentLine 1: Line 1:  +====== Project page ======  + Only users with view rights for the project can access the project page. server level permissions are used if no project specific permissions exist. Only users with view rights for the project can access the project page. server level permissions are used if no project specific permissions exist.
Categories: Documentation

pootle:pages:frontpage - Spelling corrections

26. August 2010 - 9:51
1282748518currentLine 1: Line 1:  +====== Front page ======  + At the top of the front page a paragraph describing the Pootle server is displayed. the content of which can be changed in the [[admin/settings|server settings]] page. At the top of the front page a paragraph describing the Pootle server is displayed. the content of which can be changed in the [[admin/settings|server settings]] page. -The front page lists all Languages and Projects, each with their translation statistics and the last user to submit a translation and the time and date of that last submission+The front page lists all Languages and Projects, each one with their translation statistics and the last user who submitted a translation and the time and date of the last submission. - + -Whether visitors get to see the languages and projects is governed by the server wide view permission not by the permission of each language and project. + - + -It also displays the last few [[pootle/glossary#news]] items relating to the server as a whole (new projects or languages added to the server and new users registering).+ -Finally at the bottom is the top contributors for the whole server.+Whether visitors get to see the languages and projects is governed by the server-wide view permission, not by the permission of each language and project.  +It also displays the last few [[pootle/glossary#news]] items relating to the server as a whole (new projects or languages added to the server and newly registered users).  +Finally at the bottom there is the top contributors table for the whole server.
Categories: Documentation

es:virtaal:using_virtaal - Updated from PO files

25. August 2010 - 19:29
1282757295currentLine 23: Line 23: Tenga en cuenta que <Intro> le lleva a la siguiente posición donde desea teclear. En el caso de los segmentos con [[guide:translation:plurals|plurales]], <Intro> le llevará a la siguiente línea dentro de ese segmento. Tenga en cuenta que <Intro> le lleva a la siguiente posición donde desea teclear. En el caso de los segmentos con [[guide:translation:plurals|plurales]], <Intro> le llevará a la siguiente línea dentro de ese segmento. -Si tiene los [[spell checking||correctores ortográficos]] adecuados ya instalados, la corrección ortográfica debería estar activa tanto para el texto de origen como el de destino.+Si tiene los [[spell checking|correctores ortográficos]] adecuados ya instalados, la corrección ortográfica debería estar activa tanto para el texto de origen como el de destino. Puede deshacer normalmente con Ctrl+Z. Puede deshacer normalmente con Ctrl+Z.
Categories: Documentation

guide:translation:accelerators

25. August 2010 - 18:33
1279209454currentLine 6: Line 6: ===== What is an accelerator key and an accelerator marker ===== ===== What is an accelerator key and an accelerator marker ===== -If you look at the menu bar on any application you will see that the first letter of each entry in underlined.  Notice that __F__ile, __E__dit and __V__iew each have the first letter underlined.  To quickly open the File menu press Alt-F.  You will notice that most of the menu entries also have accelerator keys, to access __O__pen simply type **o** after typing Alt+F.+If you look at the menu bar on any application you will see that the first letter of each entry in underlined.  Notice that __F__ile, __E__dit and __V__iew each have the first letter underlined.  To quickly open the File menu press Alt+F.  You will notice that most of the menu entries also have accelerator keys, to access __O__pen simply type **o** after typing Alt+F. -An //accelerator marker// is the character we use to mark accelerator keys when we translate.+An //accelerator marker// is the special character we use to mark accelerator keys when we translate. ===== Identifying the accelerator key ===== ===== Identifying the accelerator key ===== Line 23: Line 23: In all of the above examples pressing **A** would take you to the //Save As// dialogue box. In all of the above examples pressing **A** would take you to the //Save As// dialogue box. -What happens if you want to use the & character without making it an accelerator?  In this case the accelerator is usually escaped by using && (for KDE) or &amp; (for Mozilla). Eg "Mail && News" or "Mail &amp; News".  As a translator you would be free to drop the & and use the equivalent of 'and' in your language.+What happens if you want to use the & character without making it an accelerator?  In this case the accelerator is usually escaped by using && (for KDE) or &amp; (for Mozilla). E.g. "Mail && News" or "Mail &amp; News".  As a translator you would be free to drop the & and use the equivalent of "and" in your language. ===== Selecting ===== ===== Selecting ===== Line 29: Line 29: How do you select an accelerator key for your languages? Keep these principles in mind: How do you select an accelerator key for your languages? Keep these principles in mind: -  - If it is the same or similar to the English, users will be able to switch to localised interfaces more easily.+  - Try to keep it similar to the English. This makes it easier for users to switch to localised interfaces.   - Accelerators should not degrade readability too much.   - Accelerators should not degrade readability too much. -  - Ideally, in any menu / window / dialog box, a letter should only be used as an accelerator for one string. If the letter 'T' is used for two menu entries, it is usually not a big problem, but the software isn't as usable as it could be.+  - Avoid duplication. Ideally, in any menu, window or dialogue box, a letter should only be used as an accelerator for one string. If the letter 'T' is used for two menu entries, it is usually not a big problem, but the software isn't as usable as it could be  +  - Review accelerators in the running application. We usually follow these simple rules. We usually follow these simple rules. -  - Try to keep the same position as the original.  Eg "&File" -> "&Ifayile" +  - Try to keep the same position as the original.  E.g. "&File" -> "&Ifayile"  -  - Try to keep the same letter as the original. Eg "&File" -> "I&fayile" +  - Try to keep the same letter as the original. E.g. "&File" -> "I&fayile"  -  - Select an uncommon letter.  In Xhosa the letter I occurs frequently so we try to avoid using it too much +  - Select an uncommon letter.  In Xhosa the letter I occurs frequently so we try to avoid using it too much.  -  - Avoid adding accelerators under characters with descenders such as lower case g, p, q or y.  The character goes below the base line and thus it causes the character to look odd and the accelerator not to be immediately recognisable. e.g. In GNOME _g would appear as __g__ which looks messy. It is best to confirm with an actual test, since some rendering systems actually support underlining clearly when the letter contains a descender.+  - Avoid adding accelerators under characters with descenders such as lower case g, p, q or y.  The character goes below the base line and could cause the character to look odd and the accelerator not to be immediately recognisable. E.g. in KDE &g would appear as __g__ which looks messy. It is best to confirm with an actual test, since some rendering systems actually support underlining clearly when the letter contains a descender.   - Try to avoid letter next to a descender for similar reasons as above.   - Try to avoid letter next to a descender for similar reasons as above. -  - Avoid letters that are only one pixel wide, e.g. i and l. +  - Avoid narrow letters like i and l.  -  - Make sure the character is actually available on the users keyboard.  Accented characters such as ä might or might not be present on a keyboard in the language. +  - Make sure the character is actually available on the user's keyboard.  Accented characters such as ä might or might not be present on a keyboard in the language.  -  - If your language uses diacritics under certain letters such as ț, ḓ or ọ, avoid these characters as well, as the underline might run through the diacritic. You should almost never be choosing a letter with any diacritic, since users might not be able to use the access key by pressing a single keyboard key. Rather avoid letters with diacritics unless you are very sure that they will be usable by the end-users.+  - If your language uses diacritics under certain letters such as ț, ḓ or ọ, avoid these characters as well, as the underline might run through the diacritic. Avoid letters with diacritics entirely unless you are very sure that they will be usable by the end-users.   - No available character.  Usually in Asian languages where a keyboard is Western. Translate the word into your language and use the original English accelerator. Ie "&File" -> "XXXX(&F)".  In Mozilla you can safely ignore defining the accelerator in which case it will default to the English version (FIXME: validate this :)   - No available character.  Usually in Asian languages where a keyboard is Western. Translate the word into your language and use the original English accelerator. Ie "&File" -> "XXXX(&F)".  In Mozilla you can safely ignore defining the accelerator in which case it will default to the English version (FIXME: validate this :)   - Non-letters like numbers and punctuation marks can be used if they are present on a standard keyboard as is common amongst the speakers of your language. This will usually only be a relevant choice if it was chosen for the source text as well.   - Non-letters like numbers and punctuation marks can be used if they are present on a standard keyboard as is common amongst the speakers of your language. This will usually only be a relevant choice if it was chosen for the source text as well. Line 55: Line 56:   * Available __A__ctions...   * Available __A__ctions... -You will notice that all the accelerators use the **A** key --- this is a clash.  Fortunatly most applications will cycle through the options as you press A repeatedly.  But what would happen if the 3rd item appeared first? (The third item uses the elipses (...) to indicate that a dialogue box will open.  This if this appeared first you would never be able to access the other items.+You will notice that all the accelerators use the **A** key --- this is a clash.  Fortunately most applications will cycle through the options as you press A repeatedly.  But what would happen if the 3rd item appeared first? (The third item uses the ellipses (...) to indicate that a dialogue box will open.  This if this appeared first you would never be able to access the other items. Here is a better choice of accelerators for the same menu: Here is a better choice of accelerators for the same menu: Line 88: Line 89: ===== Errors ===== ===== Errors ===== -What happens if you select the same accelerator key for two different components?  How +What happens if you select the same accelerator key for two different components?  How do you check this? -do you check this?+ -Firstly, its not a train smash.  Once the application is fully translated these +Firstly, it is not a big problem.  Once the application is fully translated these conflicts should sort themselves out over time. -conflicts should sort themselves out over time.+ ===== Application Specific Notes ===== ===== Application Specific Notes ===== Line 102: Line 101: ==== OpenOffice ==== ==== OpenOffice ==== -OpenOffice.org seems to have a system that will automatically determine missing accelerator +OpenOffice.org seems to have a system that will automatically determine missing accelerator keys.  What would work best with this system is to mark the accelerators that you would like to remain static and allow the others to be automatically determined.  So keep "File", "Edit", "View" accelerators constant but allow all others to be determined at runtime. -keys.  What would work best with this system is to mark the accelerators that you would + -like to remain static and allow the others to be automatically determined.  So keep "File", + -"Edit", "View" accelerators constant but allow all others to be determined at runtime.+
Categories: Documentation

developers:index - add ajaxifying project

25. August 2010 - 10:32
1282375885currentLine 51: Line 51: ===== Current projects ===== ===== Current projects =====  +  * [[developers:projects:ajax-editor|AJAXifying Pootle's editor]]   * [[developers:projects:odf|OpenDocument translation project]] (done, with some areas of improvement possible)   * [[developers:projects:odf|OpenDocument translation project]] (done, with some areas of improvement possible)   * <del>[[developers:projects:mozilla|Mozilla tools project]]</del>   * <del>[[developers:projects:mozilla|Mozilla tools project]]</del>
Categories: Documentation

virtaal:localising_virtaal

24. August 2010 - 11:20
1282641452currentLine 9: Line 9:     * Check for clashes of access keys that should be accessible in the main application window.  These are all the main menu items, all the items in the search navigation, and all the access keys in the editing area.     * Check for clashes of access keys that should be accessible in the main application window.  These are all the main menu items, all the items in the search navigation, and all the access keys in the editing area.     * Check for the strings that have limited space to show. These should be marked in the PO file for your attention.  They are usually the descriptions of the TM backends.  Try to get suggestions from these to see how much space is available.  It is usually around 11 characters in the worst case.     * Check for the strings that have limited space to show. These should be marked in the PO file for your attention.  They are usually the descriptions of the TM backends.  Try to get suggestions from these to see how much space is available.  It is usually around 11 characters in the worst case.  +  * Send your translated file to one of the developers, or attach it to a bug report, or upload it to Pootle.   * We currently use the InnoSetup installer for building our Windows installers. You might want to check that the localisation for your language is there and an official translation.   * We currently use the InnoSetup installer for building our Windows installers. You might want to check that the localisation for your language is there and an official translation.   * Check if your language is already supported with [[autoterm]] and talk to the Virtaal developers about adding support for your language.   * Check if your language is already supported with [[autoterm]] and talk to the Virtaal developers about adding support for your language.   * We use autocorrect data from OpenOffice.org, but can also ship with extra files.  Contact us if you want to do some customisation.   * We use autocorrect data from OpenOffice.org, but can also ship with extra files.  Contact us if you want to do some customisation.   * For translators with non-Latin scripts, you can customise the image on the welcome screen. Send us the text and your desired font to start the process.  If you prefer to edit it yourself, get in contact with us and ensure you are working on the SVG, not the PNG.   * For translators with non-Latin scripts, you can customise the image on the welcome screen. Send us the text and your desired font to start the process.  If you prefer to edit it yourself, get in contact with us and ensure you are working on the SVG, not the PNG.
Categories: Documentation

virtaal:index - Clean up the contributing section, link to [[localising virtaal]]

24. August 2010 - 11:20
1282556284currentLine 29: Line 29: ===== Contributing ===== ===== Contributing ===== -There are many ways of contributing to Virtaal. Join the mailing list or IRC channel to join our effort. You can translate the user interface into your language. Do that by installing Virtaal and opening the [[http://translate.svn.sourceforge.net/viewvc/translate/src/trunk/virtaal/po/virtaal.pot|latest POT file]]. Attach it in a bug report, or send it to one of the developers.+There are many ways of contributing to Virtaal. Join the mailing list or IRC channel to join our effort. You can join our effort to distribute Virtaal by sharing informing with people, writing documentation or packaging for more platforms. -You can join our effort to distribute Virtaal by sharing informing with people, writing documentation or packaging for more platforms. +If you would like to contribute to the Virtaal software, you can start by reading the instructions on the following pages: - + -If you would like to contribute to Virtaal by programming, you can start by reading the instructions on the following pages:+  +  * [[Localising Virtaal]]   * [[Building]]   * [[Building]]   * [[Testing]]   * [[Testing]]
Categories: Documentation

virtaal:opensuse_installation - created

23. August 2010 - 11:37
currentLine 1: Line 1:  +====== Installing Virtaal on openSUSE =====  +Virtaal is packaged in repositories kindly maintained by Luiz Fernando Ranghetti.  If you add these repositories to your system, you can access Virtaal through your package manager and receive updates.  +  +===== Add the correct repository =====  +You can add a repository in YaST by specifying a URL.  +  +  * **for openSUSE 11.3**: http://download.opensuse.org/repositories/home:/elchevive/openSUSE_11.3/  +  * **for openSUSE 11.2**: http://download.opensuse.org/repositories/home:/elchevive/openSUSE_11.2/  +  * **for openSUSE 11.1**: http://download.opensuse.org/repositories/home:/elchevive/openSUSE_11.1/  +  +  +If you want to add it on the command line, perform the correct command based on your version openSUSE:  +  +  zypper ar -f http://download.opensuse.org/repositories/home:/elchevive/openSUSE_11.3/  translate  +or  +  zypper ar -f http://download.opensuse.org/repositories/home:/elchevive/openSUSE_11.2/  translate  +or  +  zypper ar -f http://download.opensuse.org/repositories/home:/elchevive/openSUSE_11.1/  translate  +  +Here "ar" means "add repository", "-'f" to make it refresh and  +"translate" is the name that you give to the repository.  +  +  +Now you can install Virtaal through YaST or zypper.  +  +  +===== Installing Virtaal =====  +  +You can install Virtaal with YaST, by searching for it in the software manager.  +  +Alternatively you can install it on the command-line with zypper:  +    zypper in python-virtaal  +  +===== Note =====  +You will be asked to accept the key for the new repository.  After accepting the key, it shouldn't ask again, and everything should work.  +  +To install only the Translate Toolkit from the repositories you added, just search for python-translate-toolkit.  On the command-line, that means  +  +  zypper in python-translate-toolkit
Categories: Documentation

developers:mozootle - old revision restored

21. August 2010 - 12:01
1282379593currentLine 3: Line 3: <note >The Mozootle code has been merged into the trunk, and Pootle was ported to Django.  Pootle 2.0 (released in December 2009) was released with great success, incorporating the ideas that started as part of Mozootle. ([[developers:The Great Pootle Migration|more background information]])  Pootle is now deployed at [[http://localize.mozilla.org|Mozilla]].</note> <note >The Mozootle code has been merged into the trunk, and Pootle was ported to Django.  Pootle 2.0 (released in December 2009) was released with great success, incorporating the ideas that started as part of Mozootle. ([[developers:The Great Pootle Migration|more background information]])  Pootle is now deployed at [[http://localize.mozilla.org|Mozilla]].</note> -Mozootle is a branch of Pootle development as part of Mozilla's [[https://wiki.mozilla.org/Verbatim|Verbatim]] project. This page contains notes and planning for developers about merging of the Mozootle branch into the main development line of Pootle and [[http://www.popularreview.com/services/rankpay-review/|rankpay]]. [[http://www.resumesplanet.com/|resume writing]]+Mozootle is a branch of Pootle development as part of Mozilla's [[https://wiki.mozilla.org/Verbatim|Verbatim]] project. This page contains notes and planning for developers about merging of the Mozootle branch into the main development line of Pootle. ===== Resource ===== ===== Resource =====
Categories: Documentation

toolkit:contributing - link to the testing guidelines

21. August 2010 - 9:59
1282035022currentLine 25: Line 25: Check for any files that are missing, tools that were not installed, etc. Check for any files that are missing, tools that were not installed, etc. -Run unit tests to see if there are any issues.  You'll need the [[http://codespeak.net/py/dist/test.html|py.test]] unit test software  +[[developers:testing_guidelines#running tests|Run unit tests]] to see if there are any issues.  Please report any failures. -which you can install from your distribution. Alternatively you can install it with easy_install: + - + -  easy_install py + - + -To run the tests you do + - + -  py.test + - + -from the translate src directory, or + - + -  py.test storage/test_dtd.py + - + -to run a specific set of tests. + - + -Report any failures. + - + -Note: If your Pootle tests fail with an error along the lines of: + -  URLError: <urlopen error (-2, 'Name or service not known')> + - + -Check your http_proxy environment variable. Usually it helps just to unset it: + -  unset http_proxy+ Finally, simply work with the software.  Checking all your current usage patterns and report problems. Finally, simply work with the software.  Checking all your current usage patterns and report problems.
Categories: Documentation

spelt:testing - Link back tp our py.test page

21. August 2010 - 9:55
1214481090currentLine 1: Line 1: ====== Testing ====== ====== Testing ====== -===== Required packages =====+Please first read about [[developers:testing_guidelines#running tests]]. -  * [[http://codespeak.net/py/dist/test.html|py.test]] +To run all tests, you can run py.test from the ''spelt'' directory or any subdirectory if you only want to run the tests for that particular module. - + -===== Running the tests ===== + - + -To run all tests, you can simply run py.test from the ''spelt'' directory or any subdirectory if you only want to run the tests for that particular module.+ Currently only the models have tests. Currently only the models have tests.
Categories: Documentation

developers:release - link to the testing guidelines

21. August 2010 - 9:51
1260196490currentLine 45: Line 45: ===== Afterwards ===== ===== Afterwards ===== -  * check unit tests (py.test)+  * check unit tests ([[developers:testing_guidelines#running_tests|py.test]])     * consider disabling some if we won't fix them     * consider disabling some if we won't fix them   * Anything to backport / forwardport   * Anything to backport / forwardport
Categories: Documentation

developers:testing_guidelines - created

21. August 2010 - 9:40
1282377998currentLine 7: Line 7: You need at least py.test >= 1.0.0 You need at least py.test >= 1.0.0 -To run the tests you do+To run the all tests in the current directory and its subdirectories.   py.test   py.test -to run all tests in the directory or subdirectory.+to run tests in a specific test file.   py.test storage/test_dtd.py   py.test storage/test_dtd.py -to run a specific set of tests.  ===== py.test functionality that we use ===== ===== py.test functionality that we use =====
Categories: Documentation

developers:projects:breakage:translate_toolkit

20. August 2010 - 17:02
1216392434currentLine 1: Line 1: -====== Automatically generated Pootle files ======+====== Automatically generated Toolkit files ====== -Pootle indexes each language in every project if PyLucene or Xapian are available. +Pocount (and therefore also Virtaal and older versions of Pootle) can store the stats database in ~/.translate_toolkit/. It is an SQLite database and can be safely removed / renamed if no process is using it. - + -The indices are stored under ''.translation_index'' under a language directory (for example ''pootle/eu/.translation_index''). Corrupt indices might cause problems. Deleting the ''.translation_index'' directories will cause Pootle to regenerate the indices. + - + -Also have a look at the [[developers:projects:breakage:translate_toolkit|files generated]] by the Translate Toolkit.+
Categories: Documentation