- This topic has 78 replies, 14 voices, and was last updated Jan 1-8:23 am by Anonymous.
-
Posts
-
marcelocripe
Skidoo,
View the “background.jpg” and “panel.png” imagefiles.
Understand that SLiM has no ability to display dynamically inserted text translations.I downloaded the file and found the images “background.jpg”, “panel.png”, “slim.theme” and “slim-install.conf”.
I don’t know if the translation is not good or if it is my lack of understanding on the subject “SLiM”. I believe it is my lack of understanding. His translated words came to me as “SLiM is not able to display dynamically inserted text translations”, if dynamically it is what other programs do to get the translation files to be displayed according to the defined language. So I have some ideas, I just don’t know if they are feasible to implement or not.
If the texts that are displayed by the Slim program, with only the inserted texts “Username” and “Password” just from a “panel.png” image, then it is easier to do the translation. If the image is made available in the quality that should be used in antiX with the correct size, each contributor to the antiX translations can edit the texts “Username” and “Password” directly in the image. I just need to be told which programs I can edit the image with so that there is no loss in image quality the moment the file is saved.
If my thinking is correct, it would suffice if there was a “slim-pt-br” and it would display the “pt-br” image containing the text in the Brazilian Portuguese language, as follows: “Nome de Usuário” and “Senha” as well as a slim and an image and for each language. Standard Slim displays text in English and could still be identified by slim-en.
Is this feasible? Or it just “scrapes” the antiX ISO unnecessarily.
Could slim receive information on which image to display via another script? Imagine in the installation process a script inserting a line informing which image should be displayed for the installed system. This is just an idea, since I still don’t know how to write a script.
I’m just thinking of a simple way to solve a small barrier to allow antiX to be in fact multi-lingual in most of the operating system as possible.
marcelocripe
(Original text in Brazilian Portuguese)———-
Skidoo,
View the “background.jpg” and “panel.png” imagefiles.
Understand that SLiM has no ability to display dynamically inserted text translations.Eu baixei o arquivo e encontrei as imagens “background.jpg”, “panel.png”, “slim.theme” e “slim-install.conf”.
Eu não sei se é a tradução que não ficou boa ou se é a minha falta de compreensão sobre o assunto “SLiM”. Eu acredito que seja a minha falta de compreensão. As suas palavras traduzidas chegaram para mim como sendo que “o SLiM não tem capacidade de exibir traduções de texto inseridas dinamicamente”, se dinamicamente for aquilo que os outros programas fazem de ir buscar os arquivos de tradução para serem exibidos conforme o idioma definido. Então eu tenho algumas ideias, eu só não sei se são viáveis de serem implementadas ou não.
Se os textos que são exibidos pelo programa Slim, sendo somente os textos inseridos “Username” e “Password” apenas de uma imagem “panel.png”, então fica mais fácil fazer a tradução. Se disponibilizarem a imagem na qualidade que deverá ser utilizada no antiX com o tamanho correto, cada colaborador das traduções do antiX poderá editar os textos “Username” e “Password” diretamente na imagem. Eu só precisaria que me dissessem com quais programas eu posso fazer a edição da imagem para que não ocorra perda na qualidade da imagem no momento que o arquivo for salvo.
Se o meu pensamento estiver correto, bastaria que houvesse um “slim-pt-br” e este exibisse o a imagem “pt-br” contendo o texto em idioma Português do Brasil, da seguinte forma: “Nome de Usuário” e “Senha”, bem como um slim e uma imagem e para cada idioma. O Slim padrão exibe o texto em idioma inglês e ainda poderia estar identificado por slim-en.
Isso é viável? Ou só “enxeria” a ISO do antiX de forma desnecessária.
O slim poderia receber a informação de qual imagem deverá exibir através de outro script? Imagine no processo de instalação um script inserir uma linha informando qual imagem deverá ser exibida para o sistema instalado. Essa é só uma ideia, já que eu ainda não sei escrever script.
Eu só estou pensando em uma forma simples de resolver uma pequena barreira para permitir que o antiX seja de fato multi-idiomas na maior parte possível do sistema operacional.
marcelocripe
(Texto original em idioma Português do Brasil)Anonymous
“not dynamic” meaning “static, unchanging”
If you buy a camera and snap a photo of an English sign, the text in the photo will be Engish text.
If you tell the sign “but I speak a different language”, the text of the sign will still be displayed in English.
When the SLiM login screen is displayed, it is unaware of YOUR language. The displayed text is static, unchanging.
_______________
Toward understanding, I did direct you to visit the themes directory and inspect (view) the imagefiles which are loaded for the SLiM screen. Apparently you have not done so ~~ if you had, the meaning should have been OBVIOUS.
would suffice if there was a “slim-pt-br” and it would display the “pt-br” image containing the text in the Brazilian Portuguese language, as follows: “Nome de Usuário” and “Senha” as well as a slim and an image and for each language. Standard Slim displays text in English and could still be identified by slim-en.
Is this feasible?
No, it is not feasible.
For SLiM it is outright impossible.Could slim receive information on which image to display via another script?
No, it could not.
Here, I will reiterate:
If you tell the sign “but I speak a different language”, the text of the sign will still be displayed in English.To achieve locale-specific messaging on the login screen, you (as local sysadmin, or antiX overall) must replace slim with an alternative login manager program. The only candidate program available as an alternative is “LightDM“.
.
.
.
_________________________
edited to add this aside:
I have onhand a copy of the sourcecode for LightDM version 1.2.6, cloned from a git.devuan.dev project repository. Its code is chock-full of frilly (and corporate-workstation-centric) “features”. After paring away “guest logins” support, along with systemd and apparmor support… I still would not be comfortable using it on my local machines until/unless I nixed its (support for, aka dependence upon) “accountservice“. Hmm, grabbing that link, I just noticed that the lightdm package only Suggests (doesn’t Depend) accountservice…marcelocripe
Skidoo,
Apparently you have not done so ~~ if you had, the meaning should have been OBVIOUS.
I did not do this because I did not understand if it is to run the file “slim.theme” in antiX, or if it is to open the code. I just read the code. “Slim.theme” reminds me of CSS formatting files for HTML pages.
So if the “photo from a camera”, according to your example, represents the image from the “panel.png” file, I believe it can be modified. Or not?
It makes no sense, not being able to replace an image that is used in a program, especially in the “Linux world”. You have revised antiX inside out! They develop fantastic programs that consume the least possible resources (RAM and processor) and that we only have available in antiX or MX Linux.
I know we’re both talking about details … I’m going to write the way I see HTML forms, I know very well that what you program is not just HTML. If “Username”, “Password” and “Login” are not texts of similar form entries <label for = “name”> or <input type = “text” id = “name” /> can be edited, but if they are texts, but a “photo”, so why can’t we change the “sign photo”?
The texts translated on the transifex website of the “antix-user_ents” and user-managementpot files practically allow the “panel.png” image to be translated into all languages. Skidoo, I already know that you do not have access to the transifex website, you told me that on the other topic. I’m just indicating where it is possible to copy the texts and so we can prepare an image for each language. The languages Brazilian Portuguese and Portuguese Portuguese I have access to on the transifex website and I can prepare both images, in addition to Spanish, due to the similarity in the writing of the language. There would be three less jobs for the team. I just need to know the font type, the font size and which program I should use to be able to collaborate with a relatively simple activity.
If that can’t be done, that’s fine. At least I tried … I appreciate all your attention and explanations.
marcelocripe
(Original text in Brazilian Portuguese)———-
Skidoo,
Apparently you have not done so ~~ if you had, the meaning should have been OBVIOUS.
Eu não fiz isso porque eu não entendi se é para executar no antiX o arquivo “slim.theme”, ou se é para abrir o código. Eu apenas li o código. O “slim.theme” me lembra arquivos de formatação CSS das páginas HTML.
Então se a “foto de uma câmera”, conforme o seu exemplo, representa a imagem do arquivo “panel.png”, eu acredito que ela possa ser modificada. Ou não?
Não faz sentido, não ser possível substituir uma imagem que é utilizada em um programa, ainda mais no “mundo Linux”. Vocês reviram o antiX do avesso! Desenvolvem programas fantásticos que consomem o mínimo possível de recursos (memória RAM e processador) e que só temos disponíveis no antiX ou no MX Linux.
Eu sei que nós dois estamos conversando sobre detalhes … Eu vou escrever da forma que eu enxergo formulários em HTML, eu sei muito bem que o que vocês programam não são simples HTML. Se “Username”, “Password” e “Login” não são textos de entradas de formulário semelhantes <label for=”nome”> ou <input type=”text” id=”nome” /> podem ser editados, mas se são textos e sim uma “foto”, então porque não poderemos mudar a “foto do letreiro”?
Os textos traduzidos no site transifex dos arquivos “antix-user_ents” e user-managementpot praticamente permitem traduzir para todos os idiomas a imagem “panel.png”. Skidoo, já eu sei que você não possui acesso ao site transifex, você me contou isso no outro tópico. Eu só estou indicando onde é possível copiar os textos e assim podermos preparar uma imagem para cada idioma. Os idiomas Português do Brasil e Português de Portugal eu tenho acesso no site transifex e posso preparar as duas imagens, além do Espanhol, devido a semelhança na escrita do idioma. Seriam três trabalhos a menos para a equipe. Eu só preciso saber o tipo da fonte, o tamanho da fonte e o qual programa que eu devo utilizar para poder colaborar com uma atividade relativamente simples.
Se isso não for possível de ser feito, tudo bem. Ao menos eu tentei … Eu agradeço por toda a sua atenção e explicações.
marcelocripe
(Texto original em Português do Brasil)
anticapitalista
It’s not just a question of translating the words, you have to create the whole image with the newly translated words on them for all slim-themes provided (presently there are 7)
Even then, how difficult is it for non-English speakers to understand these terms at login?Username:
Password:
Press F1 to toggle sessions (OK this could be a bit more difficult)Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
( smiling, not angry, hoping you are smiling as well )
I want a pony.
Sorry, but you can’t have a pony.
But, I want a pony!
It’s impossible. We have no pasture, no barn.
But, we have a postal box!
My pony can live in the postal box, and I promise to feed him and clean the poo and… is dinner ready yet?Yes, dinner will be ready soon, Dear.
But, I’m hungry right now…
I’m just indicating where it is possible to copy the texts and so we can prepare an image for each language.
I do understand your premise.
Also, I can envision using a wrapper script, instead of calling SLiM directly, and code within the wrapper script would:
1) Check whether a “locale” (a keyboard layout?) has been specified on the boot line or specified via the bootmenu
2) If so, check whether a matching (e.g.) /usr/share/slim/themes/THEMENAME/pt_BR/ subdirectory exists
3) If so, prior to calling SLiM, copy (into the parent directory) the files from pt_BR subdirectory
Brian Masinick
I’m just indicating where it is possible to copy the texts and so we can prepare an image for each language.
I do understand your premise.
Also, I can envision using a wrapper script, instead of calling SLiM directly, and code within the wrapper script would:
1) Check whether a “locale” (a keyboard layout?) has been specified on the boot line or specified via the bootmenu
2) If so, check whether a (e.g.) /usr/share/slim/themes/THEMENAME/pt_BR/ subdirectory exists
3) If so, prior to calling SLiM, copy (into the parent directory) the files from pt_BR subdirectory
That’s a reasonable idea. Is it feasible to implement and is there anyone who has the skills and time to implement this?
--
Brian Masinick
Xecure
Is it worth it to translate for each language and create a new boot script and risk bringing even more login problems? If there really is a need for it to be multilingual, I would remove “Username” and “Password” and make the icons much bigger so that they are identifiable. This would solve the translation problem and reduce the amount of work. The user icon will mean “a person -> I identify people with a name -> Here goes my username” and a padlock icon that will clearly reference a need for a key (password) to unlock the user.
BobC already uses them as icons, so the original image can be used in a bigger resolution so it is clear and visible.That would be the simple proposition and solution that would bring the least amount of effort. If this problem is considered serious, this solution should be acceptable.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.BobC, that’s ingenious.
Wait, in some parts of the world, ovals are considered BadLuck.
Maybe we should stick with using rectangular input boxes.Also, in Estonia…
that door symbol might already be associated with “don’t pee on wall. please go here to pee.”Is it worth it to translate for each language and create a new boot script
and risk bringing even more login problems?Per the wrapper script proposed in my post above, I sense no “risk”.
As for “effort”, the burden would rest with the interested parties.
To have your locale-specific set of SLiM resource imagefiles added, you would need to
git yer arse up and (that’s a pun, “git”) submit a merge request to the project repository.
.
oops… if BobC is Estonian, I probably just landed on his ignorelistmake the icons much bigger so that they are identifiable. This would solve the translation problem
Okay, but not too big, else some dimwit “reviewer” is bound to insinuate that it represents an attempt to make fun of the “People of Wal-Mart”. Also, if the icons are too TOO big, there’s an increased risk of someone, somewhere, somehow noticing a curve or line or detail that just doesn’t seem gender-neutral…
BobC
Life is tricky enough 🙂
If someone has better icons that anti would approve of, feel free to post them.
Thanks in advance, if someone will pass BobC the eggnog, kiss his forehead, and let ’em know the icons he has presented are perfectly fine.
- You must be logged in to reply to this topic.
