From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Quiliro Ordonez <quiliro@riseup.net>
Cc: help-guix@gnu.org
Subject: Re: guix-a dokumentaro en Esperanto
Date: Sun, 28 Apr 2019 06:53:36 +0200 [thread overview]
Message-ID: <20190428045336.jnud4figepwa4afc@pelzflorian.localdomain> (raw)
In-Reply-To: <13c3bb941beac3d3d1c43af1039d00b7@riseup.net>
On Sat, Apr 27, 2019 at 08:44:06PM -0700, Quiliro Ordonez wrote:
> El 2019-04-27 11:01, pelzflorian (Florian Pelz) escribió:
> > On Sat, Apr 27, 2019 at 08:35:05AM +0200, swedebugia wrote:
> >> On 2019-04-18 03:33, Quiliro Ordonez wrote:
> >> > El 2019-04-16 08:53, swedebugia escribió:
> >> >> I just translated the complete manual with google translate to create a
> >> >> first draft. (it is ~200.000 words)
> >> >> […]
> >> >
> >> > Mi ne plaĉas Google-on. Plie mi pensas ke ĝi igas kop'rajton malliberan.
> >>
> >> (about whether using google translate makes the resulting text
> >> copyrighted to google)
> >>
> >> Mi tute ne konsentas pri tio. Vidu
> >> https://meta.wikimedia.org/wiki/Wikilegal/Copyright_for_Google_Translations
> >>
> >> (I disagree with that. See
> >> https://meta.wikimedia.org/wiki/Wikilegal/Copyright_for_Google_Translations)
> >>
> >
> > Should this question be asked on a more general mailing list on GNU
> > policy? I remember Parabola escalating a discussion at
> > <https://lists.gnu.org/archive/html/libreplanet-discuss/2017-01/msg00001.html>.
>
> One issue is privacy issues and another issue is non-freedom of Chromium
> on that thread. Is this appreciation incorrect?
>
Their discussion is unrelated. I wanted to state that they escalated
an issue to libreplanet-discuss.
I believe there should be GNU policy dictating whether usage of Google
Translate is OK or not, because maybe it is possible that some
jurisdiction we care about could rule that Google has a copyright on
what their software algorithms produce. AFAIK this is not covered in
their terms of service, but I did not read much of them.
Regards,
Florian
next prev parent reply other threads:[~2019-04-28 5:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 19:43 guix-a dokumentaro en Esperanto Quiliro Ordonez
2019-04-12 22:24 ` Luther Thompson
2019-04-16 8:53 ` swedebugia
2019-04-18 1:33 ` Quiliro Ordonez
2019-04-26 0:28 ` Quiliro Ordonez
2019-04-27 6:35 ` swedebugia
2019-04-27 7:27 ` Quiliro Ordonez
2019-04-27 9:01 ` swedebugia
2019-04-30 17:03 ` Quiliro's lists
2019-04-27 11:01 ` pelzflorian (Florian Pelz)
2019-04-28 3:44 ` Quiliro Ordonez
2019-04-28 4:53 ` pelzflorian (Florian Pelz) [this message]
2019-04-13 11:07 ` Konrad Hinsen
2019-04-17 21:06 ` Ludovic Courtès
2019-04-27 6:37 ` swedebugia
2019-04-28 3:53 ` Quiliro Ordonez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190428045336.jnud4figepwa4afc@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=help-guix@gnu.org \
--cc=quiliro@riseup.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).