Closed cardpuncher closed 1 year ago
@cardpuncher I added SHARE to FD-NLS. Make sure to commit your translation files there as well. :-)
On a side note... In the future, you don't really need to wait for me to add things. You are familiar with directory structure on FD-NLS and can just issue a pull request with the new directories and files. :-)
On 20.03.2023 15:05, shidel wrote:
@cardpuncher https://github.com/cardpuncher I added SHARE to FD-NLS. Make sure to commit your translation files there as well. :-)
Done :) Since the translations are waiting on FD-NLS, maybe this PR can simply be closed.
On a side note... In the future, you don't really need to wait for me to add things. You are familiar with directory structure on FD-NLS and can just issue a pull request with the new directories and files. :-)
I'm always afraid of breaking stuff, but I'll keep that in mind, thanks.
I'm always afraid of breaking stuff, but I'll keep that in mind, thanks.
That's one nice thing about version control systems like Git and Subversion. If they get messed up, you can revert to an earlier point. :-)
Thanks both. I'll apply this now, but to save your effort in the future just do PRs to https://github.com/shidel/fd-nls and I'll grab them periodically.
@andrewbird, I just added the German translations provided by Wilhelm to https://github.com/shidel/fd-nls/tree/master/share
:-)
@andrewbird, I just added the German translations provided by Wilhelm to https://github.com/shidel/fd-nls/tree/master/share
:-)
Where should I direct improvements to this? My first language is German and I noticed several errors:
Installiert auf Ihrer Festplatte Dateifreigabe-
This reads "installs on/to your disk" whereas the English message is "Installs file-sharing and locking capabilities on your hard disk". I think the "installs capabilities (on your disk)" means it installs the "capabilities" to share "on your disk". To write "installs to your disk" would be wrong.
"Dateifreigabe-Funktionen" is also wrong; "die Freigabe" means "the share" as in an exposed network share. "Dateimitnutzungs-Funktionen" is closer to share as in sharing concurrent file accesses.
Ermögliche eine residente Instanz
Should read "Aktiviere".
Parameter außerhalb des Bereichs!
Should read "außerhalb des zulässigen Bereichs".
Ungültiger Interrupt 2Fh Handler!
Should hyphenate as "Interrupt-2Fh-Handler!"
nicht im AMIS Interrupt gefunden!
Should also hyphenate as "AMIS-Interrupt". And "im" (in the) could be "auf dem" (on the) or "am" (at the).
prüfen Sie die TSR Version.
Hyphenate "TSR-Version".
ist resident installiert, aber aktuell deaktiviert.
Not wrong but I'd swap "aktuell" (currently) for "zurzeit" or "derzeit".
keine freie AMIS Multiplexnummer!
Hyphenate "AMIS-Multiplexnummer".
Ungültiger Interrupt 2Dh Handler!
Hyphenate same as for the int 2Fh message.
nicht entfernbar, die angehängten Handler sind AMIS-inkompatibel.
This reads "the appended handlers are AMIS-incompatible", but the original is "handlers hooked AMIS-incompatible". I'd go for "nicht entfernbar, Handlers sind inkompatibel zu AMIS umgeleitet." I think "umleiten" (divert, redirect) is the usual German choice for "to hook" in this context.
Patchstatus: mittel.
Original is "Patch status: indeterminate." This reads "middle", and is clearly wrong. I'd go for "unbestimmt".
Das Share_installed-Byte
"share_installed" is a variable name that should be reproduced in English in my opinion. "Das Byte share_installed" would be possible.
wurde resident auf Null gesetzt
Original is "Resident patched the share_installed byte", this reads "was residently set to zero". This is also wrong, "resident" is a noun here. So it should read something like "wurde durch das residente TSR auf Null gesetzt" or shorter "wurde durch Resident auf Null gesetzt".
That's all my comments.
Oh, one more thing:
Ungültiger Interrupt 2Dh Handler
Ungültiger should not be capitalised here.
Hi @ecm-pushbx thanks, please send your translations to https://github.com/shidel/fd-nls/tree/master/share. From there I'll collect them periodically. I have them here only so that people could theoretically build share from source, but in reality @shidel will include the latest translations from fd-nls when a package gets built for a FreeDOS release.
Hi @ecm-pushbx, as @andrewbird said, submitting updated translations to the FD-NLS Project is usually the best method for a variety of reasons. However, if you do not want to submit a PR to that project with the changes, I can send Wilhelm a message and ask him to review this thread for improvements to the current version of the German translation. :-)
Hi, ecm-pushbx, feel free to fix this Hyphen etc. I am sure the whole help misses thousands of them. And I hope you could also improve help https://www.bootablecd.de/FreeDOS-Internet-version/help110/en/hhstndrd/base/share.htm By the way, would it be possible to add a use ful help document (one for users / one for programmers that understand what AMIS etc. means) and good examples that USERS can understand? Till now "mußte ich mir das bei share und vielen anderen Programmen aus den Fingern saugen", "die Errorlevel sind undokumentiert oder falsch" etc. etc. FreeDOS...
Try reading the keephook manual, is that somewhat like the help you want?
Not really. Reading it is like reading the "Grundsteuergesetz" of a german federal state for a standard user. I asked an informatic student, he said that they teach it at university, but very very short. What I meant was that the "/? help" is meant for USERS, not for programmers. So this text should be understandable for users (I know that it is almost impossible to write a text that is understandable for everyone.) And "AMIS" and "IRQ /Interrupts" etc. are NOT understandable for everyone. I just looked once again on the text, the expressions are not part of "/? help" but error messages etc. that users usually should not see. I think this is okay. The actual help documentation is extremely short.
As much as I know from Win, share allows other users / computers to access certain folders on a HD via network / maybe other ways too. In most cases a password is required. If FD share behaves in about like this, a better documentation for USERS that do not know about "AMIS, IRQ etc." would be absolutely necessary (I found none at Ibiblio).
In case that I am absolutely wrong with this idea, please please correct me! The following text was written earlier, so if I am wrong, ignore it!
Till today nobody could tell me (and other users via htmlhelp) how to handle file sharing; it would be very important that the documentation would include a good example. Means an example that contains: a) starting with the installed FD1.3 network (of course you can start with "how to create a DOS network?" b) what do I have to do to configure share (permissions etc.) on the local machine that runs share? c) what do I have to do on the other machines that should have access to this machine? c) how do I find the machine with a shared folder with DOS (via IP , ping, or is there a tool to do so) d) can I execute / edit the files from the other machine as I can do it in Win? e) what else can I do with it? f) restrictions etc. It would be nice to have such an updated help so that it can be included in the next htmlhelp. My actual version (see: https://www.bootablecd.de/FreeDOS-Internet-version/help110/en/hhstndrd/base/share.htm ) says nothing about this theme as I had no documentation till now.
Will go and fix the translation including the very important hyphens (no other translation seems to use them) as soon as I know that my basic understanding for share is correct or not (why did the creator of the text write: "enable a resident instance" instead of "activate..."
@ecm-pushbx: I have no problem if you overtake htmlhelp and correct everything ("Dobbie is free now").
Willi
Will go and fix the translation including the very important hyphens (no other translation seems to use them) as soon as I know that my basic understanding for share is correct or not (why did the creator of the text write: "enable a resident instance" instead of "activate..."
She used the terminology that's common in English, and that's to "enable" or "disable" a resident program. I know because I added those messages, the creator is me. However, this maps most cleanly to "aktiviere" and "deaktiviere". And you already used "deaktiviere" for "disable", "aktiviere" for "enable" is just consistent then. Using "(de)activate" in English would also be correct but German "ermögliche" is very unusual for this function (and I can't think of a clean negation).
And "AMIS" and "IRQ /Interrupts" etc. are NOT understandable for everyone.
Fair enough. For example, an IRQ is a (Hardware) "Interrupt ReQuest", unlike what SHARE means by "Interrupt" (Software Interrupt).
I just looked once again on the text, the expressions are not part of "/? help" but error messages etc. that users usually should not see. I think this is okay.
I don't agree entirely, the interrupt-related messages can be seen by users depending on their use cases (eg trying a share /u
command after having installed other TSRs). The "no free AMIS multiplex number" message really is unlikely though.
As much as I know from Win, share allows other users / computers to access certain folders on a HD via network / maybe other ways too. In most cases a password is required. If FD share behaves in about like this, a better documentation for USERS that do not know about "AMIS, IRQ etc." would be absolutely necessary (I found none at Ibiblio).
In case that I am absolutely wrong with this idea, please please correct me! The following text was written earlier, so if I am wrong, ignore it!
What you're describing is network shares again. share
is for allowing concurrent file access (thus "Dateimitnutzung"). One possible reason you'd want to manage concurrent file access properly is if you're using the DOS machine as a network host. (share
only affects local files, on DOS's FAT FS drives.) Another reason could be running a multitasker or another (non-network-related) program that requires proper file sharing semantics.
Running DOS as a network client does not automatically mean there is any need for share
. This is true of MS-DOS v6 share
as well; albeit FreeDOS share
is specific to the FreeDOS kernel it provides the exact same functionality (plus now my extensions to enable, disable, uninstall, list status).
Is this correct now? Especially 0.0?
# 0.0:Installiert Dateimitbenutzungs- und Sperrfähigkeiten auf Ihre Festplatte.\n 0.1: /F:space Weist Dateispeicher (in Byte) für Dateifreigabeinformation zu.\n 0.2: /L:locks Legt die Anzahl der gleichzeitig sperrbaren Dateien fest.\n 0.3:%s [/F:space] [/L:locks]\n 0.4:%s [/F:space] [/L:locks] [/U] [/S] [/O] [/D] [/E]\n 0.5: /U Deinstalliere eine residente Instanz.\n 0.6: /S Zeige Patchstatus und Tabellengrößen an.\n 0.7: /O Nur betreiben wenn bereits resident, nicht installieren.\n 0.8: /D Deaktiviere eine residente Instanz.\n 0.9: /E Aktiviere eine residente Instanz. (Standard).\n
1.0:%s: Parameter außerhalb des zulässigen Bereichs!\n 1.1:%s: ist bereits installiert!\n 1.2:%s: Speicher reicht nicht aus!\n 1.3:%s: ungültiger Interrupt-2Fh-Handler!\n 1.4:%s: installiert.\n
1.5:%s: ist bereits installiert aber nicht am AMIS-Interrupt gefunden!\n 1.6:%s: aktiviert.\n 1.7:%s: deaktiviert.\n 1.8:%s: kann nicht aktiviert werden, prüfen Sie die TSR-Version.\n 1.9:%s: kann nicht deaktiviert werden, prüfen Sie die TSR-Version.\n 1.10:%s: ist resident installiert.\n 1.11:%s: ist resident installiert, aber derzeit deaktiviert.\n 1.12:%s: keine freie AMIS-Multiplexnummer!\n 1.13:%s: Ungültiger Interrupt-2Dh-Handler!\n 1.14:%s: entfernt.\n 1.15:%s: nicht entfernbar, noch nicht installiert.\n 1.16:%s: nicht entfernbar, irgendein Fehler.\n 1.17:%s: nicht entfernbar, Handlers sind inkompatibel zu AMIS umgeleitet.\n 1.18:%s: nicht entfernbar, interner Aushängefehler.\n 1.19:%s: nicht entfernbar, unbekannter Fehler.\n 1.20:%s: Das Programm ist nicht resident!\n
2.0:Programm ist nicht resident!\n 2.1:Patchstatus: vom TSR nicht unterstützt.\n 2.2:Patchstatus: unbestimmt.\n 2.3:Patchstatus: benötigt, Flag bei %04Xh:%04Xh.\n 2.4:Patchstatus: nicht benötigt.\n 2.5:Patchstatus: unbekannt.\n 2.6:Das Byte Share_installed des alten FreeDOS-Kernels wurde auf Null gesetzt.\n 2.7:Das Byte Share_installed des alten FreeDOS-Kernels wurde durch Resident auf Null gesetzt.\n 2.8:Dateitabelle: %u frei / %u gesamt, Sperrtabelle: %u frei / %u gesamt\n 2.9:Dateitabelle: %u gesamt, Sperrtabelle: %u gesamt\n
0.0:Installiert Dateimitbenutzungs- und Sperrfähigkeiten auf Ihre Festplatte.\n
Should be "für Ihre Festplatte".
0.1: /F:space Weist Dateispeicher (in Byte) für Dateifreigabeinformation zu.\n
Should be "Dateimitbenutzungsinformation". Also "Dateispeicher" is confusing but it's an accurate translation, might get around to change that in the original and then you could update it later in the translation.
1.13:%s: Ungültiger Interrupt-2Dh-Handler!\n
You forgot to remove the caps "U" here.
2.6:Das Byte Share_installed des alten FreeDOS-Kernels wurde auf Null gesetzt.\n 2.7:Das Byte Share_installed des alten FreeDOS-Kernels wurde durch Resident auf Null gesetzt.\n
I maintain that the variable name should not be capitalised. If a user were to search for "Share_installed" in the kernel sources they might not find anything whereas "share_installed" would find it.
# 0.0:Installiert Dateimitbenutzungs- und Sperrfähigkeiten für Ihre Festplatte.\n 0.1: /F:space Weist Dateispeicher (in Byte) für Dateimitbenutzungsinformation zu.\n 0.2: /L:locks Legt die Anzahl der gleichzeitig sperrbaren Dateien fest.\n 0.3:%s [/F:space] [/L:locks]\n 0.4:%s [/F:space] [/L:locks] [/U] [/S] [/O] [/D] [/E]\n 0.5: /U Deinstalliere eine residente Instanz.\n 0.6: /S Zeige Patchstatus und Tabellengrößen an.\n 0.7: /O Nur betreiben wenn bereits resident, nicht installieren.\n 0.8: /D Deaktiviere eine residente Instanz.\n 0.9: /E Aktiviere eine residente Instanz. (Standard).\n
1.0:%s: Parameter außerhalb des zulässigen Bereichs!\n 1.1:%s: ist bereits installiert!\n 1.2:%s: Speicher reicht nicht aus!\n 1.3:%s: ungültiger Interrupt-2Fh-Handler!\n 1.4:%s: installiert.\n
1.5:%s: ist bereits installiert aber nicht am AMIS-Interrupt gefunden!\n 1.6:%s: aktiviert.\n 1.7:%s: deaktiviert.\n 1.8:%s: kann nicht aktiviert werden, prüfen Sie die TSR-Version.\n 1.9:%s: kann nicht deaktiviert werden, prüfen Sie die TSR-Version.\n 1.10:%s: ist resident installiert.\n 1.11:%s: ist resident installiert, aber derzeit deaktiviert.\n 1.12:%s: keine freie AMIS-Multiplexnummer!\n 1.13:%s: ungültiger Interrupt-2Dh-Handler!\n 1.14:%s: entfernt.\n 1.15:%s: nicht entfernbar, noch nicht installiert.\n 1.16:%s: nicht entfernbar, irgendein Fehler.\n 1.17:%s: nicht entfernbar, Handlers sind inkompatibel zu AMIS umgeleitet.\n 1.18:%s: nicht entfernbar, interner Aushängefehler.\n 1.19:%s: nicht entfernbar, unbekannter Fehler.\n 1.20:%s: Das Programm ist nicht resident!\n
2.0:Programm ist nicht resident!\n 2.1:Patchstatus: vom TSR nicht unterstützt.\n 2.2:Patchstatus: unbestimmt.\n 2.3:Patchstatus: benötigt, Flag bei %04Xh:%04Xh.\n 2.4:Patchstatus: nicht benötigt.\n 2.5:Patchstatus: unbekannt.\n 2.6:Das Byte share_installed des alten FreeDOS-Kernels wurde auf Null gesetzt.\n 2.7:Das Byte share_installed des alten FreeDOS-Kernels wurde durch Resident auf Null gesetzt.\n 2.8:Dateitabelle: %u frei / %u gesamt, Sperrtabelle: %u frei / %u gesamt\n 2.9:Dateitabelle: %u gesamt, Sperrtabelle: %u gesamt\n
Looks all good.
Then please do what you want to do with it and add it to where it should be.
I personally would have written either: 0.2: "Lege" instead of "Legt" or: 0.5/0.6./0.8/0.9 "Deaktiviert", "Zeigt", "Deaktiviert", "Aktiviert" instead of "Deaktiviere" "Zeige" "Deaktiviere" "Aktiviere"
if I were you.
End of discussion now.
Thanks for making share translatable, here come French & Turkish translations. As a side note, it would be nice to add this project to https://github.com/shidel/fd-nls so other translators can find it more easily.