Git Product home page Git Product logo

Comments (13)

PeterBBBBB avatar PeterBBBBB commented on June 27, 2024

Should be fixed in 1.6.
Please reopen if you still see problems here.

from winff.

marcelocripe avatar marcelocripe commented on June 27, 2024

Should be fixed in 1.6.
Please reopen if you still see problems here.

Thank you very much!

I found a problem in https://github.com/WinFF/winff/tree/master/winff-windows-packaging/Docs, the file WinFF.pt.pdf that I translated is in Brazilian Portuguese (pt_BR) and not in European Portuguese (pt). You must include "pt_BR" in the file name "WinFF.pt.pdf" for "WinFF.pt_BR.pdf". If a native speaker of the "pt" language reads the document, this person may complain that the texts are not in the "pt" language and may want to make changes to the texts in the wrong file. If a native of Portugal wants to create another file with texts in "pt", from the file I created, it will be very good, as we will have two documents, one from the "original" language and the one I made from the language variant.

There is an ocean between Portugal and Brazil, the Brazilian Portuguese language has suffered several influences over the years from several other languages, such as: African languages, native indigenous languages, Italian, German, French and others. Texts in "pt_BR" sound strange to native speakers of "pt" and vice versa. But it's better to have a translation than none.


Should be fixed in 1.6.
Please reopen if you still see problems here.

Muito obrigado!

Eu encontrei um problema em https://github.com/WinFF/winff/tree/master/winff-windows-packaging/Docs, o arquivo WinFF.pt.pdf que eu traduzi está em idioma Português do Brasil (pt_BR) e não em Português Europeu (pt). É preciso incluir "pt_BR" no nome do arquivo "WinFF.pt.pdf" para "WinFF.pt_BR.pdf". Se um nativo do idioma "pt" o ler o documento, esta pessoa poderá reclamar dizendo que os textos não são em idioma "pt" e poderá querer fazer as alterações nos textos do arquivo errado. Se um nativo de Portugal quiser criar um outro arquivo com textos em "pt", a partir do arquivo que eu criei, será muito bom, pois teremos dois documentos, um do idioma "original" e o que eu fiz da variante do idioma.

Existe um oceano entre Portugal e Brasil, o idioma Português do Brasil sofreu diversas influencias aos longos dos anos de vários outros idiomas, como por exemplo: idiomas africanos, dos nativos indígenas, italiano, alemão, francês e outros. Os textos em "pt_BR" soam estranhos para os nativos do "pt" e vice-versa. Mas é melhor ter uma tradução do que não ter nenhuma.

from winff.

PeterBBBBB avatar PeterBBBBB commented on June 27, 2024

The issue here is that from the Documentation tab under the Help (Adjuda) menu,
WinFF only launches pdf files with a 2 character locale code.
So a WinFF.pt_BR.pdf will never be seen, and will default to WinFF.en.pdf.
As you say "it's better to have a translation than none." !!

I was alerted to this problem by the comment in the debian/rules file regarding the Spanish pdf
https://salsa.debian.org/pascal-team/winff/-/blob/master/debian/rules

It would of course be better if WinFF used 5 character locales for launching the pdfs, but until we have more than one dialect for any language, the point is moot.

Thanks for your translation. I'll include your desktop file in the next release.
Let me know if you would like a name added to the Sobre -> Obrigardo box.

from winff.

marcelocripe avatar marcelocripe commented on June 27, 2024

WinFF only launches pdf files with a 2 character locale code.
So a WinFF.pt_BR.pdf will never be seen, and will default to WinFF.en.pdf.
As you say "it's better to have a translation than none." !!

This same problem occurs with the translation file "winff.pt_BR.po", as I explained in the initial text of this topic.
This means that the Brazilian user needs to manually edit the names of the ".po" files to be able to have the "pt_BR" translation in the graphical interface. And both "pt" and "pt_BR" users will have access to the "pt_BR" translation of the help manual.

It would of course be better if WinFF used 5 character locales for launching
the pdfs, but until we have more than one dialect for any language, the point > is moot.

What we talked about here cannot be forgotten, because it would be very sad to lose the "pt_BR" translation if a native of Portugal made changes to the texts and images because they were unaware of our conversation.

Thanks for your translation. I'll include your desktop file in the next release.

I'm grateful that you use the "winff.desktop" file that the antiX community works on to have translations for different languages. Menus also need to be translated. We maintain translations of several ".desktop" files that are gradually being accepted by program developers. Unfortunately, not all developers accept having the ".desktop" file translated.
The ".desktop" files that the antiX community works on to have translations of different languages are in these repositories:

https://gitlab.com/Robin-antiX/antix23-desktop-files/-/tree/main/applications?ref_type=heads
https://gitlab.com/antix-contribs/antix-desktop-files
https://app.transifex.com/anticapitalista/antix-development/antix23-desktop-files/

At some point we will have translations reviewed by native speakers of other languages that are not yet in the "winff.desktop" file and this will be very good for WinFF.

Let me know if you would like a name added to the Sobre -> Obrigardo box.

Are you serious? You will include my name "marcelocripe" in the acknowledgments. That for me would be an honor.
I suggest adding the names of the other people who are involved in WinFF who have yet to be added.

Thank you very much!


WinFF only launches pdf files with a 2 character locale code.
So a WinFF.pt_BR.pdf will never be seen, and will default to WinFF.en.pdf.
As you say "it's better to have a translation than none." !!

Este mesmo problema ocorre com o arquivo da tradução "winff.pt_BR.po", conforme eu expliquei no texto inicial deste tópico.
Isso significa que o usuário do Brasil precisa editar manualmente os nomes os arquivos ".po" para poderem ter na interface gráfica a tradução "pt_BR". E tanto os usuário "pt", quanto os usuário "pt_BR" terão acesso a tradução "pt_BR" do manual de ajuda.

It would of course be better if WinFF used 5 character locales for launching
the pdfs, but until we have more than one dialect for any language, the point > is moot.

Não pode ser esquecido o que conversamos aqui, porque seria muito triste perder a tradução "pt_BR" se um nativo de Portugal fizer as alterações nos textos e nas imagens por não saber da nossa conversa.

Thanks for your translation. I'll include your desktop file in the next release.

Eu sou grato por você utilizar o arquivo "winff.desktop" que a comunidade antiX trabalha para ter as traduções de diversos idiomas. Os menus também precisam ser traduzidos. Nós mantemos as traduções de diversos arquivos ".desktop" que aos poucos estão sendo aceitos pelos desenvolvedores dos programas. Infelizmente, nem todos os desenvolvedores aceitam ter o arquivo ".desktop" traduzido.
Os arquivos ".desktop" que a comunidade antiX trabalha para ter as traduções de diversos idiomas estão nestes repositórios:
https://gitlab.com/Robin-antiX/antix23-desktop-files/-/tree/main/applications?ref_type=heads
https://gitlab.com/antix-contribs/antix-desktop-files
https://app.transifex.com/anticapitalista/antix-development/antix23-desktop-files/

Eu algum momento nós teremos as traduções revisadas por nativos de outros idiomas que ainda não estão no arquivo "winff.desktop" e isso será muito bom para o WinFF.

Let me know if you would like a name added to the Sobre -> Obrigardo box.

Você está falando sério? Você vai incluir o meu nome "marcelocripe" nos agradecimentos. Isso para mim seria um honra.
Eu sugiro adicionar os nomes das outras pessoas que estão envolvidas no WinFF que ainda foram adicionadas.

Muito obrigado!

from winff.

PeterBBBBB avatar PeterBBBBB commented on June 27, 2024

Please post your full output of
locale -v

What happens if you rename your .po file to
winff.pt_BR.UTF-8.po ?

from winff.

marcelocripe avatar marcelocripe commented on June 27, 2024

manutencao@antix1:~
$ locale -v
LANG=pt_BR.UTF-8
LANGUAGE=
LC_CTYPE="pt_BR.UTF-8"
LC_NUMERIC="pt_BR.UTF-8"
LC_TIME="pt_BR.UTF-8"
LC_COLLATE="pt_BR.UTF-8"
LC_MONETARY="pt_BR.UTF-8"
LC_MESSAGES="pt_BR.UTF-8"
LC_PAPER="pt_BR.UTF-8"
LC_NAME="pt_BR.UTF-8"
LC_ADDRESS="pt_BR.UTF-8"
LC_TELEPHONE="pt_BR.UTF-8"
LC_MEASUREMENT="pt_BR.UTF-8"
LC_IDENTIFICATION="pt_BR.UTF-8"
LC_ALL=
manutencao@antix1:~
$

from winff.

marcelocripe avatar marcelocripe commented on June 27, 2024

Conversor de Multimidia WinFF em pt_BR no antiX 23 30-09-2023

from winff.

marcelocripe avatar marcelocripe commented on June 27, 2024

What happens if you rename your .po file to
winff.pt_BR.UTF-8.po ?

With the file name "winff.pt_BR.UTF-8.po" the language "pt_BR" was successfully displayed in the WinFF Multimedia Converter graphical interface.

Could you test this solution on another GNU/Linux other than antiX Linux 23?

$ inxi -S
System:
Host: antix1 Kernel: 6.1.42-antix.1-amd64-smp arch: x86_64 bits: 64
Desktop: IceWM v: 3.4.2 Distro: antiX-23_x64-full Arditi del Popolo 27
August 2023

Thank you very much!


What happens if you rename your .po file to
winff.pt_BR.UTF-8.po ?

Com o nome do arquivo "winff.pt_BR.UTF-8.po" o idioma "pt_BR" foi exibido com sucesso na interface gráfica do Conversor de Multimídia WinFF.

Você conseguiria testar esta solução em um outro GNU/Linux diferente do antiX Linux 23?

$ inxi -S
System:
Host: antix1 Kernel: 6.1.42-antix.1-amd64-smp arch: x86_64 bits: 64
Desktop: IceWM v: 3.4.2 Distro: antiX-23_x64-full Arditi del Popolo 27
August 2023

Muito obrigado!

from winff.

PeterBBBBB avatar PeterBBBBB commented on June 27, 2024

I see what the problem is now.
I'll fix the code, so that 2 char & 5 char locale po files both load properly.
(Need to chop off the .UTF-8 part of the LANG code)

from winff.

marcelocripe avatar marcelocripe commented on June 27, 2024

I'm very happy to know that the problem will be fixed and that my language helped you identify the problem.


Eu fico muito contente em saber que o problema será corrigido e que o meu idioma te ajudou a identificar o problema.

from winff.

PeterBBBBB avatar PeterBBBBB commented on June 27, 2024

po file loading for 5 char locales should be fixed in 1.6.2

from winff.

marcelocripe avatar marcelocripe commented on June 27, 2024

Please don't forget to correct the file from "WinFF.pt.pdf" to "WinFF.pt_BR.pdf".


Por favor, não se esqueça de corrigir o arquivo de "WinFF.pt.pdf" para "WinFF.pt_BR.pdf".

from winff.

PeterBBBBB avatar PeterBBBBB commented on June 27, 2024

I'm not changing the pdfs. I mentioned this earlier. The source is still WinFF.pt_BR.odt, so its obvious what dialect it is, should someone else wish to make changes. Doing the rename you suggest results in European Portuguese users seeing the English document. (Same applies to Spanish)

from winff.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.