This tool, to be used before committing your work, should help you locate problems in translation files. Please consider it as work-in-progress, as we are still working on it.
First of all, it will help you find missing accelerators - Luebbe's translation status page shows counts but not strings themselves, so the table below will help you fix these problems.
The analysis also includes some other useful lists, it checks for instance for correct new line styles, untranslated strings and spelling mistakes. As we prefer to err on the side of caution, you may find a lot of false positives. Anyway I hope this will help you improve the quality of your translation.
Oto
Please follow this link if you think you may help with translation.
-> TortoiseSVN translation
You can upload file for check before you make actual commit, so you can fix errors in one commit.
Make sure you are going to check translation against proper branch.
Last update: September 05 2010 17:08 CET (GMT+1/GMT+2(DST))
Go to STABLE.
 Language |
 GUI check |
 DOC |
 Author(s) |
||||||||
 Flag |
 PAR!! |
 ACC! |
 NLS |
 UNT |
 FUZ |
ESC |
 Note |
 |
 |
||
| Portuguese, Portugal |  |
 4 |
1 |
 |
5 | Manuel Menezes de Sequeira, Luis X. B. Mourão, Paulo Justino | |||||
This test is necessary to pass or you can expect crashing of TSVN - specially true when you use longer type as is in English like %s instead of %d, %ld instead of %d, etc. Also having more parameters lead to crash TSVN. When TSVN not crash, the information is still wrong. For example number instead of text.
PASS
This is accessibility test. Passing this test is recommended. If you are interesting in more details about accelerator key overlapping I may enable such test for your language, but in fact there not too much to do against it. According Luebbe and Stefan there is no problem about it you just have to use accelerator more time to select element and then use enter or space for activate button.
PASS
This tests if new line style from pot match localized new line style. This test may have false positives when English text has new line style inconsistence. Using more lines for Native when English use just one is also alowed for most of translation even here reported.
| Index | Line | English | Line | Native |
| 1 | Note that the name of the folder you are importing does not appear in the repository, only its contents. For example, create the following folder structure: <screen>\n C:\\Temp\\New\\trunk\n C:\\Temp\\New\\branches\n C:\\Temp\\New\\tags\n </screen> Import <filename>C:\\Temp\\New</filename> into the repository root, which will then look like this: <screen>\n /trunk\n /branches\n /tags\n </screen> |
1266 | Tem em conta que o nome da pasta que estás a importar não aparecerá no repositório, só o seu conteúdo. Por exemplo, cria a seguinte estrutura de pastas:<screen>\n C:\\Temp\\New\\trunk\n C:\\Temp\\New\\ramos\n C:\\Temp\\New\\etiquetas\n </screen> Importa o <filename>C:\\Temp\\New</filename> para a raiz do repositório, que então terá o seguinte aspecto: <screen>\n /trunk\n /ramos\n /etiquetas\n </screen> |
|
| 2 | Assuming your repository is located in <filename>c:\\repos\\TestRepo</filename>, and your server is called <filename>localhost</filename>, enter: <screen>\n svn://localhost/repos/TestRepo\n </screen> when prompted by the repo browser. |
1463 | Assumindo que o teu repositório está localizado em <filename>c:\\repos\\TestRepo</filename>, e o teu servidor chama-se <filename>localhost</filename>, introduz: <screen>\n svn://localhost/repos/TestRepo\n </screen> quando fores solicitado pelo navegador de repositório. |
|
| 3 | You can also increase security and save time entering URLs with svnserve by using the --root switch to set the root location and restrict access to a specified directory on the server: <screen>\n svnserve.exe --daemon --root drive:\\path\\to\\repository\\root\n </screen> Using the previous test as a guide, svnserve would now run as: <screen>\n svnserve.exe --daemon --root c:\\repos\n </screen> And in TortoiseSVN our repo-browser URL is now shortened to: <screen>\n svn://localhost/TestRepo\n </screen> Note that the --root switch is also needed if your repository is located on a different partition or drive than the location of svnserve on your server. |
1467 | Podes também aumentar a segurança e poupar tempo a introduzir URLs com o svnserve usando o parâmetro --root para indicares a localização raiz e restringir o acesso a determinada pasta no servidor: <screen>\n svnserve.exe --daemon --root drive:\\path\\to\\repository\\root\n </screen> Usando o teste prévio como guia, o svnserve irá agora correr como: <screen>\n svnserve.exe --daemon --root c:\\repos\n </screen> E no TortoiseSVN o nosso URL do navegador de repositório está agora encurtado para: <screen>\n svn://localhost/TestRepo\n </screen> Observa que o parâmetro --root é também preciso no caso de o teu repositório estar localizado numa partição ou unidade diferente, da localização do svnserve no teu servidor. |
|
| 4 | To install svnserve as a native windows service, execute the following command all on one line to create a service which is automatically started when windows starts. <screen>\n sc create svnserve binpath= \"c:\\svnserve\\svnserve.exe --service\n --root c:\\repos\" displayname= \"Subversion\" depend= tcpip\n start= auto\n </screen> If any of the paths include spaces, you have to use (escaped) quotes around the path, like this: <screen>\n sc create svnserve binpath= \"\n \\\"C:\\Program Files\\Subversion\\bin\\svnserve.exe\\\"\n --service --root c:\\repos\" displayname= \"Subversion\"\n depend= tcpip start= auto\n </screen> You can also add a description after creating the service. This will show up in the Windows Services Manager. <screen>\n sc description svnserve \"Subversion server (svnserve)\"\n </screen> |
1483 | Para instalar o svnserve como um serviço nativo do Windows, executa o seguinte comando , numa só linha, para criar um serviço que será automáticamente arrancado quando o Windows arrancar. <screen>\n sc create svnserve binpath= \"c:\\svnserve\\svnserve.exe --service\n --root c:\\repos\" displayname= \"Subversion\" depend= tcpip\n start= auto\n </screen> Se algum dos caminhos incluir espaços, terás de inserir entre aspas, do seguinte modo: <screen>\n sc create svnserve binpath= \"\n \\\"C:\\Program Files\\Subversion\\bin\\svnserve.exe\\\"\n --service --root c:\\repos\" displayname= \"Subversion\"\n depend= tcpip start= auto\n </screen> Podes também adicionar uma descrição após a criação do serviço. Essa será mostrada no gestor de serviços do Windows. <screen>\n sc description svnserve \"servidor Subversion (svnserve)\"\n </screen> |
Total:4
This tests if all strings has been translated. Translated mean that there in native string set. If English and native are same it is not marked as not translated, this just can happen.
PASS
String marked as fuzzy is not in final shape.
PASS
This test check if all escaped chars are known and its using match with English. Even you get red here it may be legal for your language.
This test is in developing now. Ignored are: \r \n (wee new line style test) and \".
| Index | Line | English | Line | Native |
| 1 | A file conflict occurs when two or more developers have changed the same few lines of a file. As Subversion knows nothing of your project, it leaves resolving the conflicts to the developers. Whenever a conflict is reported, you should open the file in question, and search for lines starting with the string <literal><<<<<<<</literal>. The conflicting area is marked like this: <screen>\n <<<<<<< filename\n your changes\n =======\n code merged from repository\n >>>>>>> revision\n </screen> Also, for every conflicted file Subversion places three additional files in your directory: <placeholder-1/> |
3008 | Um conflito de ficheiro ocorre quando dois ou mais programadores alteraram o mesmo conjunto de linhas de um ficheiro. Como o Subversion não tem nenhum conhecimento do teu projecto, ele deixa a tarefa de resolução de conflitos aos programadores. Cada vez que um conflito é relatado, deverás abrir o ficheiro em questão e procurar por linhas que comecem pela string <literal><<<<<<<</literal>. A área em conflito está marcada do seguinte modo: <screen>\n \t<<<<<<< filename\n \t\tyour changes\n \t=======\n \t\tcode merged from repository\n \t>>>>>>> revision\n \t</screen> Também para cada ficheiro em conflito, o Subversion coloca três ficheiros adicionais na tua pasta: <placeholder-1/> |
Total:1
PASS
Next few sections informs about duplicate accelerators in translation. There is no reason to be stressed about this, but some translators like to know it. In a fact even English translation contains duplicate.
RC checking is currently off for this language. If you like enable it for your translation drop me an email.
