- This topic has 20 replies, 10 voices, and was last updated Mar 27-1:57 pm by marcelocripe.
-
Posts
-
Dave
I will agree with that being the safer statement; as well as the not well defined (as in the installed “stuff” does not match the definitions)
The document (https://www.pathname.com/fhs/pub/fhs-2.3.pdf) linked in that severfault thread is fairly comprehensive however.Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
marcelocripe
antiX programs are delivered via, installed via, .deb files
and the content to be delivered via the .deb files is maintained, is “collaborated”, via git project source code repositories. You seem to be asking collaborators and antiX developers to, instead, consume zipfiles which you intend to provide ~~ forcing someone else to extract from zipfile and add it to the appropriate git project source code repository. (just emphasizing/explaining here, not scolding)Skidoo,
I know that “.deb” packages are the standard for Debian-based distributions.
I think I should have included the word “unofficial” in the title of this topic. The scripts for the programs I refer to are both official and non-official programs. The “unofficial” scripts are those created by PPC, Xecure, BobC and other colleagues who develop, eventually they will never become “official”, as they depend on the approval of the antiX developers. They posted on the various topics that are spread across several different subjects. The idea is to combine these solutions, even if they never enter the antiX ISOs, they can be useful for other people, so these scripts need the shortcut icons “.desktop”, they need to be created so that the user does not have to give the command to execute directly in “program_name.sh”, an image to be displayed in the icon and instructions on how to use these three files. As for the “.mo” file, I still have to learn how to operate poedit.Some examples that I will mention are all the solutions created by PPC: control panel, the various implementations of the Tint2 toolbar for Fluxbox that can also be used in IceWM and JWM, for example: Rofi, Weather Forecast, Calendar with Agenda and etc. All of these scripts can be translated and shared for anyone interested in using them.
As I do not have full control over the “Linux Standard Base-LSB” and the organizational structure and file system hierarchy used in antiX, it is best to ask, before distributing and sharing wrong information.
So I started this topic, in order to know in which directory these scripts should or can be placed without any kind of conflict with the official antiX scripts and that mainly are not automatically deleted during an antiX update process, as they are scripts “intruders”.
marcelocripe
(Original text in Brazilian Portuguese)———-
Skidoo,
Eu sei que os pacotes “.deb” são o padrão para as distribuições baseadas em Debian.
Eu acho que eu deveria ter incluído no título deste tópico a palavra “não oficial”. Os scripts dos programas que eu me refiro são tanto dos programas oficiais, quanto dos programas não oficiais. Os scripts “não oficiais” são os criados pelo PPC, Xecure, BobC e outros colegas que desenvolvem, eventualmente nunca se tornarão “oficias”, pois dependem da aprovação dos desenvolvedores do antiX. Eles postaram nos diversos tópicos que estão espalhados em vários assuntos diferentes. A ideia é juntar estas soluções, mesmo que nunca entrem nas ISOs do antiX, podem vir a serem úteis para outras pessoas, por isso estes scripts precisam dos ícones de atalho “.desktop”, precisam ser criados para que o usuário não precise dar o comando de executar diretamente no “nome_do_programa.sh”, de uma imagem para ser exibida no ícone e instruções de como utilizar estes três arquivos. Quanto ao arquivo “.mo” eu ainda tenho que aprender a operar poedit.Alguns exemplos que irei citar são todas as soluções criadas pelo PPC: painel de controle, as diversas implementações da barra de ferramentas Tint2 para o Fluxbox que podem ser utilizadas também no IceWM e no JWM, por exemplo: Rofi, Previsão do Tempo, Calendário com Agenda e etc. Todos estes scripts podem ser traduzidos e compartilhados para quem tiver interesse em utilizar.
Como eu não possuo total domínio sobre o “Linux Standard Base-LSB” e sobre a estrutura organizacional e da hierarquia de sistema de arquivos usada no antiX, o melhor é perguntar, antes de distribuir e compartilhar informações erradas.
Por isso iniciei este tópico, afim de saber em qual diretório estes scripts devem ou podem ser colocados sem que haja qualquer tipo de conflito com os scripts oficiais do antiX e que principalmente não sejam apagados automaticamente durante um processo de atualização do antiX, por serem scripts “intrusos”.
marcelocripe
(Texto original em Português do Brasil)marcelocripe
I thank everyone for their explanations and guidance.
The scripts are available at https://archive.org/details/@marcelocripe?tab=web-archive
marcelocripe
(Original text in Brazilian Portuguese)———-
Eu agradeço a todos por suas explicações e orientações.
Os scripts estão disponíveis na página https://archive.org/details/@marcelocripe?tab=web-archive
marcelocripe
(Texto original em Português do Brasil)Robin
Your script archive looks fine. Congratulations! And archive.org is a good choice indeed.
Just one detail:
As for the “.mo” file, I still have to learn how to operate poedit
poedit isn’t able to edit the compiled “.mo” type of language files directly. They must get decompiled before to “.po” type. But you can use the most recent aCMSTS script, which does the decompilation to “.po” files before editing as well as the recompilation after editing the contents of the files automatically, without the necessity of knowing all the particular commands needed off by heart, which is much more agreeable for occasional users, just wanting to correct some few strings once in a while. In case you want to learn these commands yourself, please read carefully the “history” of this script which led to the recent version, to be found in the linked thread. I have sipped plenty of honey myself from the explanations the participants of the discussion have provided (many thanks again!)
Moreover you might want to learn from the installer script which comes with aCMSTS how to place every file included in the archive in its place in system, so user doesn’t need to do this manually. It is a really simple installer only, which I had created for this task, but for the time being I don’t know anything about the correct way of creating a .deb archive, so this non standard installer is the best reachable solution for now. Will have to learn eventually.
Windows is like a submarine. Open a window and serious problems will start.
zeh
As for the “.mo” file, I still have to learn how to operate poedit.
To translate .mo files you can use virtaal
marcelocripe
Robin, the scripts are not mine. The scripts were made by PPC, Xecure and I found one of them with the name of Skidoo and other people in the credits. What I did was adapt the texts translated by the internet translators for pt-BR. The “unplugdrive-international” that you edited the script and added other languages is also available on the Internet Archive. The “set_time-and_date.sh” is translated into pt-BR as a palliative solution until this program is translatable through the transifex website.
My intention was to organize everything, translate everything possible, include the shortcut icon “.desktop” and a text file explaining how to use the script and “.dektop”. But for that I needed to know what was explained in this topic, where to place these scripts. The orientation was to use the “/ opt” directory, so on a computer that has two or more users, everyone will be able to use the scripts inserted in the “/ opt” folder.
ACMSTS is undoubtedly the best tool to implement the corrections of the translations and still be able to see the result being displayed in the program, before sending it to the transifex website (thank you very much for creating it). And about learning to use the technique you use in the aCMSTS installer is something very interesting for me.
Zeh, thank you for the virtaal’s suggestion.
marcelocripe
(Original text in Brazilian Portuguese)———-
Robin, os scripts não são meus. Os scripts foram feitos pelo PPC, Xecure e eu encontrei em um deles com o nome do Skidoo e de outras pessoas nos créditos. O que eu fiz foi adaptar os texto traduzidos pelos tradutores da internet para o pt-BR. O “unplugdrive-international” que você editou o script e adicionou outros idiomas também está disponível no Internet Archive. O “set_time-and_date.sh” está traduzido para pt-BR como uma solução paliativa até que este programa seja traduzível através do site transifex.
A minha intenção foi de organizar tudo, traduzir tudo que fosse possível, incluir o ícone de atalho “.desktop” e um arquivo de texto explicativo de como utilizar o script e o “.dektop”. Mas para isso eu precisava saber o que foi explicado neste tópico, onde colocar estes scripts. A orientação foi de usar o diretório “/opt”, assim em um computador que tiver dois ou mais usuários, todos poderão utilizar os scripts inseridos na pasta “/opt”.
O aCMSTS é sem dúvidas alguma a melhor ferramenta para implementar as correções das traduções e ainda poder ver o resultado sendo exibido no programa, antes de enviar para o site transifex (muito obrigado por criá-lo). E sobre aprender a usar a técnica que você usa no instalador aCMSTS é sim algo muito interessante para mim.
Zeh, agradeço pelo sugestão do virtaal.
marcelocripe
(Texto original em Português do Brasil)
- You must be logged in to reply to this topic.
