unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: google-translate
Date: Fri, 18 Sep 2015 00:32:08 +0200	[thread overview]
Message-ID: <87eghwznh3.fsf@debian.uxu> (raw)
In-Reply-To: 87eghyv9ji.fsf@gmail.com

Alex Kost <alezost@gmail.com> writes:

> Emanuel Berg (2015-09-16 06:01 +0300) wrote:
>
> (google-translate-translate "sv" "en" "bok")
> (google-translate-translate "sv" "da" "stuga")
> (google-translate-translate "sv" "de" "stuga")

OK, I looked this up! Let's see if I can it right
first try...

Now, if what is supposed to be used as inputs
(arguments) are the language codes that are among
other things in the Unix/C LC*/LANG* environmental
variables, then valid data with respect to language
input is defined in ISO-3166.

The Unix/C variables carry data with the following
syntax:

    xx_YY.CHARSET

where

    xx:       language code (e.g., "en") according to ISO-3166
    YY:       country  code (e.g., "FR") according to ISO-369
    CHARSET:  ASCII, UTF-8, or ISO-8859-1

[1, p. 317]

By the way, the domain of YY is the same as the list
of national, top-level domains ("se" -> ".se" etc.).

This can be included in the help and accompanied by
some examples. If the user sees the examples, even tho
he doesn't recognize their specific meaning
(i.e., what languages), probably he still knows *his*
locale and recognize that pattern and just add it.
Otherwise perhaps he would be benefited from an
ISO-3166 list to find out.

[2, pp. 25-26]

[1]

@book{practical-guide-to-linux,
    author    = {Mark Sobell},
    title     = {A Practical Guide to Linux},
    publisher = {Prentice Hall},
    edition   = {3rd edition},
    year      = 2013,
    ISBN      = {0-13-308504-X}
}

[2]

@book{internet-message,
  title      = {The Internet Message: Closing the Book with Electronic Mail},
  author     = {Marshall Rose},
  publisher  = {Prentice-Hall},
  year       = 1993,
  ISBN       = {0-13-092941-7}
}

-- 
underground experts united
http://user.it.uu.se/~embe8573




  parent reply	other threads:[~2015-09-17 22:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08  8:29 Is it possible to transform text before feeding it to ispell? Marcin Borkowski
2015-09-08 10:19 ` Alexis
2015-09-08 11:45   ` Tassilo Horn
2015-09-08 22:40   ` google-translate (was: Re: Is it possible to transform text before feeding it to ispell?) Emanuel Berg
2015-09-09  7:18     ` Andrey Tykhonov
2015-09-10  0:51       ` Emanuel Berg
2015-09-16  3:01       ` google-translate Emanuel Berg
2015-09-16 12:22         ` google-translate Alex Kost
2015-09-16 23:29           ` google-translate Emanuel Berg
2015-09-17 22:32           ` Emanuel Berg [this message]
2015-09-19  0:09             ` google-translate Emanuel Berg
2015-09-19  4:17               ` google-translate Ian Zimmerman
2015-09-19 15:03                 ` google-translate Emanuel Berg
2015-09-19 15:25                 ` google-translate Emanuel Berg
2015-09-08 13:06 ` Is it possible to transform text before feeding it to ispell? Michael Heerdegen
2015-09-08 15:24   ` Marcin Borkowski
2015-09-08 17:39     ` Eli Zaretskii
2015-09-08 15:54 ` Eli Zaretskii

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87eghwznh3.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --cc=help-gnu-emacs@gnu.org \
    /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).