Hi Bill,
I'm grateful and glad that I'm able to give something back and to
contribute to the work in some way. :)
I´ve been giving this some thought and you are correct regarding the
links-file. I´ll try to adapt the text itself in the translation so that
the links could be left as it is, perhaps using parenthesis as you
suggested.
For the license-file I understand that the copyright notices can be a
tricky area navigating. As I'm not trained in the legal trade, I can't
guarantee the translation reflects the notices in every aspect when
translated. The current translation I've made in the Swedish user guide for
1.6 is as good as I can get it to my own knowledge in the subject and
analysis trying to reflect the original text.
For the new user guide we can, of course, leave the text as it is in the
original language with a note in Swedish, explaining why it's done this
way and urging the reader him/herself to embrace and understand the
copyright notices. This can be done in the wsjtx-main-file as a preamble to
the section.
A downside to this is that the user guide is not "completely translated"
and the "look" of the user guide may be "unfinished".
An alternative may be doing a proper translation of the text with the help
of a person with legal knowledge and in that way producing a license_se
-file for "generic"-use for future releases. This may not be a good idea
if the text have to be changed in the future for some reason.
I do agree that Joe has the last word in this. However looking at the
options above I see the most benefits with leaving the license-file as it
is and writing a short preamble in the user guide as suggested. I'll also
do a retake/update on the 1.6 user guide so this reflects the decisions
made here.
Best regards and 73:s
//Anders, SM7VRZ
2016-12-10 13:14 GMT+01:00 Bill Somerville <g4...@classdesign.com>:
> On 10/12/2016 11:01, sm7...@gmail.com wrote:
>
> Links.adoc
>
> License.adoc
>
> Hi Anders,
>
> thanks for your work on the WSJT-X User Guide Swedish translation.
>
> Having translated versions of the links document would be counter
> productive IMHO as any changes in link locations would need to be updated
> in every language. I understand that there are a small number of substitute
> link text replacements in that file but I am not sure translating them is
> worth the potential downstream maintenance burden. You could perhaps add a
> translated phrase in parenthesis after the link in the referencing document
> if you feel it is necessary.
>
> Translating copyright notices is a tricky area and most authors require
> that the text is not changed in any way. That means at least the original
> text in the original language must appear in any translated document.
> Because of this I think the English version must remain in the common area
> and be linked as in the English document.
>
> Of course Joe holds the copyright so he may have other opinions which
> carry more weight than anything I say here.
>
> 73
> Bill
> G4WJS.
>
> ------------------------------------------------------------
> ------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today.http://sdm.link/xeonphi
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
