- This topic has 56 replies, 7 voices, and was last updated Mar 8-3:48 pm by Anonymous.
-
Posts
-
Robin
Thank you very much for your hint, anticapitalista! This was the real thing in the right place!
Works like a charm. This does not only cover the compiling of .po files to .mo but also editing and checking strings. Moreover it has a graphical user interface already, so there is nothing left to be desired. Actualy this is an adequate replacement for my proposed script and the test suite. We just need to write a guidance for antix volunteer translators how the workflow of translating and testing the result is to be organised best.
Only slight drawback: it takes about 32 MiB of aditional space… This is a lot on some systems. But it compensates this fully by the functionality it brings to us.
It looks like I have been way to long rummaging in the engine room of systems, always trying to use tools from command line first… Meanwhile not always the better choice, as we can see here.
Robin
- This reply was modified 2 years, 3 months ago by Robin.
- This reply was modified 2 years, 3 months ago by Robin.
Windows is like a submarine. Open a window and serious problems will start.
marcelocripe
Guys, I have difficulties to be able to follow the progress of extremely constructive conversations on this important topic created by Robin.
As everyone knows, I depend on the translations of the internet translators to try to understand the conversations, so, a lot of information ends up being lost in the translations or due to my ability to adapt the translated texts to be able to understand them.
skidoo wrote:
Additionally, according to someone’s recent post (marcelocripe?), A transifex set does not yet exist for every script.Yes @skidoo, this was “My last request that I made year 2020 to the creator and developers of antiX”. In addition, parts / programs that do not have antiX translation and their respective files are not available for translation on the transifex website. We still have the opposite situation, there are the program files translated on the transifex website, but the programs are not translated in the antiX ISO, for example “unplugdriveshpo”. There are other examples that I won’t be able to list right now …
It is as if they are not taking advantage of all the potential available on the transifex website. Which is unfortunate, as I spent hours, days, weeks and a few months have passed on the transifex website. And it is not yet finished. As other Brazilian colleagues are getting involved and collaborating with suggestions on improving antiX translations, I will be implementing it. I search for these suggestions through the Telegram, WhatsApp groups, by E-mail or by private message here on the forum. Bearing in mind that not everyone has the time or interest in collaborating.
skidoo wrote:
Really, I haven’t “studied it” ~~ as a monoglotAnyway, something we have in common … (laughs), that is, we are able to fluently use only one language. Remember this …, how many people are exposed here every day using a language they do not speak? (I wouldn’t know how to order a glass of water in your language. But I recognize several words in English due to the volunteer work on the transifex website)
Xecure wrote:
This is the third time this comes up. Can we ask the translators/reviewers to NOT block translation strings? They don’t seem to review it properly, so it is better if they are not blocked.
DO I need to register in the MX Linux forum to make them aware that this blocking is detrimental to project translations? It doesn’t seem that the ones reviewing translations ever enter this forum (even though the transifex project has “antiX” in its name), so I assume the one in charge is also an MX linux follower.Several areas are blocked from multiple files. They were blocked by the reviewers. I have identified several minor errors in translations in the Portuguese area of Portugal, I think most are typos. I made a list and sent it to the user / reviewer “zeh” here on the forum via private message and on the transifex website on January 12th, 2021. After several days, I didn’t get any answers. So I made contact with another reviewer, hugok, luckily I got answers, the reviewer made the corrections, but kept it blocked.
Xecure, I didn’t understand the long and complicated process that you had to learn to allow the “antix-wifi-switch” to be translated into several languages. I know you worked hard and always work hard to be well understood. I wonder, why does everything need to be so complicated? I hope @Robin can understand all this complicated process … I know that it is fundamental in the evolution of the internationalization of scripts in the antiX community and antiX itself, because he has programming knowledge, knowledge in three languages and still has the will to do and is already doing … The transifex website is not the easiest platform I had to learn to operate, but it is easier to use than GitLab or GitHub which seem to be made to be difficult.
Now I leave my other request to the antiX Developers and Programmers, to send the files from the “antix-wifi-switch” to the transifex site, I will copy the texts from the GitLab pt-br file to the transifex with great pleasure.
Robin wrote:
Unbelievable! This bug has survived in french version for 6 years now!There are other similar problems … Sometimes when I update antiX, the menus are in Portuguese Portuguese / European Portuguese, even though I use antiX in Brazilian Portuguese. Other times the menus will have texts in English after the update. The operating system is trilingual (laughs), it is better to laugh than cry … Guys, this is not a criticism, please understand my words translated by the internet translator. They are the “bugs”.
I share with all the difficulties andcommunication challenges … It is not enough to translate or adapt texts, it is necessary that the sentences make complete sense, that they can be understood by as many people as possible and the most difficult is to fit in the little space available in the text area programs. This problem I exemplified in the other topic.
The essential elements for efficient communication to occur are:
Sender = It is the one who initiates the communicative process, because it transmits the message. (AntiX Developers, Programmers and Translators)
Receiver = It is the target of the sender, being the one who receives the message. (AntiX users spread across planet Earth)
Message = It can be a fact, ideas or even emotions, that is, it is the content contained in the communication. (Texts contained in antiX Linux and this forum)
Channel = It is the means by which the message is sent from the sender to the receiver. (CLI programs, but especially antiX Linux GUI programs. For communication to occur, all texts must be very well written in a clear and objective language and be properly translated)Other sites on the elements of the communication process:
https://www.educamaisbrasil.com.br/enem/lingua-portuguesa/elementos-da-comunicacao https://www.helpguide.org/articles/relationships-communication/effective-communication.htm https://www.skillsyouneed.com/ips/what-is-communication.htmlWe are on the right track, as developers are participating in this important topic that goes against the future of antiX.
marcelocripe
(Original text in Brazilian Portuguese)———-
Pessoal eu tenho dificuldades para poder acompanhar o andamento das conversas extremamente construtivas deste importante tópico criado pelo Robin.
Como todos sabem eu dependo das traduções dos tradutores da internet para tentar compreender as conversas, então, muitas informações acabam se perdendo nas traduções ou devido a minha capacidade de adaptar os textos traduzidos para poder compreendê-los.
skidoo wrote:
Additionally, according to someone’s recent post (marcelocripe?), a transifex set does not yet exist for every script.Sim @skidoo, este foi “O meu último pedido que eu fiz ano de 2020 ao criador e aos desenvolvedores do antiX”. Além das partes/programas que não possuem tradução do antiX e dos seus respectivos arquivos não estarem disponíveis para serem traduzidos no site transifex. Ainda temos a situação inversa, existem os arquivos dos programas traduzidos no site transifex, mas os programas não estão traduzidos na ISO do antiX, por exemplo o “unplugdriveshpo”. Existem outros exemplos que não poderei listar neste momento…
É como se não estivessem aproveitando todo o potencial que está disponível site transifex. O que é lamentável, pois eu desprendi horas, dias, semanas e já são se passaram alguns meses no site transifex. E ainda não está concluído. A medida que outros colegas Brasileiros estão se envolvendo e colaborando com sugestões na melhoria das traduções do antiX eu vou implementando. Eu busco estas sugestões através dos grupos de Telegram, WhatsApp, por E-mail ou por mensagem particular aqui no fórum. Haja vista que nem todas as pessoas possuem disponibilidade de tempo ou mesmo interesse em colaborar.
skidoo wrote:
Really, I haven’t “studied it” ~~ as a monoglotEnfim, algo que temos em comum … (risos), ou seja somos capazes de usar fluentemente apenas uma língua. Lembre-se disso…, quantas pessoas aqui se expõe todos os dias utilizando um idioma que não domina? (Eu não saberia pedir um copo d’ água em seu idioma. Mas reconheço várias palavras em inglês devido ao trabalho voluntário no site transifex)
Xecure wrote:
This is the third time this comes up. Can we ask the translators/reviewers to NOT block translation strings? They don’t seem to review it properly, so it is better if they are not blocked.
DO I need to register in the MX Linux forum to make them aware that this blocking is detrimental to project translations? It doesn’t seem that the ones reviewing translations ever enter this forum (even though the transifex project has “antiX” in its name), so I assume the one in charge is also an MX linux follower.Várias áreas estão bloqueadas de vários arquivos. Foram bloqueadas pelos revisores. Eu identifiquei vários pequenos erros das traduções da área Português de Portugal, eu acho que a maioria são de erros de digitação. Eu fiz um lista e enviei para o usuário/revisor “zeh” aqui no fórum via mensagem particular e no site transifex no dia 12 de Janeiro de 2021. Após vários dias, não obtive repostas. Então eu fiz contato com outro revisor, o hugok, felizmente obtive repostas, o revisor fez as correções, mas manteve bloqueado.
Xecure, eu não compreendi todo o longo processo e complicado que você teve que aprender para permitir que o “antix-wifi-switch” possa ser traduzido para vários idiomas. Eu sei que você se esforçou e sempre se esforça para ser muito bem compreendido. Eu me pergunto, por que tudo precisa ser tão complicado? Eu espero que o @Robin consiga compreender todo este processo complicado … Eu sei que ele é fundamental na evolução da internacionalização de scripts da comunidade antiX e do próprio antiX, pois ele possui conhecimentos de programação, conhecimentos em três idiomas e ainda possui vontade de fazer e já está fazendo… O site transifex não é a plataforma mais fácil que tive que aprender a operar, mas é mais fácil de utilizar do que o GitLab ou o GitHub que parecem que foram feitos para serem difíceis.
Agora deixo o meu outro pedido para os Desenvolvedores e Programadores do antiX, enviarem os arquivos do “antix-wifi-switch” para o site transifex, eu copiarei os textos do arquivo pt-br do GitLab para o transifex com muito prazer.
Robin wrote:
Unbelievable! This bug has survived in french version for 6 years now!Existem outros problemas semelhantes … Às vezes quando atualizo o antiX, os menus ficam em idioma Português de Portugal/Português Europeu, mesmo eu utilizando ao antiX em idioma Português do Brasil. Outras vezes os menus ficam com textos em idioma Inglês após a atualização. O sistema operacional fica trilíngue (risos), é melhor rir do que chorar … Pessoal, isso não é uma critica, por favor, compreendem as minhas palavras traduzidas pelo tradutor da internet. São os “bugs”.
Compartilho com todos as dificuldades e os desafios na comunicação… Não basta fazer a tradução ou a adaptação dos textos, é preciso que as frases façam sentido completo, que possam ser compreendidas ao maior número possível de pessoas e o mais difícil é caber no pouco espaço disponível na área de texto dos programas. Este problema eu exemplifiquei no outro tópico.
Os elementos essenciais para que ocorra uma comunicação eficiente são:
Emissor = É aquele que dá início ao processo comunicativo, pois transmite a mensagem. (Desenvolvedores, Programadores e Tradutores do antiX)
Receptor = É o alvo do emissor, sendo quem recebe a mensagem. (Usuários do antiX espalhados pelos planeta Terra)
Mensagem = Pode ser um fato, ideias ou até mesmo, emoções, ou seja, é o conteúdo contido na comunicação. (Textos contidos no antiX Linux e neste fórum)
Canal = É o meio pelo qual a mensagem é enviada do emissor para o receptor. (O programas em CLI, mas em especial os programas em GUI do antiX Linux. Para a comunicação ocorrer, todos os textos precisam estar muito bem escritos com uma linguagem clara e objetiva e estarem devidamente traduzidos)Outros sites sobre os elementos do processo de comunicação:
https://www.educamaisbrasil.com.br/enem/lingua-portuguesa/elementos-da-comunicacao https://www.helpguide.org/articles/relationships-communication/effective-communication.htm https://www.skillsyouneed.com/ips/what-is-communication.htmlEstamos no caminho certo, pois os desenvolvedores estão participando deste importante tópico que vai de encontro ao futuro do antiX.
marcelocripe
(Texto original em Português do Brasil)
anticapitalista
About translations and antiX (I’m not interested in the translated MX apps).
transifex is where we want all our native apps to be translated so translators will have to use that platform.
Otherwise it would be a nightmare trying to coordinate across git/transifex/personal emails etc.
Now, transifex is far from perfect, I know.This is how we deal with translations.
1. All existing antiX apps and many in-house scripts in /usr/local/bin have already been ‘localised’ via gettext.
If a user writes a script that they want included in antiX, then it is up to the script writer to localise it (with assistance if required).2. Any new translations/changes/edits will be added to the apps package every so often. I download the >95% translated files, use poedit to create the .mo files and add them to the packages.
3. Some packages that go in /etc/skel will not show up on an installed system. eg any changes to the main menu (IceWM/fluxbox/JWM).
For some languages, eg pt_BR there are several translators over at transifex. Talk to each other about the ‘best’ translation. You will have to collaborate with each other.
I cannot decide since I only speak English and Greek and would have no idea who is ‘right’.If you find that the translations haven’t made it after a few weeks, send me a pm here or better over at transifex.
HTH
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Hello all!
Well, without having read the recently added posts still (I’ll catch up on them during the next hour) I’ll introduce the script I had proposed in post above “should set up a test suite
“. It’s considered to be a draft still (Ver 0.13), so everything is possible. After I’ll have read your last answer, anticapitalista, I’ll check whether it fits into your concept of dealing with antiX translations and try to adapt it to your approach.
This script is meant to make it possible most easily for antiX users and members of antiX community who have good knowledge in their native language and would be willing and able to improve the translations, but often are unexperienced in the handling of computer programs beyond klicking some nice icons. I tried to automatise the process so anybody can make the way through it, once script will be grown up a little more.The “poedit” program anticapitalista has had recommended, is to be installed previously, and you should start the script from command line window in a test folder for now, since it will write the result of decompiling a chosen .mo file to .po from system to this folder. Please let me know, if I am about to reinvent the wheel again… just in case there are readymade programs available I am not aware of, which provide all this management for unexperienced users already.
And please let me know what you think of this new approach.
Best Regards
Robin.Windows is like a submarine. Open a window and serious problems will start.
Xecure
@anticapitalista
Thanks for explaining how things are done (and, as always, thanks for all your work)If a user writes a script that they want included in antiX, then it is up to the script writer to localise it (with assistance if required).
Ok. I will later today prepare a git merge request for antix-goodies including the adaptation of antix-wifi-switch for translation and the two translated .mo files I have right now.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.marcelocripe
anticapitalista wrote:
About translations and antiX (I’m not interested in the translated MX apps).I have a question, if any file you have in your name mx – ???? is used in antiX?
Several MX Linux files have the original text in English language identical to the files that do not have mx – ????. Since it would not make sense for me to be looking for what is for exclusive use of antiX and what is for exclusive use in MX Linux, I dedicate myself to doing my best in the same way in all files.Now, what doesn’t make any sense is to have in the files that don’t have in your name mx – ???? the “Copyright (c) MX Linux” credits. If you really need to quote MX in Copyright, at least you can write “Copyright (c) antiX / MX Linux” or “Copyright (c) MX Linux / antiX”, what do you think of this suggestion?
anticapitalista wrote:
transifex is where we want all our native apps to be translated so translators will have to use that platform.Glad you prefer this platform and use it as a standard, the transifex is simpler to learn to operate than in more difficult ones that I mentioned earlier.
anticapitalista wrote:
For some languages, eg pt_BR there are several translators over at transifex. Talk to each other about the ‘best’ translation. You will have to collaborate with each other.That is exactly how I try to do it, talking to other Brazilians interested in antiX and MX Linux, unfortunately few participate in the respective forums. I also try to chat with the other translators who are actively participating in the transifex website. Some of the Brazilians recently arrived here on the forum are collaborating with suggestions through the Telegram and WhatsApp groups that we created or through the groups that had been created for a long time.
What I ask you to do is to guide the reviewers of all languages to unlock the areas that have been blocked by themselves. I understand that older people have your trust, but for me and others to be able to collaborate, we need to have access to the files that have been blocked.
I am grateful to fellow Portuguese translators who implemented in pt_BR the writing of texts in pt (Portugal), it was less complicated / difficult for me to know antiX with Portuguese Portuguese texts than if they were all in English. As with the Spanish language (from Spain) which is different from what is spoken and written in each country in South America, the same is true with the Portuguese language which is spoken and written in Brazil. I researched about languages and communication, countries that were colonies, most had the language of the colonizing country influenced by several other languages, including indigenous and African languages (due to slavery).
But since I registered on the transifex site in August 2020, I strive to do the best I can in each sentence, as I know that it is through communication that will allow more users to like antiX or not. Even though I depend exclusively on Internet translators to translate antiX texts and my ability to adapt translated texts to make sense in my language until December 2020, today (January 2021) I can count on the support of other colleagues Brazilians who know the English language, some of them know how to speak the English language. So I ask you not to block the texts on the transifex website.
anticapitalista wrote:
I cannot decide since I only speak English and Greek and would have no idea who is ‘right’.Both are right, each in their own way they are right, pt or pt_BR, what matters is the official form of writing in each country.
I’m glad you’re bilingual, you can communicate a lot easier than I can. When defining the spaces and sizes of the English text areas, remember your Greek language, it consumes much more space than the English language text. Remember my little research I posted on this topic.
Each one collaborates as he can with the constant improvement of his creation, antiX.
Thank you for all your explanations.
marcelocripe
(Original text in Brazilian Portuguese)———-
anticapitalista wrote:
About translations and antiX (I’m not interested in the translated MX apps).Eu possuo uma dúvida, se algum arquivo que possui no seu nome mx-???? é utilizado no antiX?
Vários arquivos do MX Linux possuem o texto original em idioma Inglês idêntico aos arquivos que não possuem mx-????. Como não faria sentido eu ficar procurando do que é de uso exclusivo do antiX e o que é de uso exclusivo no MX Linux, eu me dedico em fazer o meu melhor da mesma maneira em todos os arquivos.Agora, o que não faz sentido algum é ter nos arquivos que não possuem no seu nome mx-???? os créditos “Copyright (c) MX Linux”. Se realmente é necessário citar o MX no Copyright, ao menos é possível escrever “Copyright (c) antiX/MX Linux” ou “Copyright (c) MX Linux/antiX”, o que acha desta sugestão?
anticapitalista wrote:
transifex is where we want all our native apps to be translated so translators will have to use that platform.Que bom que você prefere esta plataforma e a utiliza como padrão, o transifex é mais simples de aprender operar que em outras mais difíceis que citei anteriormente.
anticapitalista wrote:
For some languages, eg pt_BR there are several translators over at transifex. Talk to each other about the ‘best’ translation. You will have to collaborate with each other.É exatamente assim que eu tento fazer, conversando com as outros Brasileiros interessados no antiX e no MX Linux, infelizmente poucos participam dos respectivos fóruns. Eu tento, também, conversar com os outros tradutores que participam ativamente no site transifex. Alguns dos Brasileiros recém chegados aqui no fórum estão colaborando com sugestões através dos grupos de Telegram e WhatsApp que criamos ou através dos grupos que já estavam criados a bastante tempo.
O que eu peço a você é para orientar os revisores de todos os idiomas a desbloquearem as áreas que foram bloqueados por eles mesmos. Eu compreendo que as pessoas mais antigas possuem a sua confiança, mas para eu e para os outros poderem colaborar, nós precisamos ter acesso aos arquivos que foram bloqueados.
Eu sou grato aos colegas tradutores Portugueses que implementaram na área pt_BR a escrita dos textos em pt (Portugal), foi menos complicado/sofrível para mim conhecer o antiX com os textos em idioma Português de Portugal do que se estivessem todos os em idioma Inglês. Como ocorrem com o idioma Espanhol (da Espanha) que é diferente ao falado e escrito em cada país da América do Sul, o mesmo ocorre com o idioma Português que é falado e escrito no Brasil. Eu pesquisei sobre os idiomas e sobre comunicação, países que foram colonias, a maioria tiveram o idioma do pais colonizador influenciado por diversos outros idiomas, inclusive com os idiomas indígenas e africanos (devido a escravidão).
Mas desde que eu fiz o cadastro no site transifex, em agosto de 2020, eu me empenho para fazer o melhor possível em cada frase, pois eu sei que é através da comunicação que irá permitir que mais usuários gostem do antiX ou não. Mesmo eu dependendo exclusivamente dos tradutores da internet para traduzir os textos do antiX e da minha capacidade de adaptar os textos traduzidos para poderem fazer sentido em meu idioma até Dezembro de 2020, hoje (janeiro de 2021) eu posso contar com o apoio de outros colegas Brasileiros que conhecem o idioma Inglês, inclusive, alguns deles sabem falar em idioma Inglês. Por isso eu peço para não bloquear os textos do site transifex.
anticapitalista wrote:
I cannot decide since I only speak English and Greek and would have no idea who is ‘right’.Ambos estão certos, cada um a sua própria maneira estão certos, pt ou pt_BR, o que vale é a forma oficial da escrita em cada país.
Eu fico contente que você seja bilíngue, você consegue se comunicar muito mais fácil do que eu. Quando for definir os espaços e tamanhos das áreas de textos em idioma Inglês, lembre-se do seu idioma Grego, ele consome muito mais espaço do que o texto em idioma Inglês. Lembre-se da minha pequena pesquisa que postei neste tópico.
Cada um colabora como pode com a melhoria constante da sua criação, o antiX.
Obrigado por todas as suas explicações.
marcelocripe
(Texto original em Português do Brasil)Hello @Xecure,
this is what it looks like in 17.4 still. Don’t see what you’ve described, so I’ll stick to packaging files manually. Or do I miss something?From Spacefm (antiX 19.3)
Attachments:
Windows is like a submarine. Open a window and serious problems will start.
marcelocripe
Excuse me @Xecure,
Yes Robin, this is the way. In the next window that will open the program, you have an option with several possible formats for compressing files and folders, search for “.zip”.
Just remembering that “.zip” files are easy to unzip in antiX and Windows.
marcelocripe
(Original text in Brazilian Portuguese)———-
Peço licença ao @Xecure,
Sim Robin, é este o caminho. Na próxima janela que será aberta do programa, possui uma opção com vários formatos possíveis de compactação de arquivos e pastas, busque “.zip”.
Só lembrando que arquivos “.zip” são fáceis de serem descompactados no antiX e no Windows.
marcelocripe
(Texto original em Português do Brasil)Thank you, marcelocripe!
I was focused to the context-menu only, not to the file save dialog. Now I’ve found the selection at bottom of the following window.Windows is like a submarine. Open a window and serious problems will start.
Hello @anticapitalista, @Xecure, @skidoo, @Dave
drawing the consequences from your comments to my first approach I started to read manuals about the standard way of dealing with translations in antiX (and modern linux in general). These in combination wiht the experiences I made while writing the first script this thread is starting with, led me to the insight, the procedure described by anticapitalista some posts above lacks of one important step: testing. You didn’t mention this in your guide at all. And obviously most of the translations have never been tested by the translator before applying them to transifex. But when it comes to translating strings containing separators, line-breaks and dealing with different sentence structures in some foreign languages (e.g. “Klammerstellung” in de and nl language) or extremely different length of expression this is not easy to master as long as you can’t test the result of your efforts immediately and as often as necessary until everything is in its place, before applying changes to transifex. Hence I started with a draft some posts above, and here comes the first fully functioning version, covering the main workflow only. There are some more methods to be integrated, which will follow in next versions. I’ve taken some screenshots in order to give you a feeling for the workflow. Experienced users may set the switch in line 18 to 1 in order to save you from some extra clicks. For some additional informational output in terminal window you may set switch on line 17 to 1, for standard operation to 0 (zero). It is set to 1 in the uploaded file.
Comments and review appreciated. Tested on 17.4, needs testing on 19x series.
This script is not localised itself yet, I’ll have to figure out what exactly I’ll have to do utilising gettext. Please make do with english language only for now.
Robin.
Windows is like a submarine. Open a window and serious problems will start.
Screenshots:
1. starting when working folder exists. Doesn’t show up when folder is not present. (is omitted for experienced users)
2. chose language
3. choes application
4. start editor (is omitted for experienced usersAttachments:
Windows is like a submarine. Open a window and serious problems will start.
5. Editor starts (poedit) after corresponding .mo file was decompiled.
6. After user has saved edited file and closed editor a specialy prepared terminal window pops up. This window will use all language files as set in system, except the freshly edited one. This doesn’t change anything on the system, everything happens just in a virtually generated language only.
7. Example of antixscreenshot with edited language file. Translator may test every single function after translation, before applying his changes to transifex.
8. If test is satisfactory, he may write file back to system structure again, or reopen editor (poedit) to make corrections.This way translator can be safe from submitting bug-causing translations to transifex.
- This reply was modified 2 years, 3 months ago by Robin.
- This reply was modified 2 years, 3 months ago by Robin.
Attachments:
Windows is like a submarine. Open a window and serious problems will start.
Anonymous
I mentioned in another post recently:
skidoo is confused by the fact that
screenshot from the antiX21alpha boot menu shows 62 LANG entries (+1 for Default)
vs
this list shows only 61 total https://gitlab.com/antiX-Linux/antiX-Gfxboot/-/blob/master/Input/common/isolinux/languagesHere, I’m also wondering:
When maintaining antiX translations, do you (all, collectively) just drop//discard//ignore fr_FR
???
fr_FR
fr_BE
fr_CA
fr_CH
When maintaining antiX translations, do you (all, collectively) just drop//discard//ignore fr_FR
???
fr_FR
fr_BE
fr_CA
fr_CHOf course not. This script does actually support any language found in directory /usr/share/locale on the system it is running on. The fact that a language script has to support not only two letter language code is one of the things I’ve learned while writing the first approach, while corresponding with marcelocripe. He was in need of pt_BR instead of pt only, so I did a rewrite to use four letters. But this new one makes use of the complete ID exactly as found in folder.
One of the problems left over is: I didn’t find a way to derive the correct correlation of output “locale -a” (“locale | grep LANG=”) to the folder structure in /usr/share/locale. This would be necessary to determine the correct folder to be copied/linked to the virtual language folder used for testing environment. This doesn’t concern basic functionality, since the list of languages (and subsequent the .mo file to be edited) is directly derived from folder structure and not from output of locale.
BUT I need to know, which folder is used in the UI on user system, when locale gives a dedicated ID, since this is what should be used as a template for the virtual test language folder. To find out how the correlation between “locale” and the folder structure is done in antiX will have to be one of the next steps. For now I use for creating the environment for the file in test actually the two letter code only, which may result in all other commands in test window (except the one referring to the edited .mo file) may come up in another flavour of the users language. The result of the test should not be concerned by this in any way, so I consider it as a surface blemish only.All the programs I had tested with the script started flawlessly using the edited language file: galculator, libreoffice, clawsmail, gimp, geany, frescobaldi, leafpad and many others. BUT how to test menu entries of antiX main menu I’ll have to figure out, I guess this will be quite a tough nut to crack. This would probably mean to start a second instance of it without touching the original one.
- This reply was modified 2 years, 3 months ago by Robin. Reason: typo
Attachments:
Windows is like a submarine. Open a window and serious problems will start.
Of course not.
Hopefully this screenshot will illustrate WHY i ask that question.
Where are the files for all the other 5-characters-long locales hiding?
- You must be logged in to reply to this topic.
