Skip to content
This repository was archived by the owner on Nov 25, 2020. It is now read-only.

Conversation

kluckow
Copy link
Contributor

@kluckow kluckow commented Mar 30, 2015

No description provided.

cdujeu added a commit that referenced this pull request Mar 30, 2015
updated umlauts and some bad translations/grammar
@cdujeu cdujeu merged commit aa79a32 into pydio:develop Mar 30, 2015
@ghost
Copy link

ghost commented Mar 31, 2015

Hi and thanks for contributing!

You did good work. Don't know if you plan to do further changes beside updating the german umlauts.

If so just keep in mind to replace words that are half german and half english with a german synonym.
e.g. "Upload" => "Hochladen"
or "Upload-Limit" => "Limit"

Also have a look at how the same word is translated in other parts of the application to keep them equal. (e.g. "Optionen" => "Einstellungen")

Dont forget to do a quick review in user interface to ensure that everything is correct (length in ui, etc.)

I just did a view minor changes while reviewing (most changes are not in your code):
#890

Stefan

@kluckow
Copy link
Contributor Author

kluckow commented Mar 31, 2015

Thank you huzergackl,

I might do further german translation.

You mentioned "Upload" and "Upload-Limit". There are english words like
these for example, that you do not need to translate that strict into
german.
"Upload" is one of many other words you do not need to translate.
Nowadays there is a lot of english in the german language. It is almost
weird to see "Hochladen".
And so the "Upload-Limit" is also perfect as translation. This is just a
suggestion, but I am not the only german who thinks that way. But of
course, the aspect of keeping terms equal all over Pydio is very important.

So next time I will be more careful and check other i18n's to do so.

kluckow
Am 31.03.2015 21:26 schrieb "huzergackl" notifications@github.com:

Hi and thanks for contributing!

You did good work. Don't know if you plan to do further changes beside
updating the german umlauts.

If so just keep in mind to replace words that are half german and half
english with a german synonym.
e.g. "Upload" => "Hochladen"
or "Upload-Limit" => "Limit"

Also have a look at how the same word is translated in other parts of the
application to keep them equal. (e.g. "Optionen" => "Einstellungen")

Dont forget to do a quick review in user interface to ensure that
everything is correct (length in ui, etc.)

I just did a view minor changes while reviewing (most changes are not in
your code):
#890

Stefan


Reply to this email directly or view it on GitHub.

@ghost
Copy link

ghost commented Apr 1, 2015

Upload is one of the words, i am not sure either and i dont want to bring in my personal preference.

The word upload is already in Duden where you can see how common it is. But this level is the same for "Hochladen" or "Upload". Arguments for "Hochladen" instead of upload is, that "Hochladen" is already used many times (e.g. for upload button) and that other Services like Dropbox also use "Hochladen".

@kluckow
Copy link
Contributor Author

kluckow commented Apr 1, 2015

Ah ok. Like I said, its probably more important to keep terms equal and on
a level that users are used to.

But I would not rely too much on the Duden.
There is a word called "Denglisch" in the german Duden.
It combines the words "Deutsch" and "Englisch" into one. And it just came
up, because there is such a change going on in the german language.
That is what I meant.
So sometimes it is way more attractive for an user to see the english term
than the german one.

kluckow

2015-04-01 16:23 GMT+02:00 huzergackl notifications@github.com:

Upload is one of the words, i am not sure either and i dont want to bring
in my personal preference.

The word upload is already in Duden where you can see how common it is.
But this level is the same for "Hochladen" or "Upload". Arguments for
"Hochladen" instead of upload is, that "Hochladen" is already used many
times (e.g. for upload button) and that other Services like Dropbox also
use "Hochladen".


Reply to this email directly or view it on GitHub
#888 (comment).

@cdujeu
Copy link
Member

cdujeu commented Apr 2, 2015

Hi guys, seeing this discussion, I'll wait for your GO before merging #890 , just tell me :-)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants