marcelocripe
Hello Robin.
The second step would be to put the translations to transifex. Again, the correct place I feel would be antix-community-contributions at transifex, since this space is meant exactly for projects created and driven by people of community like yours.
I hope PPC agrees with your suggestions.
All the scripts that I sent to the PPC prepared to receive translations have at least the .pot file, .po in pt-BR and the .mo in pt-BR. Not all texts in pt-BR were implemented in FT10, unfortunately… Some scripts I didn’t adapt and that’s why I don’t know if the .pot files exist.
In addition to the .pot, .po files, we need to send the .desktop files to Transifex to benefit from the greatest possible amount of translations made by native humans or if it is in the interest of the PPC, we can use their “magical” translation script automatically and sending the translated file to Transifex.
Some suggestions on procedures and organization I have presented in this topic Suggested Review of .desktop File Translations.
Maybe it’s a good idea to create another file similar to antix-desktop-files, but this new one will only contain the texts of the .desktop files that are not “official” from antiX 21. It would be a file to receive all the texts of the .desktop files which are in GitLab and which are not the programs which are in the antiX 21 full ISO. Or if it is better for future administration to include all the texts of all the .desktop files (official or not) in a single file, then this will be the best option.
Upgrading from antiX 19 to antiX 21 also caused me a lot of problems that I still haven’t had time to try to research and solve (or ask for help on the forum), for example, the sound not working and the terrible loss of automatic translations in HexChat and Thunderbird email.
It doesn’t count for me, whether I personally use it or not, there are many people out there who will use it. which is enough to encourage me to help. And it looks great. Good work, PPC!
That’s what really matters, Robin, even if it doesn’t work for you, it can work for other people and your help is very necessary and important.
Also I noticed that neither my aCSTV nor my automatic IRC hexchat translation script work on antiX 21 anymore, due to version incompatibility to upgraded versions of some helper programs.
In addition to these terrible losses, there are other programs that were standard in antiX that were discontinued, the application submenus became smaller with the loss of some programs and as anticapitalsita had written in another topic, several programs would have to be ported to the new technology, I think it was something about GTK3.
Marcelo does know quite well meanwhile how to prepare a bash script for transifex.
It’s not like that…, I’m learning from you. If I can’t do something, I ask for your help, however HexChat is critical for fast and instant communication.
I have never done this packaging myself, probably will learn some day.
I’m also interested in learning how to create .deb and AppImage packages.
– – – – –
Olá Robin.
The second step would be to put the translations to transifex. Again, the correct place I feel would be antix-community-contributions at transifex, since this space is meant exactly for projects created and driven by people of community like yours.
Eu espero que o PPC concorde com as suas sugestões.
Todos os scripts que eu enviei para o PPC preparados para receberem traduções possuem no mínimo o arquivo .pot, .po em pt-BR e o .mo em pt-BR. Nem todos os textos em pt-BR foram impementados no FT10, infelizmente… Alguns scripts eu não adaptei e por isso eu não sei se existem os arquivos .pot.
Além dos arquivos .pot, .po, precisamos enviar para o Transifex os arquivos .desktop para serem beneficiados com a maior quantidade possível de traduções feitas por humanos nativos ou se for do interesse do PPC, poderemos utilizar o seu script “mágico” de tradução automática e envio do arquivo traduzido para o Transifex.
Algumas sugestões sobre procedimentos e organização eu apresentei neste tópico Suggested Review of .desktop File Translations.
Talvez seja uma boa ideia criar um outro arquivo semelhante ao antix-desktop-files, mas neste novo conterá apenas os textos dos arquivos .desktop que não são “oficiais” do antiX 21. Seria um arquivo para receber todos os textos dos arquivos .desktop que estão no GitLab e que não são os programas que estão na ISO full do antiX 21. Ou se é melhor para a administração futura incluir todos os textos de todos dos arquivos .desktop (oficiais ou não) em um único arquivo, então esta será a melhor opção.
A atualização do antiX 19 para o antiX 21 também me causou muitos problemas que ainda não tive tempo para tentar pesquisar e de resolver (ou pedir ajuda no fórum), por exemplo, o som que não funciona e a terrível perda das traduções automáticas no HexChat e do e-mail do Thunderbird.
It doesn’t count for me, whether I personally use it or not, there are many people out there who will use it. which is enough to encourage me to help. And it looks great. Good work, PPC!
É isso que realmente importa, Robin, mesmo se não servir para você, poderá servir para as outras pessoas e a sua ajuda é sim muito necessária e importante.
Also I noticed that neither my aCSTV nor my automatic IRC hexchat translation script work on antiX 21 anymore, due to version incompatibility to upgraded versions of some helper programs.
Além destas terríveis perdas, existem outros programas que eram padrão no antiX que foram descontinuados, os submenus aplicativos ficaram menores com a perda de alguns programas e como o anticapitalsita havia escrito em um outro tópico, vários programas teriam que ser portados para a nova tecnologia, eu acho que era algo sobre o GTK3.
Marcelo does know quite well meanwhile how to prepare a bash script for transifex.
Não é bem assim…, eu estou aprendendo com você. Se eu não conseguir fazer alguma coisa, eu peço a sua ajuda, contudo o HexChat é fundamental para a comunicação rápida e instantânea.
I have never done this packaging myself, probably will learn some day.
Eu também tenho interesse em aprender a criar pacotes .deb e AppImage.