Re: [pt-BR] Question about language tool home page.
On 2016-07-16 21:43, Matheus Poletto wrote: > I was looking in https://www.languagetool.org [1] so i found the > different versions of translations like to /pt/, /uk/ ... As im doing > the pt-BR i would like ask you if is possible to translate and create > a pt-BR version, cause some words from /pt/ page are not same we use > in Brazil, like the following word example: "actual" in > https://www.languagetool.org/pt/ [2] is a error to pt-BR. The source of the website is in git at https://github.com/languagetool-org/languagetool-website/tree/master/www You can just copy the 'pt' folder to 'pt-BR' and commit and push it, it will appear automatically at languagetool.org about 5 minutes later. I see that /pt/ doesn't have much content, so adding more for pt-BR would be appreciated. You could have a look at the other pages, e.g. the German one has several examples of errors LT can detect. Regards Daniel -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev ___ Languagetool-devel mailing list Languagetool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/languagetool-devel
Re: [pt-BR] Question about language tool home page.
Err, was running the site locally, and copied the link from the wrong tab kinoshita.eti.br/2016/07/17/reasons-for-having-pt-and-ptbr-in-a-software/ Bruno From: Bruno P. Kinoshita <brunodepau...@yahoo.com.br> To: development discussion for LanguageTool <languagetool-devel@lists.sourceforge.net> Sent: Sunday, 17 July 2016 4:35 PM Subject: Re: [pt-BR] Question about language tool home page. Hi, If it is just for spelling differences, I agree that it makes sense to keep a single page. However, it is important to note that Portuguese from Portugal and from Brazil also have different grammar rules. I just wrote a quick (and not well revised) blog post about it: http://localhost:8080/2016/07/17/reasons-for-having-pt-and-ptbr-in-a-software But the tl;dr is that there are spelling differences, different words for the same meaning, and also grammar differences. Looking at examples from the /pt/ page: - Por favor vê a lista de problemas comuns se experienciares problemas. Descarrega versões anteriores ou builds diários. 1. The verb vê, from a Brazilian Portuguese POV, is in the wrong conjugation. It should be "veja".2. We do not use "experienciares". It would be "experienciar" in the imperative form, or written in another way (e.g. se você notar, se ocorrer algum, etc)3. Descarrega is used only when you are unloading things from somewhere. Like unloading a truck. - Extra do Navegador 1. Normally it would be Extensão para o Navegador, or maybe use Plug-in, Add-on. - Usar o LanguageTool localmente requer o Java 8 ou acima. 1. The verb in infinitive, in the beginning of the sentence, sounds weird. "Para usar" (like "In order to use") sounds more natural in Brazilian Portuguese.2. The "acima", in Brazilian Portuguese, would also be incorrect. It could be "superior" or "mais recente". - Builds diários não testados, do estado actual de desenvolvimento, estão disponíveis na directoria de snapshots (CHANGES.txt). Versões antigas continuam disponíveis na directoria de download. 1. s/actual/atual as mentioned before in this thread2. directoria does not exist in Brazilian Portuguese. It sounds like diretoria (school principal room, or company director department). In this case, it would be written as "estão disponíveis no diretório de snapshots". So we change the word, plus the gender of the noun. I think the point is, that if it would demand too much work to maintain both pages, then I'm +1 for keeping just /pt/. But if it's easy to maintain, then I'd be +1 to add the page. Just my 0.02 cents Bruno From: Jaume Ortolà i Font <jaumeort...@gmail.com> To: development discussion for LanguageTool <languagetool-devel@lists.sourceforge.net> Sent: Sunday, 17 July 2016 9:14 AM Subject: Re: [pt-BR] Question about language tool home page. 2016-07-16 21:43 GMT+02:00 Matheus Poletto <motav...@gmail.com>: Hi guys; I was looking in https://www.languagetool.org so i found the different versions of translations like to /pt/, /uk/ ... As im doing the pt-BR i would like ask you if is possible to translate and create a pt-BR version, cause some words from /pt/ page are not same we use in Brazil, like the following word example: "actual" in https://www.languagetool.org/pt/ is a error to pt-BR. Hi, So it is "actual" (Portugal) vs. "atual" (Brazil). It doesn't seem reasonable to have a different page for these small differences. There are differences like these in other languages (in English: analyze vs. analyse), but we don't duplicate pages. I suggest adding a section explaining the differences between variants that LanguageTool is able to detect and live with these tiny spelling differences. Regards, Jaume Ortolà -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev ___ Languagetool-devel mailing list Languagetool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/languagetool-devel -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev___ Languagetool-devel mailing list Languagetool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/languagetool-devel
Re: [pt-BR] Question about language tool home page.
Hi, If it is just for spelling differences, I agree that it makes sense to keep a single page. However, it is important to note that Portuguese from Portugal and from Brazil also have different grammar rules. I just wrote a quick (and not well revised) blog post about it: http://localhost:8080/2016/07/17/reasons-for-having-pt-and-ptbr-in-a-software But the tl;dr is that there are spelling differences, different words for the same meaning, and also grammar differences. Looking at examples from the /pt/ page: - Por favor vê a lista de problemas comuns se experienciares problemas. Descarrega versões anteriores ou builds diários. 1. The verb vê, from a Brazilian Portuguese POV, is in the wrong conjugation. It should be "veja".2. We do not use "experienciares". It would be "experienciar" in the imperative form, or written in another way (e.g. se você notar, se ocorrer algum, etc)3. Descarrega is used only when you are unloading things from somewhere. Like unloading a truck. - Extra do Navegador 1. Normally it would be Extensão para o Navegador, or maybe use Plug-in, Add-on. - Usar o LanguageTool localmente requer o Java 8 ou acima. 1. The verb in infinitive, in the beginning of the sentence, sounds weird. "Para usar" (like "In order to use") sounds more natural in Brazilian Portuguese.2. The "acima", in Brazilian Portuguese, would also be incorrect. It could be "superior" or "mais recente". - Builds diários não testados, do estado actual de desenvolvimento, estão disponíveis na directoria de snapshots (CHANGES.txt). Versões antigas continuam disponíveis na directoria de download. 1. s/actual/atual as mentioned before in this thread2. directoria does not exist in Brazilian Portuguese. It sounds like diretoria (school principal room, or company director department). In this case, it would be written as "estão disponíveis no diretório de snapshots". So we change the word, plus the gender of the noun. I think the point is, that if it would demand too much work to maintain both pages, then I'm +1 for keeping just /pt/. But if it's easy to maintain, then I'd be +1 to add the page. Just my 0.02 cents Bruno From: Jaume Ortolà i Font <jaumeort...@gmail.com> To: development discussion for LanguageTool <languagetool-devel@lists.sourceforge.net> Sent: Sunday, 17 July 2016 9:14 AM Subject: Re: [pt-BR] Question about language tool home page. 2016-07-16 21:43 GMT+02:00 Matheus Poletto <motav...@gmail.com>: Hi guys; I was looking in https://www.languagetool.org so i found the different versions of translations like to /pt/, /uk/ ... As im doing the pt-BR i would like ask you if is possible to translate and create a pt-BR version, cause some words from /pt/ page are not same we use in Brazil, like the following word example: "actual" in https://www.languagetool.org/pt/ is a error to pt-BR. Hi, So it is "actual" (Portugal) vs. "atual" (Brazil). It doesn't seem reasonable to have a different page for these small differences. There are differences like these in other languages (in English: analyze vs. analyse), but we don't duplicate pages. I suggest adding a section explaining the differences between variants that LanguageTool is able to detect and live with these tiny spelling differences. Regards, Jaume Ortolà -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev ___ Languagetool-devel mailing list Languagetool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/languagetool-devel -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev___ Languagetool-devel mailing list Languagetool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/languagetool-devel
[pt-BR] Question about language tool home page.
Hi guys; I was looking in https://www.languagetool.org so i found the different versions of translations like to /pt/, /uk/ ... As im doing the pt-BR i would like ask you if is possible to translate and create a pt-BR version, cause some words from /pt/ page are not same we use in Brazil, like the following word example: "actual" in https://www.languagetool.org/pt/ is a error to pt-BR. Best regards, Matheus Poletto -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev___ Languagetool-devel mailing list Languagetool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/languagetool-devel
