- This topic has 68 replies, 7 voices, and was last updated Oct 20-12:22 am by marcelocripe.
-
Posts
-
Robin
but I don’t know if it will work correctly in antiX bootloader.
This is what we have to know now, before I can replace/correct/change the resource at transifex, so the downloaded files will be usable. We have to wait for anticapitalistas response, whether the testing was successful, since I have no idea how or where to place the (x)html files to check them in an antiX live environment.
Windows is like a submarine. Open a window and serious problems will start.
anticapitalista
Doing what Robin suggested AND replacing
<br> with <br />works.Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Xecure
Don’t kill me, but while working on this I was thinking of adding the new options for “Use * Kernel” in the “Main Menu Entries” help “page”, as it would be the place where it should be shown. The thing is that this menu entries do not appear in the i386 ISO edition, so users may be confused. Should I continue and just not include these explanations?
- This reply was modified 1 year, 7 months ago by Xecure.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.anticapitalista
Quick way to test your F1 Help document in Virtualbox.
1. Download this file antiX-Gfxboot.tar.gz
2. Decompress the file
3. Download/test your translated .html file by putting it in Help/antiX folder.
4. Rename it en.html (yes, overwrite the old file).
5. cd antiX-Gfxboot and
a) make distclean
b) make test-antiX
This will create an iso file called test-gfxboot.iso
6. Boot this file in Virtualbox, press F1 and see how the translation is.
Esc to get out of the Help menu and Esc again to Poweroff VBox.Each time you test a translated file, you must do steps 3-6.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
anticapitalista
Don’t kill me, but while working on this I was thinking of adding the new options for “Use + Kernel” in the “General Help” help “page”, as it would be the place where it should be shown. The thing is that this menu entries do not appear in the i386 ISO edition, so users may be confused. Should I continue and just not include these explanations?
We probably should add it, but the 2 kernel option is only on the 64bit full edition (or should it be on all 64 bit editions?)
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
anticapitalista
Later tests.
Simply downloading the files from Transifex and replacing
<br> with <br />also works.Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Xecure
We probably should add it, but the 2 kernel option is only on the 64bit full edition (or should it be on all 64 bit editions?)
Makes sense to be only in the full edition.
There is a F1 menu option in the first “Select kernel, Boot from HD, etc.” boot screen. If this loads the same Help menu, could it load instead a different “page” unique only to this multi-kernel case (that would be inside the same .html file but not linked in the “main page”)? This way the same file would be valid for all antiX editions, but this “antiX multi-kernel support Menu” would only show if it is called from this screen.If it is too much work, forget it. Simply adding a few lines to “Main Menu Entries” “page” at the bottom
<em>Use Legacy Kernel</em><br> This option is only available in the 64-bits full release. It will load a Long Term Support kernel with better compatibility with older 64 bit machines. Choose this option if you believe your system will experience compatibility problems with newer kernel releases. <br> <br> <em>Use Modern Kernel</em><br> This option is only available in the 64-bits full release. It will load a more recent Long Term Support kernel with better compatibility with newer hardware. This is the option you should choose for modern computers. <br> <br>should be more than enough.
- This reply was modified 1 year, 7 months ago by Xecure.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.anticapitalista
There is a F1 menu option in the first “Select kernel, Boot from HD, etc.” boot screen. If this loads the same Help menu, could it load instead a different “page” unique only to this multi-kernel case (that would be inside the same .html file but not linked in the “main page”)? This way the same file would be valid for all antiX editions, but this “antiX multi-kernel support Menu” would only show if it is called from this screen.
A better idea perhaps (and it works) is to only have the extra info shown in these F1 Help menus. Saves on size too.
So ‘full’ F1 Help on first screen.
Extra info only on F1 Help after choosing Legacy or Modern.Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Xecure
A better idea perhaps (and it works) is to only have the extra info shown in these F1 Help menus. Saves on size too.
SO, after the translations are done, will we add this info to a different file? I don’t think I understand what you mean or how to help here.
Now that the fix is confirmed, I will edit the html file from transifex and upload there once I am done. I won’t add anything extra for now.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.
marcelocripe
There is another help file topic that has no text, on the line:
Tem um outro tópico do arquivo de ajuda que não possui texto, na linha:
<div id="frugal"> <h3> <a name="frugal">Frugal Install</a>Since we need <br /> tag I#ve switched the resource antiX bootscreen helpmenu to xhtml on transifex now. This is the only way to get the file back from transifex the way we need it and can use it without postprocessing.
All existing translations were saved and transferred to the new file format. Please check whether any errors have occurred.
The invalid
<a name=>tag has proven to be no problem at transifex, they do tolerate it simply.Windows is like a submarine. Open a window and serious problems will start.
anticapitalista
@Robin – thanks.
@all – we will use Robin’s changes at Transifex. Make sure your translations there are correct.
I noticed some French got into the Greek translation – now fixed.So far we have fully translated F1 Help in:
fr, fr_BE, el, pt, pt_BR
thanks to all translators.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
marcelocripe
My thanks to everyone involved for making this achievement possible.
Some suggestions and comments:
-If the file “for_translation_antix-contribs_antix-bootscreen-helpmenu_pt_BR.xhtml” or is downloaded from “for_use_antix-contribs_antix-bootscreen-helpmenu_pt_BR.xhtml”, they can be edited locally and Transifex will accept them. Yesterday I did a quick test with the file “for_use_antix-contribs_antix-bootscreen-helpmenu_pt_BR.xhtml”, I copied and pasted the translations of some sentences and tried to send the file to Transifex, but unfortunately Transifex complained about some entries that I didn’t have modified. Apparently, Robin blocked the possibility of downloading the file “for_use_antix-contribs_antix-bootscreen-helpmenu_pt_BR.xhtml”, so only the file “for_translation_antix-contribs_antix-bootscreen-helpmenu_pt_BR.xhtml” can be used for local editing (off-BR.xhtml). line) that we do not yet know if it will be accepted by Transifex;
-The current text of antix-bootscreen-helpmenu in pt-BR is not complete, it doesn’t have the same content that I sent to the anti-capitalist file with old HTML code. It took me more time to make the texts on the antix-bootscreen-helpmenu the same as the texts I had sent to the anticapitalist;
-I intend to do this test, download the file “for_translation_antix-contribs_antix-bootscreen-helpmenu_pt_BR.xhtml”, make one or two text modifications and try to send the file to Transifex;
-Please Robin, check as soon as possible my comments in the personal message I sent you, it has some details that need to be corrected in the original English language file. For example, line 23 is missing the closing ‘]’ of the ‘[Enter’. These details I had corrected and made available via GitLab, but they were with the old HTML code, it wasn’t XHTML;
-After these tests and fixes are done, I suggest sending to the official antiX Transifex the antix-bootscreen-helpmenu file, due to the greater range of translators. Or make an announcement on the official antiX Transifex asking translators to participate in antiX contrib.
– – – – –
Meus agradecimentos a todos os envolvidos para que esta conquista fosse possível.
Algumas sugestões e comentários:
-Se o arquivo “for_translation_antix-contribs_antix-bootscreen-helpmenu_pt_BR.xhtml” ou for baixado do “for_use_antix-contribs_antix-bootscreen-helpmenu_pt_BR.xhtml”, poderão ser editados localmente e o Transifex os aceitarão. Ontem eu fiz um teste rápido com o arquivo “for_use_antix-contribs_antix-bootscreen-helpmenu_pt_BR.xhtml”, copiei e colei as traduções de algumas frases e tentei enviar para o Transifex o arquivo, mas infelizmente o Transifex reclamou de algumas entradas que eu não havia modificado. Ao que parece, o Robin bloqueou a possibilidade de baixar o arquivo “for_use_antix-contribs_antix-bootscreen-helpmenu_pt_BR.xhtml”, por tanto apenas o arquivo “for_translation_antix-contribs_antix-bootscreen-helpmenu_pt_BR.xhtml” poderá ser utilizado para edição local (off-line) que ainda não sabemos se será aceito pelo Transifex;
-O texto atual do antix-bootscreen-helpmenu em pt-BR não está completo, não possui o mesmo conteúdo que eu enviei para o anticapitalista do arquivo com código HTML antigo. Eu precisei de mais tempo para tornar os textos do antix-bootscreen-helpmenu iguais aos textos que eu havia enviado para o anticapitalista;
-Eu pretendo fazer este teste, baixar o arquivo “for_translation_antix-contribs_antix-bootscreen-helpmenu_pt_BR.xhtml”, fazer uma ou duas modificações no texto tentar enviar o arquivo para o Transifex;
-Por favor, Robin, verifique, assim que for possível os meus comentários na mensagem pessoal que eu te enviei, possui alguns detalhes que precisam ser corrigidos no arquivo original em idioma Inglês. Por exemplo, na linha 23 falta o fechamento ‘]’ do ‘[Enter’. Estes detalhes eu havia corrigido e disponibilizado via GitLab, mas estavam com o código HTML antigo, não era o XHTML;
-Depois que estes testes e correções forem feitas, eu sugiro enviar para o Transifex oficial do antiX o aquivo antix-bootscreen-helpmenu, devido ao alcance maior de tradutores. Ou fazer um anúncio no Transifex oficial do antiX pedindo para os tradutores participarem no contrib do antiX.
Hello all
Some actions are to be taken still, I didn’t have time to write this morning more detailed.
1.) Please check somebody the translation files coming back »for use« now from transifex in the test scenario anticapitalista has described above. I couldn’t perform this testing these days. The old machine I’m working on right now doesn’t have installed virtualbox since I’ve switched it to antiX 19 anymore, and it would be a big battle to make virtualbox run again under antiX 19 on this 32 bit single core probably. This took some days on antiX 17.4.1 I remember (but after this it worked perfectly), and I have right now not the time for this to do. So I restructured the file manually on a theoretical base, following the xhtml design rules. So please somebody else may step in now and prove the new xhtml files are functioning in real life.
2.) No file is blocked for downloading.
Apparently, Robin blocked the possibility of downloading the file “for_use_antix-contribs_antix-bootscreen-helpmenu_pt_BR.xhtml”,
If a file is not downloadable from transifex this means, there are some severe errors in the translations. I was late this morning and I hadn’t time anymore to check the pt and pt_BR translation after uploading before leaving. As you can see from the attached screenshots there is an error in string 210 in pt language. This prevents you from downloading the file “for use”. Same goes for any other files not downloadable »for use«, e.g. pt_BR. (The translation and download was only blocked for a short period this morning completely during the big move procedure from html to xhtml.) You can see all strings with errors immediately when typing »check:error« in the filters field on the left side of screen (see screenshot).
/Update:
Fixed it meanwhile. There were some minor deviations found compared to the original en string text in the translations: entry 143 was missing two quotes within an html tag in pt and pt_BR translation, and string 210 was missing one opening arrow of a tag in the translation so it was not recognised anymore. So again: Be carefully to leave any html-tag untouched while translating, and don’t use anything in your translations which could look like part of such a tag. It will probably get misinterpreted by transifex I reckon. Files should be downloadable now for use again. You could have fixed this yourself, if you had known where to look./3.) French sprinkles in translations:
I noticed some French got into the Greek translation – now fixed.
Sorry for this. It occurred obviously while transferring the strings to the new file format. French happened to be the testing base, the master transfer file for the other languages. So this might have happened in other languages also, please check carefully.
So far we have fully translated F1 Help in:
I’ll work on German and hopefully also Russian translation during next week, now after the correct path of file formatting for transifex was paved.
it has some details that need to be corrected in the original English language file. For example, line 23 is missing the closing ‘]’ of the ‘[Enter’. These details I had corrected and made available via GitLab, but they were with the old HTML code, it wasn’t XHTML
@marcelocripe , could you please check the new xhtml file anticapitalista has merged already from my request on gitlab for these errors, since you do know best what you have found. Maybe some of your findings are fixed anyway, since I also fixed what I noticed during the transfer process. But without exact knowledge about what to search for it is nearly impossible to find the differences from your corrected version to the new xhtml. You may remember still which paragraphs you have mended. Your mending has to be done again in the new xhtml file format. After this it can re-uploaded at transifex (I always check in our testing space at transifex beforehand whether everything works properly, so no strings already translated will get lost). Sorry Marcelo, there is no other way.
/Update: Your finding
»For example, line 23 is missing the closing ‘]’ of the ‘[Enter’.«
is fixed on transifex and gitlab now. It is entry 23, not line number. It is line 50 in the new xhtml file. Merge request for this is already sent./Attachments:
Windows is like a submarine. Open a window and serious problems will start.
marcelocripe
Please, Robin, check the private message I sent you.
In the ‘en.html’ file, I only included the ‘ ] ‘ after the Enter that was missing, I placed some lines, but they are just details to be standardized.Congratulations on the excellent work, as soon as possible I will check the texts on Transifex in pt-BR.
– – – – –
Por favor, Robin, verifique a mensagem particular que eu te enviei.
No arquivo ‘en.html’, eu incluí apenas o ‘ ] ‘ depois do Enter que faltava, posicionei algumas linhas, mas são apenas detalhes para ficarem padronizadas.Parabéns pelo excelente trabalho, assim que for possível eu verificarei os textos no Transifex em pt-BR.
- You must be logged in to reply to this topic.
