Pootle

1351594744currentLine 1: Line 1: -<note>Most of the information on this page has been moved: http://docs.translatehouse.org/projects/translate-toolkit/en/latest/index.html</note>+<note>Most of the information on this page has been ... [More] moved: http://toolkit.translatehouse.org/</note>     ====== The Translate Toolkit ====== ====== The Translate Toolkit ====== [Less]

1346164866currentLine 168: Line 168:  | pms | Piemontese | nplurals=2; plural=(n != 1) | | pms | Piemontese | nplurals=2; plural=(n != 1) |  | pt | Portuguese | nplurals=2; plural=(n != 1) | | pt | Portuguese | nplurals=2; plural=(n != 1) | -| pt_BR ... [More] | Brazilian Portuguese | nplurals=2; plural=(n != 1) |+| pt_BR | Brazilian Portuguese | nplurals=2; plural=(n > 1) |     ===== R ===== ===== R ===== [Less]

1342456095currentLine 1: Line 1:  +<note>Most of the information on this page has been moved: http://translate.readthedocs.org/projects/pootle/en/latest/features/hooks.html</note>  +  ====== Pootle hooks ====== ====== Pootle hooks ======   

1356954289currentLine 13: Line 13:  ===== UI ===== ===== UI =====    -The developer comments are currently visually separate from translators comments, this could cause a bit of confusion. So we might want to investigate merging our comments into ... [More] one area.  In this case developer comments would need to move down to display with translators comments.  We'd also need to use visual cues and text to indicate the different roles.+The developer comments are currently visually separate from translators comments, this could cause a bit of confusion. FIXME So we might want to investigate merging our comments into one area.  In this case developer comments would need to move down to display with translators comments.  We'd also need to use visual cues and text to indicate the different roles.     DELETEME (If we don't do use case one then this can be ignored) The existing developer comment should be editable.  Thus an edit button and the ability to make a correction to the developer comment text should be available to a user with the correct rights.  If someone has edited the developer comment then the new version should be what is displayed instead of the version supplied from the source files.  If the source version changes then both should be displayed so that the second version may be deleted. DELETEME (If we don't do use case one then this can be ignored) The existing developer comment should be editable.  Thus an edit button and the ability to make a correction to the developer comment text should be available to a user with the correct rights.  If someone has edited the developer comment then the new version should be what is displayed instead of the version supplied from the source files.  If the source version changes then both should be displayed so that the second version may be deleted. [Less]

currentLine 1: Line 1:  +====== Shared Project Comments ======     +See [[bug>2658]]  +  +===== User Stories =====  +  +Jane notices a problem with an existing translator comment and wants to improve the quality of information shared with ... [More] translators. So she makes the correction and all other translators now see that correction.  +  +Fred was struggling with a terms, found a great Wikipedia reference and wants to share that with other translators so that they don't need to waste as much time.  +  +==== Proposed Solution ====  +  +We'll use most of the existing infrastructure we've created:  +  +  - User comments are used as this prevents the overwriting of them by Gettext tools  +  - Comments are displayed as our user comments but in addition to any language specific comments.  This limits the changes to the UI.  +  +  +=== Interaction with Gettext ===  +  +If we use translators comments i.e. #[space] these will be preserved when manipulated by Gettext tools.  Developer comment #. will be overwritten.  +  +Thus the proposed solution is to use marked translators comments.  We use marking so that they can be distinguished from other translator comments and can thus be updated as needed.  +  +=== Comment examples ===  +  +  +# (shared)Some comments(/shared)  +  +  +=== Updating comments ===  +  +==== Things not dealt with ====  +  +The following are things we have on purpose not dealt with.  Some are hard and some are of indeterminate value compared to other things we can spend time on.  +  +  * If you are correcting a comment do we hide the incorrect one? At the moment we're not doing that at all.  Thus you could end up with two comments that are almost identical.  +  * We don't propose a way to extract the comments from Pootle and place them back into the code so that they can become proper developer comments.  +  *  [Less]

1354461274currentLine 51: Line 51:     Het OpenOffice.org bestand voor AutoCorrectie is een zip-bestand, dat bijvoorbeeld is genaamd: acor_en-US.dat.  [[[email protected]|Søren Thing Pedersen]] heeft ... [More] [[http://da.openoffice.org/files/documents/122/2851/csv2acor.py|csv2acor.py]] gemaakt, wat een bestand voor AutoCorrectie genereert vanuit CSV-bronnen.   Het OpenOffice.org bestand voor AutoCorrectie is een zip-bestand, dat bijvoorbeeld is genaamd: acor_en-US.dat.  [[[email protected]|Søren Thing Pedersen]] heeft [[http://da.openoffice.org/files/documents/122/2851/csv2acor.py|csv2acor.py]] gemaakt, wat een bestand voor AutoCorrectie genereert vanuit CSV-bronnen.   -The autocorrect file contains 3 XML files:+Het bestand voor autocorrectie bevat 3 XML-bestanden:       * DocumentList.xml - paren van foutief gespelde woorden en hun correcte spelling   * DocumentList.xml - paren van foutief gespelde woorden en hun correcte spelling [Less]

currentLine 1: Line 1:  +====== Prioritisation of 2.5 bugs ======  +  +  - P1 - can't install the server e.g. toolkit release (since you can't even install the thing)  +  - P2 - breaks the server in an important way.  Things are broken when you ... [More] translate or push/pull translations e.g. timezone (since this means you can't actually work on the server)  +  - P3 - breaks the server i.e. some error report.  But nothing that prevents you doing anything.  (So news bugs and credits bugs while anoying wouldn't stop you doing translations.)  +  - P3 - something confuses the user e.g. reached end of translations and not indicated (won't kill you but frustrates users)  +  - P4 - features - one that we would want to land in 2.5 if it's easy enough to do. Incomplete parts of 2.5 features. (while incomplete we can live without it)  +  - P5 - feature - one that we can delay to 2.5+ (too big this late or we can live without it)  +  +===== Not important =====  +  +  - Small graphics glitches e.g. hiding checks  +  - Small nice-to-have features e.g. wikipedia plugin on by default    [Less]

1353598970currentLine 33: Line 33:  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. You will be asked to accept the key for the new repository.  After ... [More] 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 translate-toolkit.  On the command-line, that means+To install just the Translate Toolkit from the repositories you added, just search for translate-toolkit.  On the command-line, that means       zypper in translate-toolkit   zypper in translate-toolkit [Less]

1337265892currentLine 35: Line 35:  |  Persian  |  فارسی  | |  Persian  |  فارسی  |  |  Portuguese  |  Português  | |  Portuguese  |  Português  | -|  Russian     |  русский  | +|  Russian     |  Русский  |  -|  Serbian     |  српски //or// srpski   ... [More] |+|  Serbian     |  Српски //or// Srpski   |  |  Sinhala     |  සිංහල  | |  Sinhala     |  සිංහල  |  |  Sotho, Southern |  Sesotho  | |  Sotho, Southern |  Sesotho  | [Less]

1353098900currentLine 1: Line 1: -<note>Deze pagina 1s verplaatst naar: http://translate.readthedocs.org/projects/pootle/en/latest/server/installation.html</note>+<note>Deze pagina is verplaatst naar: ... [More] http://translate.readthedocs.org/projects/pootle/en/latest/server/installation.html</note>     ====== Systeemvereisten ====== ====== Systeemvereisten ====== [Less]