Hey all,
I just edited the script to handle the translations. Here are the
variables that need to be translated. Please give them to me
_exactly_ how they should appear, with caps, spaces, accents, etc.
They'll go straight into the templates. For things like how case is
used, I think we should follow wikipedia's standards.
# wikipedia terms $stub = ""; $template = ""; $category = ""; $infobox = "";
# pdpedia terms $objectclass = "";
# page headers $inlets = ""; $outlets = ""; $arguments = ""; $messages = "";
# infobox $name = ""; $description = ""; $abbreviation = ""; $library = ""; $author = ""; $developer = ""; $releaseVersion = ""; $releaseDate = ""; $dependencies = ""; $license = ""; $website = ""; $programmingLanguage = ""; $platform = ""; $operatingSystem = ""; $language = ""; $dataType = ""; $distributions = "";
.hc
I spent 33 years and four months in active military service and
during that period I spent most of time as a high class muscle man
for Big Business, for Wall Street and the bankers. - General
Smedley Butler
You mean something like this?
Portuguese:
# wikipedia terms $stub = "Esboço"; $template = "Template"; $category = "Categoria"; $infobox = "Infobox";
# pdpedia terms $objectclass = "Classe de objecto";
# page headers $inlets = "Entradas"; $outlets = "SaÃdas"; $arguments = "Argumentos"; $messages = "Mensagens";
# infobox $name = "Nome"; $description = "Descrição"; $abbreviation = "Abreviatura"; $library = "Bbiblioteca"; $author = "Autor"; $developer = "Programador"; $releaseVersion = "Nº de versão"; $releaseDate = "Data de lançamento"; $dependencies = "Dependências"; $license = "Licença"; $website = "Website"; $programmingLanguage = "Linguagem de programação"; $platform = "Plataforma"; $operatingSystem = "Sistema operativo"; $language = "Linguagem"; $dataType = "Tipo de dado"; $distributions = "Distribuição";
Looks good, except maybe the wikipedia terms. They should be just
like in wikipedia. "template" also seems to be translated. How's this:
http://pt.wikipedia.org/wiki/Predefini%C3%A7%C3%A3o:Infobox
# wikipedia terms $stub = "Esboço"; $template = "Predefinição"; $category = "Categoria"; $infobox = "Infobox";
Also, is this a typo or is 'Bb' correct:
$library = "Bbiblioteca";
Is this term used for "release version" (instead of "test version",
"beta version", etc)
$releaseVersion = "Nº de versão";
Could it be:
$releaseVersion = "versão de lançamento";
.hc
On Oct 2, 2007, at 10:53 AM, João Miguel Pais wrote:
You mean something like this?
Portuguese:
# wikipedia terms $stub = "Esboço"; $template = "Template"; $category = "Categoria"; $infobox = "Infobox";
# pdpedia terms $objectclass = "Classe de objecto";
# page headers $inlets = "Entradas"; $outlets = "Saídas"; $arguments = "Argumentos"; $messages = "Mensagens";
# infobox $name = "Nome"; $description = "Descrição"; $abbreviation = "Abreviatura"; $library = "Bbiblioteca"; $author = "Autor"; $developer = "Programador"; $releaseVersion = "Nº de versão"; $releaseDate = "Data de lançamento"; $dependencies = "Dependências"; $license = "Licença"; $website = "Website"; $programmingLanguage = "Linguagem de programação"; $platform = "Plataforma"; $operatingSystem = "Sistema operativo"; $language = "Linguagem"; $dataType = "Tipo de dado"; $distributions = "Distribuição";
Computer science is no more related to the computer than astronomy is
related to the telescope. -Edsger Dykstra
Spanish
# wikipedia terms $stub = "borrador"; $template = "plantilla"; $category = "categoría"; $infobox = "cuadro informativo";
# pdpedia terms $objectclass = "clase de objeto";
# page headers $inlets = "inlets"; $outlets = "inlets"; $arguments = "argumentos"; $messages = "mensajes";
# infobox $name = "nombre"; $description = "descripción"; $abbreviation = "abreviación"; $library = "librería"; $author = "autor"; $developer = "desarrollador"; $releaseVersion = "número de versión"; $releaseDate = "fecha de la versión"; $dependencies = "dependencias"; $license = "licencia"; $website = "página web"; $programmingLanguage = "lenguaje de programación"; $platform = "plataforma"; $operatingSystem = "sistema operativo"; $language = "ldioma"; $dataType = "Tipo de dato"; $distributions = "distribuciones";
Note: Inlets and oulets could be transtaled like "entradas" and "salidas", but... as the most anglicism pehaps is best don't translate
On Oct 2, 2007, at 2:28 PM, Vircy Parker wrote:
Spanish
# wikipedia terms $stub = "borrador";
I couldnt' find the wikipedia work for "stub":
http://es.wikipedia.org/wiki/Plantilla:Borrador
It seems to be:
http://es.wikipedia.org/wiki/Plantilla:Esbozo
$template = "plantilla"; $category = "categoría"; $infobox = "cuadro informativo";
These are straight from wikipedia. I think they use the term "Infobox":
http://es.wikipedia.org/wiki/Plantilla:Infobox_Pa%C3%ADs
# pdpedia terms $objectclass = "clase de objeto";
# page headers $inlets = "inlets"; $outlets = "inlets";
"inlets" for both? in French and Portuguese, they used "entrada" and
"salida" (whatever those terms are in those languages, I forget), so
maybe that's appropriate in Spanish too.
.hc
$arguments = "argumentos"; $messages = "mensajes";
# infobox $name = "nombre"; $description = "descripción"; $abbreviation = "abreviación"; $library = "librería"; $author = "autor"; $developer = "desarrollador"; $releaseVersion = "número de versión"; $releaseDate = "fecha de la versión"; $dependencies = "dependencias"; $license = "licencia"; $website = "página web"; $programmingLanguage = "lenguaje de programación"; $platform = "plataforma"; $operatingSystem = "sistema operativo"; $language = "ldioma"; $dataType = "Tipo de dato"; $distributions = "distribuciones";
Note: Inlets and oulets could be transtaled like "entradas" and
"salidas", but... as the most anglicism pehaps is best don't
translate
Looking at things from a more basic level, you can come up with a
more direct solution... It may sound small in theory, but it in
practice, it can change entire economies. - Amy Smith
Spanish
# wikipedia terms $stub = "borrador";
I couldnt' find the wikipedia work for "stub":
http://es.wikipedia.org/wiki/Plantilla:Borrador
It seems to be:
ok, it seem to be Esbozo
$template = "plantilla";
$category = "categoría"; $infobox = "cuadro informativo";
These are straight from wikipedia. I think they use the term "Infobox":
ok, our custom are full of anglicism. :)
# pdpedia terms
$objectclass = "clase de objeto";
# page headers $inlets = "inlets"; $outlets = "inlets";
"inlets" for both? in French and Portuguese, they used "entrada" and "salida" (whatever those terms are in those languages, I forget), so maybe that's appropriate in Spanish too.
.hc
Not, excuse me: $inlets = "inlets"; $outlets = "outlets";
I like more entrada (entry) , salida (exit), but in pd-microworld inlet and oulet are already memes.
$arguments = "argumentos";
$messages = "mensajes";
# infobox $name = "nombre"; $description = "descripción"; $abbreviation = "abreviación"; $library = "librería"; $author = "autor"; $developer = "desarrollador"; $releaseVersion = "número de versión"; $releaseDate = "fecha de la versión"; $dependencies = "dependencias"; $license = "licencia"; $website = "página web"; $programmingLanguage = "lenguaje de programación"; $platform = "plataforma"; $operatingSystem = "sistema operativo"; $language = "ldioma"; $dataType = "Tipo de dato"; $distributions = "distribuciones";
Note: Inlets and oulets could be transtaled like "entradas" and "salidas", but... as the most anglicism pehaps is best don't translate
Looking at things from a more basic level, you can come up with a more direct solution... It may sound small in theory, but it in practice, it can change entire economies. - Amy Smith
Hey,
I haven't seen a complete template for this, I hope you haven't lost
interest. Please post a complete version of this template that I can
copy and paste, or attach it as a separate file. I don't speak much
Spanish, so I can't tell what's wrong or right most of the time.
# wikipedia terms my $stub = ""; my $template = ""; my $category = ""; my $infobox = ""; my $topLevel = ""; #
# pdpedia terms my $objectclass = "";
# page headers my $inlets = ""; my $outlets = ""; my $arguments = ""; my $messages = "";
# infobox my $name = ""; my $description = ""; my $abbreviation = ""; my $library = ""; my $author = ""; my $developer = ""; my $releaseVersion = ""; my $releaseDate = ""; my $dependencies = ""; my $license = ""; my $website = ""; my $programmingLanguage = ""; my $platform = ""; my $operatingSystem = ""; my $language = ""; my $dataType = ""; my $distributions = ""; my $status = "";
.hc
On Oct 2, 2007, at 3:52 PM, Vircy Parker wrote:
Spanish
# wikipedia terms $stub = "borrador";
I couldnt' find the wikipedia work for "stub":
http://es.wikipedia.org/wiki/Plantilla:Borrador
It seems to be:
http://es.wikipedia.org/wiki/Plantilla:Esbozo
ok, it seem to be Esbozo
$template = "plantilla"; $category = "categoría"; $infobox = "cuadro informativo";
These are straight from wikipedia. I think they use the term
"Infobox":http://es.wikipedia.org/wiki/Plantilla:Infobox_Pa%C3%ADs
ok, our custom are full of anglicism. :)
# pdpedia terms $objectclass = "clase de objeto"; # page headers $inlets = "inlets"; $outlets = "inlets";
"inlets" for both? in French and Portuguese, they used "entrada"
and "salida" (whatever those terms are in those languages, I
forget), so maybe that's appropriate in Spanish too..hc
Not, excuse me: $inlets = "inlets"; $outlets = "outlets";
I like more entrada (entry) , salida (exit), but in pd-microworld
inlet and oulet are already memes.$arguments = "argumentos"; $messages = "mensajes";
# infobox $name = "nombre"; $description = "descripción"; $abbreviation = "abreviación"; $library = "librería"; $author = "autor"; $developer = "desarrollador"; $releaseVersion = "número de versión"; $releaseDate = "fecha de la versión"; $dependencies = "dependencias"; $license = "licencia"; $website = "página web"; $programmingLanguage = "lenguaje de programación"; $platform = "plataforma"; $operatingSystem = "sistema operativo"; $language = "ldioma"; $dataType = "Tipo de dato"; $distributions = "distribuciones";
Note: Inlets and oulets could be transtaled like "entradas" and
"salidas", but... as the most anglicism pehaps is best don't
translate
Looking at things from a more basic level, you can come up with a
more direct solution... It may sound small in theory, but it in
practice, it can change entire economies. - Amy Smith
If you are not part of the solution, you are part of the problem.
# wikipedia terms my $stub = "esbozo"; my $template = "plantilla"; my $category = "categoría"; my $infobox = "infobox"; my $topLevel = "toplevel"; #
# pdpedia terms my $objectclass = "Clase del objeto";
# page headers my $inlets = "inlets"; my $outlets = "outlets"; my $arguments = "argumentos"; my $messages = "mensajes";
# infobox my $name = "nombre"; my $description = "descripción"; my $abbreviation = "abreviación"; my $library = "librería"; my $author = "autor"; my $developer = "desarrollador"; my $releaseVersion = "versión"; my $releaseDate = "fecha de la versión"; my $dependencies = "dependencias"; my $license = "licencia"; my $website = "sitio web"; my $programmingLanguage = "lenguaje de programación"; my $platform = "plataforma"; my $operatingSystem = "sistema operativo"; my $language = "lenguaje"; my $dataType = "tipo de dato"; my $distributions = "distribución"; my $status = "estado";
hc, I'm not sure about language:
programing language, braille language --- in spanish---> lenguaje english, french, inuit language ---in spanish --> idioma (idiom)
(correction: inlets, outlets, language)
# wikipedia terms my $stub = "esbozo"; my $template = "plantilla"; my $category = "categoría"; my $infobox = "infobox"; my $topLevel = "toplevel"; #
# pdpedia terms my $objectclass = "Clase del objeto";
# page headers my $inlets = "entradas"; my $outlets = "salidas"; my $arguments = "argumentos"; my $messages = "mensajes";
# infobox my $name = "nombre"; my $description = "descripción"; my $abbreviation = "abreviación"; my $library = "librería"; my $author = "autor"; my $developer = "desarrollador"; my $releaseVersion = "versión"; my $releaseDate = "fecha de la versión"; my $dependencies = "dependencias"; my $license = "licencia"; my $website = "sitio web"; my $programmingLanguage = "lenguaje de programación"; my $platform = "plataforma"; my $operatingSystem = "sistema operativo"; my $language = "idioma"; my $dataType = "tipo de dato"; my $distributions = "distribución"; my $status = "estado";
hc, I'm not sure about language:
programing language, braille language --- in spanish---> lenguaje english, french, inuit language ---in spanish --> idioma (idiom)
I would only change
my $distributions = "distribución"
to "distribuciones"
small thing, hope it helps best, j
hc, I'm not sure about language:
programing language, braille language --- in spanish---> lenguaje english, french, inuit language ---in spanish --> idioma (idiom)
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Ok, I am currently running the Español import into the test wiki:
http://wiki.puredata.info/test/boids2d
Check it out and make sure it's ok and I'll run the import into the
es wiki. You can find next steps here:
http://wiki.puredata.info/en/Wiki_administrator_how-to
.hc
On Oct 16, 2007, at 5:43 PM, Vircy Parker wrote:
(correction: inlets, outlets, language)
# wikipedia terms my $stub = "esbozo"; my $template = "plantilla"; my $category = "categoría"; my $infobox = "infobox"; my $topLevel = "toplevel"; #
# pdpedia terms my $objectclass = "Clase del objeto";
# page headers my $inlets = "entradas"; my $outlets = "salidas"; my $arguments = "argumentos"; my $messages = "mensajes";
# infobox my $name = "nombre"; my $description = "descripción"; my $abbreviation = "abreviación"; my $library = "librería"; my $author = "autor"; my $developer = "desarrollador"; my $releaseVersion = "versión"; my $releaseDate = "fecha de la versión"; my $dependencies = "dependencias"; my $license = "licencia"; my $website = "sitio web"; my $programmingLanguage = "lenguaje de programación"; my $platform = "plataforma"; my $operatingSystem = "sistema operativo"; my $language = "idioma"; my $dataType = "tipo de dato"; my $distributions = "distribución"; my $status = "estado";
hc, I'm not sure about language:
programing language, braille language --- in spanish---> lenguaje english, french, inuit language ---in spanish --> idioma (idiom)
I have the audacity to believe that peoples everywhere can have three
meals a day for their bodies, education and culture for their minds,
and dignity, equality and freedom for their spirits. - Martin
Luther King, Jr.
Hi,
sorry, I was busy these days before.. Anyway i dont (cant) usually read all emails of this list.
The translations are right. Only these two maybe could be translated:
my $infobox = "infobox"; my $topLevel = "toplevel";
Maybe "infobox" could be translated as "información". The second one i dont know the context exactly...
If you want more information about translation ask me, even directly.
br. GARFF
From: hans@eds.org Date: Fri, 19 Oct 2007 15:56:54 -0400 To: eloggro@gmail.com CC: pd-list@iem.at Subject: Re: [PD] Pdpedia Español WAS: translations for pdpedia templates
Ok, I am currently running the Español import into the test wiki:http://wiki.puredata.info/test/boids2dCheck it out and make sure it's ok and I'll run the import into the es wiki. You can find next steps here:http://wiki.puredata.info/en/Wiki_administrator_how-to.hc On Oct 16, 2007, at 5:43 PM, Vircy Parker wrote: (correction: inlets, outlets, language)
# wikipedia termsmy $stub = "esbozo";my $template = "plantilla";my $category = "categoría";my $infobox = "infobox"; my $topLevel = "toplevel"; # # pdpedia termsmy $objectclass = "Clase del objeto"; # page headersmy $inlets = "entradas";my $outlets = "salidas"; my $arguments = "argumentos";my $messages = "mensajes"; # infoboxmy $name = "nombre";my $description = "descripción"; my $abbreviation = "abreviación";my $library = "librería";my $author = "autor";my $developer = "desarrollador";my $releaseVersion = "versión"; my $releaseDate = "fecha de la versión";my $dependencies = "dependencias";my $license = "licencia";my $website = "sitio web"; my $programmingLanguage = "lenguaje de programación"; my $platform = "plataforma";my $operatingSystem = "sistema operativo";my $language = "idioma";my $dataType = "tipo de dato"; my $distributions = "distribución"; my $status = "estado";
hc, I'm not sure about language:
programing language, braille language --- in spanish---> lenguaje english, french, inuit language ---in spanish --> idioma (idiom)
I have the audacity to believe that peoples everywhere can have three meals a day for their bodies, education and culture for their minds, and dignity, equality and freedom for their spirits. - Martin Luther King, Jr.
Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Looks good, except maybe the wikipedia terms. They should be just like
in wikipedia. "template" also seems to be translated. How's this:
although it's an english word, template (as well as other words) is used
usually by people - in this context, much more often than Predefinicao.
http://pt.wikipedia.org/wiki/Predefini%C3%A7%C3%A3o:Infobox
# wikipedia terms $stub = "Esboço"; $template = "Predefinição"; $category = "Categoria"; $infobox = "Infobox";
Also, is this a typo or is 'Bb' correct:
ah, it's a typo. only one B
$library = "Bbiblioteca";
Is this term used for "release version" (instead of "test version",
"beta version", etc)$releaseVersion = "Nº de versão";
Could it be:
$releaseVersion = "versão de lançamento";
that can be more accurate, although it sounds a bit strange (that's why I
was trying to put something more language-friendly).
On Oct 2, 2007, at 10:53 AM, João Miguel Pais wrote:
You mean something like this?
Portuguese:
# wikipedia terms $stub = "Esboço"; $template = "Template"; $category = "Categoria"; $infobox = "Infobox";
# pdpedia terms $objectclass = "Classe de objecto";
# page headers $inlets = "Entradas"; $outlets = "SaÃdas"; $arguments = "Argumentos"; $messages = "Mensagens";
# infobox $name = "Nome"; $description = "Descrição"; $abbreviation = "Abreviatura"; $library = "Bbiblioteca"; $author = "Autor"; $developer = "Programador"; $releaseVersion = "Nº de versão"; $releaseDate = "Data de lançamento"; $dependencies = "Dependências"; $license = "Licença"; $website = "Website"; $programmingLanguage = "Linguagem de programação"; $platform = "Plataforma"; $operatingSystem = "Sistema operativo"; $language = "Linguagem"; $dataType = "Tipo de dado"; $distributions = "Distribuição";
On Oct 2, 2007, at 3:24 PM, João Miguel Pais wrote:
Looks good, except maybe the wikipedia terms. They should be just
like in wikipedia. "template" also seems to be translated. How's
this:although it's an english word, template (as well as other words) is
used usually by people - in this context, much more often than
Predefinicao.
Wikipedia PT has both, with Template as an alias.
http://pt.wikipedia.org/wiki/Predefini%C3%A7%C3%A3o:Infobox
# wikipedia terms $stub = "Esboço"; $template = "Predefinição"; $category = "Categoria"; $infobox = "Infobox";
Also, is this a typo or is 'Bb' correct:
ah, it's a typo. only one B
$library = "Bbiblioteca";
Is this term used for "release version" (instead of "test
version", "beta version", etc)$releaseVersion = "Nº de versão";
Could it be:
$releaseVersion = "versão de lançamento";
that can be more accurate, although it sounds a bit strange (that's
why I was trying to put something more language-friendly).
"Nº de versão" looks like "version number", which is not quite what
"release version" means. It is meant to mean the version of the most
recent release of that software. "latest release version" would be a
longer term for it.
.hc
On Oct 2, 2007, at 10:53 AM, João Miguel Pais wrote:
You mean something like this?
Portuguese:
# wikipedia terms $stub = "Esboço"; $template = "Template"; $category = "Categoria"; $infobox = "Infobox";
# pdpedia terms $objectclass = "Classe de objecto";
# page headers $inlets = "Entradas"; $outlets = "Saídas"; $arguments = "Argumentos"; $messages = "Mensagens";
# infobox $name = "Nome"; $description = "Descrição"; $abbreviation = "Abreviatura"; $library = "Bbiblioteca"; $author = "Autor"; $developer = "Programador"; $releaseVersion = "Nº de versão"; $releaseDate = "Data de lançamento"; $dependencies = "Dependências"; $license = "Licença"; $website = "Website"; $programmingLanguage = "Linguagem de programação"; $platform = "Plataforma"; $operatingSystem = "Sistema operativo"; $language = "Linguagem"; $dataType = "Tipo de dado"; $distributions = "Distribuição";
If nature has made any one thing less susceptible than all others of
exclusive property, it is the action of the thinking power called an
idea, which an individual may exclusively possess as long as he keeps
it to himself; but the moment it is divulged, it forces itself into
the possession of everyone, and the receiver cannot dispossess
himself of it. - Thomas Jefferson
Wikipedia PT has both, with Template as an alias.
Among designers, teachers and etc I always heard template. Do these hard
cases have to be 100% decided now? I can ask a portuguese programmer to
have a look at it at some point.
$releaseVersion = "versão de lançamento";
that can be more accurate, although it sounds a bit strange (that's why
I was trying to put something more language-friendly)."Nº de versão" looks like "version number", which is not quite what
"release version" means. It is meant to mean the version of the most
recent release of that software. "latest release version" would be a
longer term for it.
that's true.
what happens now? do you put the information somewhere, or must we
copy/paste elsewhere?
Joao
what happens now? do you put the information somewhere, or must we
copy/paste elsewhere?
what happens when a good enough translation has been found? is a page
created by the "language admin" like the one in the turkish version?
http://wiki.puredata.info/tr/index.php?title=%C5%9Eablon:Infobox_Objectclass
And then, is it a question of copying/translating/correcting the
individual articles of the english version?
I know that everything is just starting, but there are already some people
joining in fast and putting their time+energy. It might be efficient if
someone in the english version did 1 article correctly, so that there's a
model where all should follow. Then all can know how to put their energy
into the process. (for that reason I tried to start the
http://wiki.puredata.info/en/Wiki_administrator_how-to)
Joao
hi, the translation is used to label the standard textfields in the infobox and the raw pages. with that information it is possible to create a basic version of a language wiki. the next thing is to translate content. maybe start with general pages or objects that are often used, or do it library by library. as I already said before you can also do that by using a database file http://www.parasitaere-kapazitaeten.net/Pd/pdobjects with that file it is easy to generate wikipages and import them on a scripting basis. you can also do it library per library. people can split the list and do it in parts. then you have to decide if you want english text in your pages or not.
there is no real standardized layout yet. some sections like inlets outlets... will appear in every page. we try to find a style that is similar to wikipedia; at the top a small sentence that explains the object, then some paragraphs about technical information, and then examples and more details about what you can use the object for.
I think that can be translated from the english pages from the wiki itself, but we don't have that yet. [msd] already has a lot of information.
marius.
João Miguel Pais wrote:
what happens now? do you put the information somewhere, or must we
copy/paste elsewhere?what happens when a good enough translation has been found? is a page
created by the "language admin" like the one in the turkish version?
http://wiki.puredata.info/tr/index.php?title=%C5%9Eablon:Infobox_ObjectclassAnd then, is it a question of copying/translating/correcting the
individual articles of the english version?I know that everything is just starting, but there are already some people
joining in fast and putting their time+energy. It might be efficient if
someone in the english version did 1 article correctly, so that there's a
model where all should follow. Then all can know how to put their energy
into the process. (for that reason I tried to start the
http://wiki.puredata.info/en/Wiki_administrator_how-to)Joao
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Oct 2, 2007, at 6:08 PM, João Miguel Pais wrote:
Wikipedia PT has both, with Template as an alias.
Among designers, teachers and etc I always heard template. Do these
hard cases have to be 100% decided now? I can ask a portuguese
programmer to have a look at it at some point.
It's up to you, I don't speak Portuguese :D
$releaseVersion = "versão de lançamento";
that can be more accurate, although it sounds a bit strange
(that's why I was trying to put something more language-friendly)."Nº de versão" looks like "version number", which is not quite
what "release version" means. It is meant to mean the version of
the most recent release of that software. "latest release
version" would be a longer term for it.that's true.
what happens now? do you put the information somewhere, or must we
copy/paste elsewhere?
I think we should proceed like this:
- send your complete template of the translations to the list under
the name "portuguese pdpedia template" or something like that.
2) try to get feedback from other Portuguese speakers
3) after a short lazy consensus waiting period, I'll import the
templates
.hc
Joao
You can't steal a gift. Bird gave the world his music, and if you can
hear it, you can have it. - Dizzy Gillespie
Among designers, teachers and etc I always heard template. Do these
hard cases have to be 100% decided now? I can ask a portuguese
programmer to have a look at it at some point.It's up to you, I don't speak Portuguese :D
no, but you did a nice job correcting my portuguese
- send your complete template of the translations to the list under the
name "portuguese pdpedia template" or something like that. 2) try to get feedback from other Portuguese speakers 3) after a short lazy consensus waiting period, I'll import the templates
will do
On 10/2/07, Hans-Christoph Steiner hans@eds.org wrote:
I just edited the script to handle the translations. Here are the variables that need to be translated. Please give them to me _exactly_ how they should appear, with caps, spaces, accents, etc. They'll go straight into the templates. For things like how case is used, I think we should follow wikipedia's standards.
# These are for Turkish / Türkçe translations -uğur-
# wikipedia terms $stub = "Taslak"; $template = "Şablon"; $category = "Kategori"; $infobox = "Bilgi Kutusu";
# pdpedia terms $objectclass = "Nesne Sınıfı";
# page headers $inlets = "Girişler"; $outlets = "Çıkışlar"; $arguments = "Argümanlar"; $messages = "Mesajlar";
# infobox $name = "İsim"; $description = "Açıklama"; $abbreviation = "Kısaltma"; $library = "Kütüphane"; $author = "Yazar"; $developer = "Geliştirici"; $releaseVersion = "Versiyon"; $releaseDate = "Yayım Tarihi"; $dependencies = "Bağımlılıklar"; $license = "Lisans"; $website = "Web Sitesi"; $programmingLanguage = "Programlama Dili"; $platform = "Platform"; $operatingSystem = "İşletim Sistemi"; $language = "Lisan"; $dataType = "Veri Tipi"; $distributions = "Dağıtımlar";
Any comments on this template? There is one word which I forgot to
include, "status", like this: http://wiki.puredata.info/en/Status
Other than that, is this one ready to go? I am ready to do the import.
.hc
On Oct 2, 2007, at 1:29 PM, Uğur Güney wrote:
On 10/2/07, Hans-Christoph Steiner hans@eds.org wrote:
I just edited the script to handle the translations. Here are the variables that need to be translated. Please give them to me _exactly_ how they should appear, with caps, spaces, accents, etc. They'll go straight into the templates. For things like how case is used, I think we should follow wikipedia's standards.
# These are for Turkish / Türkçe translations -uğur-
# wikipedia terms $stub = "Taslak"; $template = "Şablon"; $category = "Kategori"; $infobox = "Bilgi Kutusu";
# pdpedia terms $objectclass = "Nesne Sınıfı";
# page headers $inlets = "Girişler"; $outlets = "Çıkışlar"; $arguments = "Argümanlar"; $messages = "Mesajlar";
# infobox $name = "İsim"; $description = "Açıklama"; $abbreviation = "Kısaltma"; $library = "Kütüphane"; $author = "Yazar"; $developer = "Geliştirici"; $releaseVersion = "Versiyon"; $releaseDate = "Yayım Tarihi"; $dependencies = "Bağımlılıklar"; $license = "Lisans"; $website = "Web Sitesi"; $programmingLanguage = "Programlama Dili"; $platform = "Platform"; $operatingSystem = "İşletim Sistemi"; $language = "Lisan"; $dataType = "Veri Tipi"; $distributions = "Dağıtımlar";
"It is convenient to imagine a power beyond us because that means we
don't have to examine our own lives.", from "The Idols of
Environmentalism", by Curtis White
This looks o.k. Status is: "Durum"
Batuhan
Hans-Christoph Steiner wrote:
Any comments on this template? There is one word which I forgot to
include, "status", like this: http://wiki.puredata.info/en/StatusOther than that, is this one ready to go? I am ready to do the import.
.hc
On Oct 2, 2007, at 1:29 PM, Uğur Güney wrote:
On 10/2/07, Hans-Christoph Steiner hans@eds.org wrote:
I just edited the script to handle the translations. Here are the variables that need to be translated. Please give them to me _exactly_ how they should appear, with caps, spaces, accents, etc. They'll go straight into the templates. For things like how case is used, I think we should follow wikipedia's standards.
# These are for Turkish / Türkçe translations -uğur-
# wikipedia terms $stub = "Taslak"; $template = "Şablon"; $category = "Kategori"; $infobox = "Bilgi Kutusu";
# pdpedia terms $objectclass = "Nesne Sınıfı";
# page headers $inlets = "Girişler"; $outlets = "Çıkışlar"; $arguments = "Argümanlar"; $messages = "Mesajlar";
# infobox $name = "İsim"; $description = "Açıklama"; $abbreviation = "Kısaltma"; $library = "Kütüphane"; $author = "Yazar"; $developer = "Geliştirici"; $releaseVersion = "Versiyon"; $releaseDate = "Yayım Tarihi"; $dependencies = "Bağımlılıklar"; $license = "Lisans"; $website = "Web Sitesi"; $programmingLanguage = "Programlama Dili"; $platform = "Platform"; $operatingSystem = "İşletim Sistemi"; $language = "Lisan"; $dataType = "Veri Tipi"; $distributions = "Dağıtımlar";
"It is convenient to imagine a power beyond us because that means we
don't have to examine our own lives.", from "The Idols of
Environmentalism", by Curtis White
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Ok, I am running a test import now, check it out here:
http://wiki.puredata.info/test/boids/boids2d
It turns out that MediaWiki uses the word "Template" for Turkish
rather than "Taslak". You can make a #redirect page if you want,
then use Taslak.
To see the infobox, you'll need to copy this:
http://wiki.puredata.info/en/index.php? title=Template:Infobox_Objectclass&action=edit
And paste it here, and translate it:
http://wiki.puredata.info/test/index.php? title=Template:Infobox_Nesne_S%C4%B1n%C4%B1f%C4%B1&action=edit
.hc
On Oct 15, 2007, at 1:02 AM, Batuhan Bozkurt wrote:
This looks o.k. Status is: "Durum"
Batuhan
Hans-Christoph Steiner wrote:
Any comments on this template? There is one word which I forgot to include, "status", like this: http://wiki.puredata.info/en/Status
Other than that, is this one ready to go? I am ready to do the
import..hc
On Oct 2, 2007, at 1:29 PM, Uğur Güney wrote:
On 10/2/07, Hans-Christoph Steiner hans@eds.org wrote:
I just edited the script to handle the translations. Here are the variables that need to be translated. Please give them to me _exactly_ how they should appear, with caps, spaces, accents, etc. They'll go straight into the templates. For things like how
case is used, I think we should follow wikipedia's standards.# These are for Turkish / Türkçe translations -uğur-
# wikipedia terms $stub = "Taslak"; $template = "Şablon"; $category = "Kategori"; $infobox = "Bilgi Kutusu";
# pdpedia terms $objectclass = "Nesne Sınıfı";
# page headers $inlets = "Girişler"; $outlets = "Çıkışlar"; $arguments = "Argümanlar"; $messages = "Mesajlar";
# infobox $name = "İsim"; $description = "Açıklama"; $abbreviation = "Kısaltma"; $library = "Kütüphane"; $author = "Yazar"; $developer = "Geliştirici"; $releaseVersion = "Versiyon"; $releaseDate = "Yayım Tarihi"; $dependencies = "Bağımlılıklar"; $license = "Lisans"; $website = "Web Sitesi"; $programmingLanguage = "Programlama Dili"; $platform = "Platform"; $operatingSystem = "İşletim Sistemi"; $language = "Lisan"; $dataType = "Veri Tipi"; $distributions = "Dağıtımlar";
"It is convenient to imagine a power beyond us because that means we don't have to examine our own lives.", from "The Idols of Environmentalism", by Curtis White
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
If you are not part of the solution, you are part of the problem.
On Tue, 2007-10-02 at 10:22 -0400, Hans-Christoph Steiner wrote:
yo, so many german speaking people here: i need your advice. since nobody have done yet the translation to german, i thougth, i could go for it. but: for me it's not quite obvious, what really should be translated and what not. when speaking german to other german people, often just the english terms are used. i tried to make a translation, that makes the most sense in my eyes, but that doesn't mean, that it does for others as well.
# wikipedia terms $stub = "Überarbeiten"; # this is used in the german wikipedia $template = "Vorlage"; $category = "Kategorie"; $infobox = "Infobox";
# pdpedia terms $objectclass = "Objektklasse";
# page headers $inlets = "Inlets"; $outlets = "Outles"; $arguments = "Argumente"; $messages = "Messages"; # not sure about this one. # german would be 'Nachrichten', but # noone seems to use it. # infobox $name = "Name"; $description = "Beschreibung"; $abbreviation = "Abkürzung"; $library = "Bibliothek"; $author = "Autor"; $developer = "Entwickler"; $releaseVersion = "Releaseversion"; $releaseDate = "Releasedatum"; $dependencies = "Abhängigkeiten"; $license = "Lizenz"; $website = "Webseite"; $programmingLanguage = "Programmiersprache"; $platform = "Plattform"; $operatingSystem = "Betriebssystem"; $language = "Sprache"; $dataType = "Datentyp"; $distributions = "Distribution";
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
On Oct 2, 2007, at 3:08 PM, Roman Haefeli wrote:
On Tue, 2007-10-02 at 10:22 -0400, Hans-Christoph Steiner wrote:
yo, so many german speaking people here: i need your advice. since nobody have done yet the translation to german, i thougth, i could go for it. but: for me it's not quite obvious, what really should be
translated and what not. when speaking german to other german people, often just the english terms are used. i tried to make a translation, that makes the most sense in my eyes, but that doesn't mean, that it does for
others as well.
# wikipedia terms $stub = "Überarbeiten"; # this is used in the german wikipedia
You can find the equivalents of a page in another language by
clicking the link on the lower lefthand side. Überarbeiten seems to
be Cleanup, but there isn't a Deutsch link for "stub".
http://en.wikipedia.org/wiki/Template:Cleanup
$template = "Vorlage"; $category = "Kategorie"; $infobox = "Infobox";
# pdpedia terms $objectclass = "Objektklasse";
# page headers $inlets = "Inlets"; $outlets = "Outles"; $arguments = "Argumente"; $messages = "Messages"; # not sure about this one. # german would be 'Nachrichten', but # noone seems to use it.
Since 'Messages' will be on the english site, I think that the German
pdpedia site would be oriented to people whose English isn't very
good. So I would think that Nachrichten would be better. Do people
ever talk about Nachrichten in the OOP world? There is already
Rechner, Festplatte, Bildschirm, etc.
.hc
# infobox $name = "Name"; $description = "Beschreibung"; $abbreviation = "Abkürzung"; $library = "Bibliothek"; $author = "Autor"; $developer = "Entwickler"; $releaseVersion = "Releaseversion"; $releaseDate = "Releasedatum"; $dependencies = "Abhängigkeiten"; $license = "Lizenz"; $website = "Webseite"; $programmingLanguage = "Programmiersprache"; $platform = "Plattform"; $operatingSystem = "Betriebssystem"; $language = "Sprache"; $dataType = "Datentyp"; $distributions = "Distribution";
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http:// messenger.yahoo.de
You can't steal a gift. Bird gave the world his music, and if you can
hear it, you can have it. - Dizzy Gillespie
On Tue, 2007-10-02 at 15:27 -0400, Hans-Christoph Steiner wrote:
On Oct 2, 2007, at 3:08 PM, Roman Haefeli wrote:
On Tue, 2007-10-02 at 10:22 -0400, Hans-Christoph Steiner wrote:
yo, so many german speaking people here: i need your advice. since nobody have done yet the translation to german, i thougth, i could go for it. but: for me it's not quite obvious, what really should be
translated and what not. when speaking german to other german people, often just the english terms are used. i tried to make a translation, that makes the most sense in my eyes, but that doesn't mean, that it does for
others as well.
# wikipedia terms $stub = "Überarbeiten"; # this is used in the german wikipedia
You can find the equivalents of a page in another language by
clicking the link on the lower lefthand side. Überarbeiten seems to
be Cleanup, but there isn't a Deutsch link for "stub".
i really investigated this one and and asked people from #wikipedia and it seems, that the german wikipedia lacks the exact equivalent for 'stub'. i don't know what to do in such a case. since all correct translations don't make much sense according to [1]. my suggestion is to use 'Rohbau'. Any objections from the german speaking community?
[1] http://dict.leo.org/ende?lp=ende&lang=de&searchLoc=0&cmpType=rel... (i am excited to see, if this one gets a linebreak)
$messages = "Messages"; # not sure about this one. # german would be 'Nachrichten', but # noone seems to use it.
Since 'Messages' will be on the english site, I think that the German
pdpedia site would be oriented to people whose English isn't very
good. So I would think that Nachrichten would be better. Do people
ever talk about Nachrichten in the OOP world? There is already
Rechner, Festplatte, Bildschirm, etc.
are you referring to Object Oriented Programming? i don't know, it's just that i never ever heard someone using the word 'Nachricht' in that context. i would like to hear other opinions.
roman
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Hallo!
$inlets = "Inlets"; $outlets = "Outles";
I use in german also the terms Eingang and Ausgang - don't know what the others think ...
$arguments = "Argumente"; $messages = "Messages"; # not sure about this one. # german would be 'Nachrichten', but # noone seems to use it.
Hm ... I also don't use Nachrichten, but it does not sound that bad ...
LG Georg
$stub = rumpffassung or (unbearbeiteter) rohentwurf $library could stay library $inlet, $outlet could be eingang/eingänge ausgang/ausgänge $messages stay messags. marisu.
Roman Haefeli wrote:
On Tue, 2007-10-02 at 10:22 -0400, Hans-Christoph Steiner wrote:
yo, so many german speaking people here: i need your advice. since nobody have done yet the translation to german, i thougth, i could go for it. but: for me it's not quite obvious, what really should be translated and what not. when speaking german to other german people, often just the english terms are used. i tried to make a translation, that makes the most sense in my eyes, but that doesn't mean, that it does for others as well.
# wikipedia terms $stub = "Überarbeiten"; # this is used in the german wikipedia $template = "Vorlage"; $category = "Kategorie"; $infobox = "Infobox";
# pdpedia terms $objectclass = "Objektklasse";
# page headers $inlets = "Inlets"; $outlets = "Outles"; $arguments = "Argumente"; $messages = "Messages"; # not sure about this one. # german would be 'Nachrichten', but # noone seems to use it. # infobox $name = "Name"; $description = "Beschreibung"; $abbreviation = "Abkürzung"; $library = "Bibliothek"; $author = "Autor"; $developer = "Entwickler"; $releaseVersion = "Releaseversion"; $releaseDate = "Releasedatum"; $dependencies = "Abhängigkeiten"; $license = "Lizenz"; $website = "Webseite"; $programmingLanguage = "Programmiersprache"; $platform = "Plattform"; $operatingSystem = "Betriebssystem"; $language = "Sprache"; $dataType = "Datentyp"; $distributions = "Distribution";
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Tue, 2007-10-02 at 16:00 -0400, marius schebella wrote:
$stub = rumpffassung or (unbearbeiteter) rohentwurf
yeah, 'rohentwurf' sounds pretty reasonable
$library could stay library
hm... that doesn't make sense to me. 'Programmbibliothek' or just 'Bibliothek' are widely used terms. why should it be different for pd-world?
$inlet, $outlet could be eingang/eingänge ausgang/ausgänge
i'm fine with that. though, i have the feeling that this could be nationality influenced. i never heard a swiss using 'eingang' for 'inlet', but austrians do it, iirc. don't know about germans.
$messages stay messags.
i am fine with that.
marius, can you elaborate a bit your preferences?
roman
Roman Haefeli wrote:
On Tue, 2007-10-02 at 10:22 -0400, Hans-Christoph Steiner wrote:
yo, so many german speaking people here: i need your advice. since nobody have done yet the translation to german, i thougth, i could go for it. but: for me it's not quite obvious, what really should be translated and what not. when speaking german to other german people, often just the english terms are used. i tried to make a translation, that makes the most sense in my eyes, but that doesn't mean, that it does for others as well.
# wikipedia terms $stub = "Überarbeiten"; # this is used in the german wikipedia $template = "Vorlage"; $category = "Kategorie"; $infobox = "Infobox";
# pdpedia terms $objectclass = "Objektklasse";
# page headers $inlets = "Inlets"; $outlets = "Outles"; $arguments = "Argumente"; $messages = "Messages"; # not sure about this one. # german would be 'Nachrichten', but # noone seems to use it. # infobox $name = "Name"; $description = "Beschreibung"; $abbreviation = "Abkürzung"; $library = "Bibliothek"; $author = "Autor"; $developer = "Entwickler"; $releaseVersion = "Releaseversion"; $releaseDate = "Releasedatum"; $dependencies = "Abhängigkeiten"; $license = "Lizenz"; $website = "Webseite"; $programmingLanguage = "Programmiersprache"; $platform = "Plattform"; $operatingSystem = "Betriebssystem"; $language = "Sprache"; $dataType = "Datentyp"; $distributions = "Distribution";
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
for stub I prefer rohfassung or rohentwurf. it means raw draft or basic sketch. for inlets/outlets I think we can use german words, but also mention the english terms, so that people are not totally helpless when they read english documentation. I used "befehl" and "nachricht" for message. bibliothek for library sounds good to me, although I do not really use it. There are also some other terms that need to be translated, like box = ? abstraction = ? canvas = arbeitsbereich patch = ? marius.
Roman Haefeli wrote:
On Tue, 2007-10-02 at 16:00 -0400, marius schebella wrote:
$stub = rumpffassung or (unbearbeiteter) rohentwurf
yeah, 'rohentwurf' sounds pretty reasonable
$library could stay library
hm... that doesn't make sense to me. 'Programmbibliothek' or just 'Bibliothek' are widely used terms. why should it be different for pd-world?
$inlet, $outlet could be eingang/eingänge ausgang/ausgänge
i'm fine with that. though, i have the feeling that this could be nationality influenced. i never heard a swiss using 'eingang' for 'inlet', but austrians do it, iirc. don't know about germans.
$messages stay messags.
i am fine with that.
marius, can you elaborate a bit your preferences?
roman
Roman Haefeli wrote:
On Tue, 2007-10-02 at 10:22 -0400, Hans-Christoph Steiner wrote:
yo, so many german speaking people here: i need your advice. since nobody have done yet the translation to german, i thougth, i could go for it. but: for me it's not quite obvious, what really should be translated and what not. when speaking german to other german people, often just the english terms are used. i tried to make a translation, that makes the most sense in my eyes, but that doesn't mean, that it does for others as well.
# wikipedia terms $stub = "Überarbeiten"; # this is used in the german wikipedia $template = "Vorlage"; $category = "Kategorie"; $infobox = "Infobox";
# pdpedia terms $objectclass = "Objektklasse";
# page headers $inlets = "Inlets"; $outlets = "Outles"; $arguments = "Argumente"; $messages = "Messages"; # not sure about this one. # german would be 'Nachrichten', but # noone seems to use it. # infobox $name = "Name"; $description = "Beschreibung"; $abbreviation = "Abkürzung"; $library = "Bibliothek"; $author = "Autor"; $developer = "Entwickler"; $releaseVersion = "Releaseversion"; $releaseDate = "Releasedatum"; $dependencies = "Abhängigkeiten"; $license = "Lizenz"; $website = "Webseite"; $programmingLanguage = "Programmiersprache"; $platform = "Plattform"; $operatingSystem = "Betriebssystem"; $language = "Sprache"; $dataType = "Datentyp"; $distributions = "Distribution";
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
for inlets/outlets I think we can use german words, but also mention the english terms, so that people are not totally helpless when they read english documentation.
in germany among germans I always heard Eingang/Ausgang, as well as
Nachricht.
I used "befehl" and "nachricht" for message. bibliothek for library sounds good to me, although I do not really use it. There are also some other terms that need to be translated, like box = ?
kÀstchen?
abstraction = ?
http://de.wikipedia.org/wiki/Objektorientierte_Programmierung has
Abstraktion
canvas = arbeitsbereich patch = ?
If it can helps, 'abstraction' should be translated in French by "capsule" which means something that looks like a box, and the process of 'making an abstraction' from a (piece of) patch is "encapsulation", used in french object programming language...
I don't know how 'patch' should be translated, it seems to be used because it looks like a 'patch bay'... So, it's already an argotic french langage used by sound ingeniors since a long time, it's not new and not specific to graphical-object-digital sound programming...
Fred
João Miguel Pais wrote:
for inlets/outlets I think we can use german words, but also mention the english terms, so that people are not totally helpless when they read english documentation.
in germany among germans I always heard Eingang/Ausgang, as well as
Nachricht.I used "befehl" and "nachricht" for message. bibliothek for library sounds good to me, although I do not really use it. There are also some other terms that need to be translated, like box = ?
kästchen?
abstraction = ?
http://de.wikipedia.org/wiki/Objektorientierte_Programmierung has
Abstraktioncanvas = arbeitsbereich patch = ?
http://de.wikipedia.org/wiki/Patch
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Wed, 2007-10-03 at 00:03 +0200, João Miguel Pais wrote:
for inlets/outlets I think we can use german words, but also mention the english terms, so that people are not totally helpless when they read english documentation.
in germany among germans I always heard Eingang/Ausgang, as well as
Nachricht.I used "befehl" and "nachricht" for message. bibliothek for library sounds good to me, although I do not really use it. There are also some other terms that need to be translated, like box = ?
kästchen?
infobox is certainly nothing, that could be misunderstood in german. i'd say let's skip any intention to be pure in that case, since any correct translation sounds so 19th century. furthermore is german a language, that is quite used to anglizisms, unlike french.
roman
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
I was talking about message"box" object"box" number"box"... marius.
Roman Haefeli wrote:
On Wed, 2007-10-03 at 00:03 +0200, João Miguel Pais wrote:
for inlets/outlets I think we can use german words, but also mention the english terms, so that people are not totally helpless when they read english documentation.
in germany among germans I always heard Eingang/Ausgang, as well as
Nachricht.I used "befehl" and "nachricht" for message. bibliothek for library sounds good to me, although I do not really use it. There are also some other terms that need to be translated, like box = ?
kästchen?
infobox is certainly nothing, that could be misunderstood in german. i'd say let's skip any intention to be pure in that case, since any correct translation sounds so 19th century. furthermore is german a language, that is quite used to anglizisms, unlike french.
roman
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
On Tue, 2007-10-02 at 21:03 -0400, marius schebella wrote:
I was talking about message"box" object"box" number"box"... marius.
oops, sorry.
'box' seems to exist in german, at least duden shows two entries for it and de.wikipedia more.
i think, one can say, that even in german it has the meaning of a thing, where you can put something into, which would be suitable for the context of pd, wouldn't it?
yo, i can't think of a really good translation. 'kästchen' doesn't sound so good, does it?
roman
I used "befehl" and "nachricht" for message. bibliothek for library sounds good to me, although I do not really use it. There are also some other terms that need to be translated, like box = ?
kästchen?
infobox is certainly nothing, that could be misunderstood in german. i'd say let's skip any intention to be pure in that case, since any correct translation sounds so 19th century. furthermore is german a language, that is quite used to anglizisms, unlike french.
roman
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
nachrichtenbox, objektbox, zahlenbox
m.
Am 02.10.2007 um 21:03 schrieb marius schebella:
I was talking about message"box" object"box" number"box"... marius.
Roman Haefeli wrote:
On Wed, 2007-10-03 at 00:03 +0200, João Miguel Pais wrote:
for inlets/outlets I think we can use german words, but also
mention the english terms, so that people are not totally helpless when they
read english documentation.in germany among germans I always heard Eingang/Ausgang, as well as Nachricht.
I used "befehl" and "nachricht" for message. bibliothek for library sounds good to me, although I do not really use it. There are also some other terms that need to be translated, like box = ?
kästchen?
infobox is certainly nothing, that could be misunderstood in
german. i'd say let's skip any intention to be pure in that case, since any
correct translation sounds so 19th century. furthermore is german a language, that is quite used to anglizisms, unlike french.roman
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http:// messenger.yahoo.de
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
just as a resume: are all german speaking people fine with that?
# wikipedia terms $stub = "Rohentwurf"; $template = "Vorlage"; $category = "Kategorie"; $infobox = "Infobox";
# pdpedia terms $objectclass = "Objektklasse";
# page headers $inlets = "Eingänge"; $outlets = "Ausgänge"; $arguments = "Argumente"; $messages = "Nachrichten";
# infobox $name = "Name"; $description = "Beschreibung"; $abbreviation = "Abkürzung"; $library = "Bibliothek"; $author = "Autor"; $developer = "Entwickler"; $releaseVersion = "Releaseversion"; $releaseDate = "Releasedatum"; $dependencies = "Abhängigkeiten"; $license = "Lizenz"; $website = "Webseite"; $programmingLanguage = "Programmiersprache"; $platform = "Plattform"; $operatingSystem = "Betriebssystem"; $language = "Sprache"; $dataType = "Datentyp"; $distributions = "Distributionen";
On Tue, 2007-10-02 at 17:20 -0400, marius schebella wrote:
for stub I prefer rohfassung or rohentwurf. it means raw draft or basic sketch. for inlets/outlets I think we can use german words, but also mention the english terms, so that people are not totally helpless when they read english documentation. I used "befehl" and "nachricht" for message. bibliothek for library sounds good to me, although I do not really use it. There are also some other terms that need to be translated, like box = ? abstraction = ? canvas = arbeitsbereich patch = ? marius.
Roman Haefeli wrote:
On Tue, 2007-10-02 at 16:00 -0400, marius schebella wrote:
$stub = rumpffassung or (unbearbeiteter) rohentwurf
yeah, 'rohentwurf' sounds pretty reasonable
$library could stay library
hm... that doesn't make sense to me. 'Programmbibliothek' or just 'Bibliothek' are widely used terms. why should it be different for pd-world?
$inlet, $outlet could be eingang/eingänge ausgang/ausgänge
i'm fine with that. though, i have the feeling that this could be nationality influenced. i never heard a swiss using 'eingang' for 'inlet', but austrians do it, iirc. don't know about germans.
$messages stay messags.
i am fine with that.
marius, can you elaborate a bit your preferences?
roman
Roman Haefeli wrote:
On Tue, 2007-10-02 at 10:22 -0400, Hans-Christoph Steiner wrote:
yo, so many german speaking people here: i need your advice. since nobody have done yet the translation to german, i thougth, i could go for it. but: for me it's not quite obvious, what really should be translated and what not. when speaking german to other german people, often just the english terms are used. i tried to make a translation, that makes the most sense in my eyes, but that doesn't mean, that it does for others as well.
# wikipedia terms $stub = "Überarbeiten"; # this is used in the german wikipedia $template = "Vorlage"; $category = "Kategorie"; $infobox = "Infobox";
# pdpedia terms $objectclass = "Objektklasse";
# page headers $inlets = "Inlets"; $outlets = "Outles"; $arguments = "Argumente"; $messages = "Messages"; # not sure about this one. # german would be 'Nachrichten', but # noone seems to use it. # infobox $name = "Name"; $description = "Beschreibung"; $abbreviation = "Abkürzung"; $library = "Bibliothek"; $author = "Autor"; $developer = "Entwickler"; $releaseVersion = "Releaseversion"; $releaseDate = "Releasedatum"; $dependencies = "Abhängigkeiten"; $license = "Lizenz"; $website = "Webseite"; $programmingLanguage = "Programmiersprache"; $platform = "Plattform"; $operatingSystem = "Betriebssystem"; $language = "Sprache"; $dataType = "Datentyp"; $distributions = "Distribution";
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
heute schon nachrichten geschaut? I am not sure about "nachrichten", but the rest is ok for me. m.
Roman Haefeli wrote:
just as a resume: are all german speaking people fine with that?
# wikipedia terms $stub = "Rohentwurf"; $template = "Vorlage"; $category = "Kategorie"; $infobox = "Infobox";
# pdpedia terms $objectclass = "Objektklasse";
# page headers $inlets = "Eingänge"; $outlets = "Ausgänge"; $arguments = "Argumente"; $messages = "Nachrichten";
# infobox $name = "Name"; $description = "Beschreibung"; $abbreviation = "Abkürzung"; $library = "Bibliothek"; $author = "Autor"; $developer = "Entwickler"; $releaseVersion = "Releaseversion"; $releaseDate = "Releasedatum"; $dependencies = "Abhängigkeiten"; $license = "Lizenz"; $website = "Webseite"; $programmingLanguage = "Programmiersprache"; $platform = "Plattform"; $operatingSystem = "Betriebssystem"; $language = "Sprache"; $dataType = "Datentyp"; $distributions = "Distributionen";
On Tue, 2007-10-02 at 17:20 -0400, marius schebella wrote:
for stub I prefer rohfassung or rohentwurf. it means raw draft or basic sketch. for inlets/outlets I think we can use german words, but also mention the english terms, so that people are not totally helpless when they read english documentation. I used "befehl" and "nachricht" for message. bibliothek for library sounds good to me, although I do not really use it. There are also some other terms that need to be translated, like box = ? abstraction = ? canvas = arbeitsbereich patch = ? marius.
Roman Haefeli wrote:
On Tue, 2007-10-02 at 16:00 -0400, marius schebella wrote:
$stub = rumpffassung or (unbearbeiteter) rohentwurf
yeah, 'rohentwurf' sounds pretty reasonable
$library could stay library
hm... that doesn't make sense to me. 'Programmbibliothek' or just 'Bibliothek' are widely used terms. why should it be different for pd-world?
$inlet, $outlet could be eingang/eingänge ausgang/ausgänge
i'm fine with that. though, i have the feeling that this could be nationality influenced. i never heard a swiss using 'eingang' for 'inlet', but austrians do it, iirc. don't know about germans.
$messages stay messags.
i am fine with that.
marius, can you elaborate a bit your preferences?
roman
Roman Haefeli wrote:
On Tue, 2007-10-02 at 10:22 -0400, Hans-Christoph Steiner wrote:
yo, so many german speaking people here: i need your advice. since nobody have done yet the translation to german, i thougth, i could go for it. but: for me it's not quite obvious, what really should be translated and what not. when speaking german to other german people, often just the english terms are used. i tried to make a translation, that makes the most sense in my eyes, but that doesn't mean, that it does for others as well.
# wikipedia terms $stub = "Überarbeiten"; # this is used in the german wikipedia $template = "Vorlage"; $category = "Kategorie"; $infobox = "Infobox";
# pdpedia terms $objectclass = "Objektklasse";
# page headers $inlets = "Inlets"; $outlets = "Outles"; $arguments = "Argumente"; $messages = "Messages"; # not sure about this one. # german would be 'Nachrichten', but # noone seems to use it. # infobox $name = "Name"; $description = "Beschreibung"; $abbreviation = "Abkürzung"; $library = "Bibliothek"; $author = "Autor"; $developer = "Entwickler"; $releaseVersion = "Releaseversion"; $releaseDate = "Releasedatum"; $dependencies = "Abhängigkeiten"; $license = "Lizenz"; $website = "Webseite"; $programmingLanguage = "Programmiersprache"; $platform = "Plattform"; $operatingSystem = "Betriebssystem"; $language = "Sprache"; $dataType = "Datentyp"; $distributions = "Distribution";
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
nice and clean translation.
just releaseversion sounds like an ugly hybrid – although i can't
come up with something better.
“veröffentlicht” might be close..
Am 02.10.2007 um 21:12 schrieb marius schebella:
heute schon nachrichten geschaut? I am not sure about "nachrichten", but the rest is ok for me. m.
Roman Haefeli wrote:
just as a resume: are all german speaking people fine with that?
# wikipedia terms $stub = "Rohentwurf"; $template = "Vorlage"; $category = "Kategorie"; $infobox = "Infobox";
# pdpedia terms $objectclass = "Objektklasse";
# page headers $inlets = "Eingänge"; $outlets = "Ausgänge"; $arguments = "Argumente"; $messages = "Nachrichten";
# infobox $name = "Name"; $description = "Beschreibung"; $abbreviation = "Abkürzung"; $library = "Bibliothek"; $author = "Autor"; $developer = "Entwickler"; $releaseVersion = "Releaseversion"; $releaseDate = "Releasedatum"; $dependencies = "Abhängigkeiten"; $license = "Lizenz"; $website = "Webseite"; $programmingLanguage = "Programmiersprache"; $platform = "Plattform"; $operatingSystem = "Betriebssystem"; $language = "Sprache"; $dataType = "Datentyp"; $distributions = "Distributionen";
On Tue, 2007-10-02 at 17:20 -0400, marius schebella wrote:
for stub I prefer rohfassung or rohentwurf. it means raw draft or basic sketch. for inlets/outlets I think we can use german words, but also
mention the english terms, so that people are not totally helpless when they
read english documentation. I used "befehl" and "nachricht" for message. bibliothek for library sounds good to me, although I do not really use it. There are also some other terms that need to be translated, like box = ? abstraction = ? canvas = arbeitsbereich patch = ? marius.Roman Haefeli wrote:
On Tue, 2007-10-02 at 16:00 -0400, marius schebella wrote:
$stub = rumpffassung or (unbearbeiteter) rohentwurf
yeah, 'rohentwurf' sounds pretty reasonable
$library could stay library
hm... that doesn't make sense to me. 'Programmbibliothek' or just 'Bibliothek' are widely used terms. why should it be different for pd-world?
$inlet, $outlet could be eingang/eingänge ausgang/ausgänge
i'm fine with that. though, i have the feeling that this could be nationality
influenced. i never heard a swiss using 'eingang' for 'inlet', but austrians
do it, iirc. don't know about germans.$messages stay messags.
i am fine with that.
marius, can you elaborate a bit your preferences?
roman
Roman Haefeli wrote:
On Tue, 2007-10-02 at 10:22 -0400, Hans-Christoph Steiner wrote:
yo, so many german speaking people here: i need your advice.
since nobody have done yet the translation to german, i thougth, i
could go for it. but: for me it's not quite obvious, what really should be
translated and what not. when speaking german to other german people, often
just the english terms are used. i tried to make a translation, that
makes the most sense in my eyes, but that doesn't mean, that it does for
others as well.
# wikipedia terms $stub = "Überarbeiten"; # this is used in the german
wikipedia $template = "Vorlage"; $category = "Kategorie"; $infobox = "Infobox";# pdpedia terms $objectclass = "Objektklasse";
# page headers $inlets = "Inlets"; $outlets = "Outles"; $arguments = "Argumente"; $messages = "Messages"; # not sure about this one. # german would be 'Nachrichten',
but # noone seems to use it. # infobox $name = "Name"; $description = "Beschreibung"; $abbreviation = "Abkürzung"; $library = "Bibliothek"; $author = "Autor"; $developer = "Entwickler"; $releaseVersion = "Releaseversion"; $releaseDate = "Releasedatum"; $dependencies = "Abhängigkeiten"; $license = "Lizenz"; $website = "Webseite"; $programmingLanguage = "Programmiersprache"; $platform = "Plattform"; $operatingSystem = "Betriebssystem"; $language = "Sprache"; $dataType = "Datentyp"; $distributions = "Distribution";___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http:// messenger.yahoo.de
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http:// lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http:// lists.puredata.info/listinfo/pd-list
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http:// messenger.yahoo.de
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http:// messenger.yahoo.de
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
marius schebella wrote:
heute schon nachrichten geschaut? I am not sure about "nachrichten", but the rest is ok for me. m.
same for me: i don't think that "nachrichten" is the correct translation. probably "Signale" would be better, if signals wasn't already used for something else...
how do you call "messages" when you teach pd in german? at least, i call them "messages"
fmga.sdr IOhannes
hi iohannes, marius,
i think roman is correct with “Nachrichten” like in: „eine Nachricht verschicken an...“ not like in watching the news though. ;]
m
Am 03.10.2007 um 02:49 schrieb IOhannes m zmoelnig:
marius schebella wrote:
heute schon nachrichten geschaut? I am not sure about "nachrichten", but the rest is ok for me. m.
same for me: i don't think that "nachrichten" is the correct
translation. probably "Signale" would be better, if signals wasn't already used for something else...how do you call "messages" when you teach pd in german? at least, i call them "messages"
fmga.sdr IOhannes
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
Max Neupert wrote:
hi iohannes, marius,
i think roman is correct with “Nachrichten” like in: „eine Nachricht verschicken an...“ not like in watching the news though. ;]
well obviously. the question is whether we should translate "pure data" as "reine daten" ("rein" as in "reines wasser", not as in "rheingold").
after all, it is a translation to german, not french.
fgmadsr. IOhannes
what about some other germanophones on the list cast their ballot on
this question?
frank, what's your opinion?
i taught pd to german speaking non-nerds with russian as their second
language and i think they appreciated that i used nachrichten instead
of messages.. but maybe you're right and i spent to much time in
montreal and became to sensible about political correct language
usage ;)
or alternatively we make an austrian version of pdpedia...
greetings, m.
Am 03.10.2007 um 12:23 schrieb IOhannes m zmoelnig:
Max Neupert wrote:
hi iohannes, marius, i think roman is correct with “Nachrichten” like in: „eine Nachricht verschicken an...“ not like in watching the news though. ;]
well obviously. the question is whether we should translate "pure data" as "reine
daten" ("rein" as in "reines wasser", not as in "rheingold").after all, it is a translation to german, not french.
fgmadsr. IOhannes
Hallo, Max Neupert hat gesagt: // Max Neupert wrote:
what about some other germanophones on the list cast their ballot on
this question? frank, what's your opinion?
I'm normally all for anglicisms and I use "Message" when talking to IOhannes or other german-speaking Pd people, but I admit, that I've mostly used "Nachrichten" in my c't-Artikel on Pd. I sometimes wrote Message as well, though, just so people know what's used on pd-Liste. I'd say, "Nachrichten" would be the better term for a german pdpedia, but if there's a "Message" somewhere, it would be okay as well.
Some more things I used in that article and their translations:
box: Box message box: Nachrichtenbox number box: Zahlenbox inlet: Inlet, Ausgang (both were used) object box: Objektbox patch: Patch patch window: Patchfenster patch cord: Patchkabel edit mode: Edit-Modus/Editiermodus run mode: Run-Modus default value: Default-Wert compute audio: Audioberechnung array: Array table: Tabelle (seldom used) sender: Sender receiver: EmpfÀnger argument: Argument float: FlieÃkommazahl, Zahl
Of course when talking about an actual object (class) literally, nothing was translated: [float] stayed [float], "float object" as in "put a float-object there" became "float-Objekt"
Tschau,
Frank Barknecht _ ______footils.org__
Some more things I used in that article and their translations:
patch window: Patchfenster
arbeitsbereich
patch cord: Patchkabel
verbindung
edit mode: Edit-Modus/Editiermodus run mode: Run-Modus
bearbeitungs- und betriebs modus
default value: Default-Wert compute audio: Audioberechnung
signalverarbeitung einschalten
array: Array table: Tabelle (seldom used) Tschau,
baba. marius.
Hallo, marius schebella hat gesagt: // marius schebella wrote:
Some more things I used in that article and their translations:
patch window: Patchfenster
arbeitsbereich
Urgh.
patch cord: Patchkabel
verbindung
That's "connection". A patch cord is something else. (Though a patch cable actually is something different as well, but well.)
Anyway I wouldn't even try to translate "patch" itself. It a technical term that's used in a special way even when talking about Pd in its natural, English language.
edit mode: Edit-Modus/Editiermodus run mode: Run-Modus
bearbeitungs- und betriebs modus
Urgh.
Ciao
Frank Barknecht _ ______footils.org__
On Fri, 2007-10-05 at 00:20 +0200, Frank Barknecht wrote:
Hallo, marius schebella hat gesagt: // marius schebella wrote:
Some more things I used in that article and their translations:
patch window: Patchfenster
arbeitsbereich
Urgh.
yeah: 'urgh'
patch cord: Patchkabel
verbindung
That's "connection". A patch cord is something else. (Though a patch cable actually is something different as well, but well.)
Anyway I wouldn't even try to translate "patch" itself. It a technical term that's used in a special way even when talking about Pd in its natural, English language.
edit mode: Edit-Modus/Editiermodus run mode: Run-Modus
bearbeitungs- und betriebs modus
Urgh.
yeah: 'urgh'
marius: can you elaborate a bit, what your proposals are based on? if you rather find one better than the other, i'd like to know why.
roman
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
well first of all, I cannot remember where I read patch window? I often read canvas and I translated that as arbeitsbereich. but that is not very specific, I commit. to edit means bearbeiten. I don't use editieren, which is more herausgeben, or at least related to text. and to run means betreiben. (run a business). betriebs-modus ist der modus in dem der patch "in betrieb" ist. ich wuerde allerdings nicht drauf bestehen. marius.
Roman Haefeli wrote:
On Fri, 2007-10-05 at 00:20 +0200, Frank Barknecht wrote:
Hallo, marius schebella hat gesagt: // marius schebella wrote:
Some more things I used in that article and their translations:
patch window: Patchfenster
arbeitsbereich
Urgh.
yeah: 'urgh'
patch cord: Patchkabel
verbindung
That's "connection". A patch cord is something else. (Though a patch cable actually is something different as well, but well.)
Anyway I wouldn't even try to translate "patch" itself. It a technical term that's used in a special way even when talking about Pd in its natural, English language.
edit mode: Edit-Modus/Editiermodus run mode: Run-Modus
bearbeitungs- und betriebs modus
Urgh.
yeah: 'urgh'
marius: can you elaborate a bit, what your proposals are based on? if you rather find one better than the other, i'd like to know why.
roman
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
marius schebella wrote:
well first of all, I cannot remember where I read patch window? I often read canvas and I translated that as arbeitsbereich. but that is not very specific, I commit. to edit means bearbeiten. I don't use editieren, which is more herausgeben, or at least related to text. and to run means betreiben. (run a business). betriebs-modus ist der modus in dem der patch "in betrieb" ist. ich wuerde allerdings nicht drauf bestehen. marius.
Bearbeitungsmodus is good, run mode should be translated to Ablaufmodus (to run a test/program = einen Test/Programm ablaufen lassen).
cu Thomas
"Prisons are needed only to provide the illusion that courts and police are effective. They're a kind of job insurance." (Leto II. in: Frank Herbert, God Emperor of Dune) http://thomas.dergrossebruder.org/
Frank Barknecht wrote:
Some more things I used in that article and their translations:
box: Box message box: Nachrichtenbox number box: Zahlenbox inlet: Inlet, Ausgang (both were used)
Eingang
default value: Default-Wert
Vorgabe
cu Thomas
"Prisons are needed only to provide the illusion that courts and police are effective. They're a kind of job insurance." (Leto II. in: Frank Herbert, God Emperor of Dune) http://thomas.dergrossebruder.org/
Hallo, Thomas Mayer hat gesagt: // Thomas Mayer wrote:
Frank Barknecht wrote:
Some more things I used in that article and their translations:
box: Box message box: Nachrichtenbox number box: Zahlenbox inlet: Inlet, Ausgang (both were used)
Eingang
ugh, yes, of course.
default value: Default-Wert
Vorgabe
That's good as well. I guess I was allowed to use default in c't magazine, as it's a computer magazine and somehow the readers are kind of familiar with "default", too, so the editor didn't mind (or just overlooked it).
Ciao
Frank Barknecht _ ______footils.org__
On Wed, 2007-10-03 at 10:39 -0400, Max Neupert wrote:
hi iohannes, marius,
i think roman is correct with “Nachrichten” like in: „eine Nachricht verschicken an...“ not like in watching the news though. ;]
yo, actually i don't have an opinion on this. first i proposed 'messages', but then some people suggested 'nachrichten', that is why i changed it in the second proposal. i really cannot say, what is better in that case.
roman
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
On Oct 2, 2007, at 9:04 PM, Roman Haefeli wrote:
just as a resume: are all german speaking people fine with that?
# wikipedia terms $stub = "Rohentwurf";
Since the German Wikipedia doesn't use stubs, and instead merged
stubs and cleanups into "Überarbeiten", I think it would be a good
idea to follow that standard. Then the wikipedia docs apply nicely
to the pdpedia.
Otherwise, the rest looks fine to me. I let the rest of you haggle
of 'messages' vs. 'nachtrichten'. :D
.hc
$template = "Vorlage"; $category = "Kategorie"; $infobox = "Infobox";
# pdpedia terms $objectclass = "Objektklasse";
# page headers $inlets = "Eingänge"; $outlets = "Ausgänge"; $arguments = "Argumente"; $messages = "Nachrichten";
# infobox $name = "Name"; $description = "Beschreibung"; $abbreviation = "Abkürzung"; $library = "Bibliothek"; $author = "Autor"; $developer = "Entwickler"; $releaseVersion = "Releaseversion"; $releaseDate = "Releasedatum"; $dependencies = "Abhängigkeiten"; $license = "Lizenz"; $website = "Webseite"; $programmingLanguage = "Programmiersprache"; $platform = "Plattform"; $operatingSystem = "Betriebssystem"; $language = "Sprache"; $dataType = "Datentyp"; $distributions = "Distributionen";
On Tue, 2007-10-02 at 17:20 -0400, marius schebella wrote:
for stub I prefer rohfassung or rohentwurf. it means raw draft or basic sketch. for inlets/outlets I think we can use german words, but also
mention the english terms, so that people are not totally helpless when they read english documentation. I used "befehl" and "nachricht" for message. bibliothek for library sounds good to me, although I do not really use it. There are also some other terms that need to be translated, like box = ? abstraction = ? canvas = arbeitsbereich patch = ? marius.Roman Haefeli wrote:
On Tue, 2007-10-02 at 16:00 -0400, marius schebella wrote:
$stub = rumpffassung or (unbearbeiteter) rohentwurf
yeah, 'rohentwurf' sounds pretty reasonable
$library could stay library
hm... that doesn't make sense to me. 'Programmbibliothek' or just 'Bibliothek' are widely used terms. why should it be different for pd-world?
$inlet, $outlet could be eingang/eingänge ausgang/ausgänge
i'm fine with that. though, i have the feeling that this could be nationality
influenced. i never heard a swiss using 'eingang' for 'inlet', but austrians do
it, iirc. don't know about germans.$messages stay messags.
i am fine with that.
marius, can you elaborate a bit your preferences?
roman
Roman Haefeli wrote:
On Tue, 2007-10-02 at 10:22 -0400, Hans-Christoph Steiner wrote:
yo, so many german speaking people here: i need your advice. since nobody have done yet the translation to german, i thougth, i
could go for it. but: for me it's not quite obvious, what really should be
translated and what not. when speaking german to other german people, often
just the english terms are used. i tried to make a translation, that
makes the most sense in my eyes, but that doesn't mean, that it does for
others as well.
# wikipedia terms $stub = "Überarbeiten"; # this is used in the german wikipedia $template = "Vorlage"; $category = "Kategorie"; $infobox = "Infobox";
# pdpedia terms $objectclass = "Objektklasse";
# page headers $inlets = "Inlets"; $outlets = "Outles"; $arguments = "Argumente"; $messages = "Messages"; # not sure about this one. # german would be 'Nachrichten', but # noone seems to use it. # infobox $name = "Name"; $description = "Beschreibung"; $abbreviation = "Abkürzung"; $library = "Bibliothek"; $author = "Autor"; $developer = "Entwickler"; $releaseVersion = "Releaseversion"; $releaseDate = "Releasedatum"; $dependencies = "Abhängigkeiten"; $license = "Lizenz"; $website = "Webseite"; $programmingLanguage = "Programmiersprache"; $platform = "Plattform"; $operatingSystem = "Betriebssystem"; $language = "Sprache"; $dataType = "Datentyp"; $distributions = "Distribution";
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http:// messenger.yahoo.de
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http:// lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http:// messenger.yahoo.de
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http:// messenger.yahoo.de
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
"[W]e have invented the technology to eliminate scarcity, but we are
deliberately throwing it away to benefit those who profit from
scarcity." -John Gilmore
German Wikipedia doesn't use "stub" at all, so I think it would be
good to follow their standard. It is the second biggest wikipedia,
so it should be well developed.
They seem to mark things with "Überarbeiten", combining the English
"stub" and "cleanup" into one concept.
.hc
On Oct 2, 2007, at 4:00 PM, marius schebella wrote:
$stub = rumpffassung or (unbearbeiteter) rohentwurf $library could stay library $inlet, $outlet could be eingang/eingänge ausgang/ausgänge $messages stay messags. marisu.
Roman Haefeli wrote:
On Tue, 2007-10-02 at 10:22 -0400, Hans-Christoph Steiner wrote: yo, so many german speaking people here: i need your advice. since nobody have done yet the translation to german, i thougth, i could go for it. but: for me it's not quite obvious, what really should be
translated and what not. when speaking german to other german people, often just the english terms are used. i tried to make a translation, that makes the most sense in my eyes, but that doesn't mean, that it does for
others as well. ---------------------------------- # wikipedia terms $stub = "Überarbeiten"; # this is used in the german wikipedia $template = "Vorlage"; $category = "Kategorie"; $infobox = "Infobox"; # pdpedia terms $objectclass = "Objektklasse"; # page headers $inlets = "Inlets"; $outlets = "Outles"; $arguments = "Argumente"; $messages = "Messages"; # not sure about this one. # german would be 'Nachrichten', but # noone seems to use it. # infobox $name = "Name"; $description = "Beschreibung"; $abbreviation = "Abkürzung"; $library = "Bibliothek"; $author = "Autor"; $developer = "Entwickler"; $releaseVersion = "Releaseversion"; $releaseDate = "Releasedatum"; $dependencies = "Abhängigkeiten"; $license = "Lizenz"; $website = "Webseite"; $programmingLanguage = "Programmiersprache"; $platform = "Plattform"; $operatingSystem = "Betriebssystem"; $language = "Sprache"; $dataType = "Datentyp"; $distributions = "Distribution"; ___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http:// messenger.yahoo.de _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
If you are not part of the solution, you are part of the problem.
Hello,
Since didn't see any Nederlands verison yet, here's my attempt at one:
# wikipedia terms $stub = "beg"; // i asked this on #wikipedia-nl, and they told me {{beg}} (with the curly braces). 'beg' is an abbreviation for 'begin' $template = "sjabloon"; $category = "categorie"; $infobox = "infobox";
# pdpedia terms $objectclass = "objectklasse";
# page headers $inlets = "ingangen"; $outlets = "uitgangen"; $arguments = "argumenten"; $messages = "berichten"; // could be 'boodschappen' too, but that sounds a bit wierd to me, as that also means 'arrands'.
# infobox $name = "naam"; $description = "beschrijving"; // can also be 'omschrijving' $abbreviation = "afkorting"; $library = "bibliotheek"; $author = "auteur"; $developer = "ontwikkelaar"; $releaseVersion = "versie"; $releaseDate = "uitgebrachtOp"; // or 'gepubliceerdOp' ? or 'vrijgegevenOp? or just 'releasedate' ? $dependencies = "vereisten"; // translated freely as 'requirements' here, maybe there's a better word but it doesnt spring to mind now $license = "licentie"; $website = "website"; $programmingLanguage = "programmeerTaal"; $platform = "platform"; $operatingSystem = "besturingsSysteem"; $language = "taal"; $dataType = "dataType"; $distributions = "distributies";
comments and suggestions from dutch speakers welcome !
Tim
On Oct 8, 2007, at 2:19 PM, tim wrote:
Hello,
Since didn't see any Nederlands verison yet, here's my attempt at one:
Cool, so you want to be the "sysop" of the Nederlands site?
# wikipedia terms $stub = "beg"; // i asked this on #wikipedia-nl, and they told
me {{beg}} (with the curly braces). 'beg' is an abbreviation for
'begin'
Beginnetje is also used:
http://nl.wikipedia.org/wiki/Categorie:Beginnetje
$template = "sjabloon"; $category = "categorie"; $infobox = "infobox";
# pdpedia terms $objectclass = "objectklasse";
# page headers $inlets = "ingangen"; $outlets = "uitgangen"; $arguments = "argumenten"; $messages = "berichten"; // could be 'boodschappen' too, but that
sounds a bit wierd to me, as that also means 'arrands'.# infobox $name = "naam"; $description = "beschrijving"; // can also be 'omschrijving' $abbreviation = "afkorting"; $library = "bibliotheek"; $author = "auteur"; $developer = "ontwikkelaar"; $releaseVersion = "versie"; just 'releasedate' ? $dependencies = "vereisten"; // translated freely as
'requirements' here, maybe there's a better word but it doesnt
spring to mind now $license = "licentie"; $website = "website";$releaseDate = "uitgebrachtOp"; // or 'gepubliceerdOp' ? or
'vrijgegevenOp? or $programmingLanguage = "programmeerTaal"; $operatingSystem = "besturingsSysteem"; $dataType = "dataType";
"camel case" isn't used in wikipedia (unless that's a Dutch spelling
convention). In English, following wikipedia, these are:
Release date Programming language Operating system Data type
.hc
comments and suggestions from dutch speakers welcome !
Tim
Using ReBirth is like trying to play an 808 with a long stick. - David Zicarelli
Hi Tim & all!
my 50c on the Duch translations you proposed..
$arguments = "argumenten";
maybe "parameters" is better here. if i here "argumenten" in Dutch i rather think of arguments like in a discussion
$messages = "berichten"; // could be 'boodschappen' too, but that sounds a bit wierd to me, as that also means 'arrands'.
i think "berichten" definitely sounds better
$dependencies = "vereisten"; // translated freely as 'requirements' here, maybe there's a better word but it doesnt spring to mind now
if i read "vereisten" in Dutch i woldn't think of dependencies the way it's used in computer programming. maybe the literal translation "afhankelijkheden"? sounds a bit ugly but i think it's more clear
$releaseDate = "uitgebrachtOp"; // or 'gepubliceerdOp' ? or 'vrijgegevenOp? or
"datum van uitgave" ? - i think it's better to stick to a noun..
$programmingLanguage = "programmeerTaal"; $operatingSystem = "besturingsSysteem"; $dataType = "dataType";
"camel case" isn't used in wikipedia (unless that's a Dutch spelling convention). In English, following wikipedia, these are:
it are all existing words which you normally write i one word in dutch, so you can just drop the camelcase..
groetjes,
Kristof
info@kristoflauwers.domainepublic.net
http://kristoflauwers.domainepublic.net http://myspace.com/xofxof ____________________________________
-
Batuhan Bozkurt -
Frank Barknecht -
FredVoisin -
Georg Holzmann -
Hans-Christoph Steiner -
IOhannes m zmoelnig -
Jaime Oliver -
Javier García -
João Miguel Pais -
kristof lauwers -
marius schebella -
Max Neupert -
Roman Haefeli -
Thomas Mayer -
tim -
Uğur Güney -
Vircy Parker