Hello Romano,
Thank you for taking the time to make this translation.
Roman wrote:
EDIT: I have uploaded file here: https://limewire.com/?referrer=pq7i8xx7p2
It seems that limewire requires both javascript and an account to access the
code. Luckily, I could extract the code from your original submission to
lzip-bug.
My question is if the way I publish it to forums and maybe github is
correct before I do it. Licence stays and COPYING file will be
distributed along the code. Should I also add original lzip code or just
translation is enough? Also credits are in -V of the utility that refer
to both original lzip author as well as those others mentioned.
Copyright from source files have been added at the beginning of my
source file as well. Please review if that is enough or something else
need to be done? Finally, internal project name is lzipcs but I can change
it if you do not wish similarities in case people start bothering you.
Thanks for asking. I'll try to answer all your questions:
- COPYING is distributed along the code. OK
- As in any derivative work, the source code of the work itself
(translation) is enough. There is no need to distribute the original lzip
source code.
- It would be useful for users that the source code and the output of
--version or --help include also a way to reach you or the lzipcs project
page, so that they can report problems (for example).
- the name (lzipcs) is OK (and informative).
Maybe you should state in the output of --version or --help that lzipcs is
not a complete translation of lzip-1.25. Else users may complain to you that
it lacks the fast encoder (option -0) and several other options.
BTW, it seems that when you removed option -0 you forgot to decrease the
index of the default encoder options to 5 in line 3919 of Program.cs. I
guess lzipcs compresses at level -7 by default (instead of -6).
Everything else seems good to me.
Best regards,
Antonio.
