[Geoserver-devel] Completing and Updating German translation

GeoServer GeoServer Developer
1

Hello GeoServer devs and German translators,

as recommended by Jody Garnett, I've translated the new messages on the welcome page for the 2.22.0 release.

After that, I started to complete the German translation. In order to give the German UI a consistent appearance, I also need to change some of the already localized messages. The whole process will take some time and I will contribute batches of changes from time to time.

This affects work done by others (maybe long) before so, I'd like to ask whether you are fine with that and/or like to participate concerning some basic wording decisions. Since it's about really a lot of messages, we cannot discuss every change in advance. However, you could always review my upcoming PRs. I will be open for a discussion on any change made.

There are several goals:

- consistent wording and use of terms
- use common IT wording
- be more precise and descriptive (if required and possible)

Very likely, I won't reach all goals in a single step so, this is work in progress.

Nevertheless, I'd like to discuss renaming of some very basic terms in advance. Some of them are located at quite prominent places in the UI and so, may affect German users that have been used to the old terms for quite a long time.

1. Layer Group

Inconsistently translated:

"Gruppenlayer"
"Layergruppe"

Will change to "Gruppenlayer" (I guess it's the more common term).

2. Root Layer

Inconsistently translated:

"Hauptlayer" (in WMS global settings)
"Wurzellayer" (in Layer Group Editor, type 'Earth Observetion Tree')

I tend to use "Wurzellayer" (like in "Wurzelvereichnis"). Due to the double "ll", for better readability writing it with a hyphen "Wurzel-Layer" may be an option. Any suggestions?

3. Dimensions

Context: Layer Editor Tab "Dimensions" to enable Time and Elevation dimensions and to add custom dimensions.

Translated as:

"Ausdehnung" ("expansion" in English)

I guess, this term is misleading. More correct may actually be "Dimensionen", since in all major German GIS, features also have two or more dimensions like they do in English.

4. Publishing

Translated as:

"Publizierung"

My suggestion is to change this into "Veröffentlichung", which I guess is the more common term in German. However, this change may not be part of the first batch of German translation changes.

The 2.22.0 release is scheduled for Friday, November 18th. In turn, I will issue the first PR on that on Thursday, November 17th. So, please send any suggestions and/or vetos prior to that date. If I get no such responses, I will assume that you are all fine with my proposed changes.

Cheers
Carsten

--

Carsten Klein
Lead Software Engineer

DataGis GmbH

Johann-Strauß-Str. 26
70794 Filderstadt

T +49 7158 9490-106
F +49 7158 9490-111

E-Mail: c.klein@anonymised.com
Internet: www.datagis.com

Registergericht: Amtsgericht Stuttgart, HRB 225945
Geschäftsführung: Dr. Gunter Hahn, Markus Ruess, Carsten Klein

2

Hi Carsten, list,

please find some comments inline.

Am 15.11.22 um 13:04 schrieb Carsten Klein:

Hello GeoServer devs and German translators,

as recommended by Jody Garnett, I've translated the new messages on the welcome page for the 2.22.0 release.

After that, I started to complete the German translation. In order to give the German UI a consistent appearance, I also need to change some of the already localized messages. The whole process will take some time and I will contribute batches of changes from time to time.

+1 for the efforts towards consistency, nice!

This affects work done by others (maybe long) before so, I'd like to ask whether you are fine with that and/or like to participate concerning some basic wording decisions. Since it's about really a lot of messages, we cannot discuss every change in advance. However, you could always review my upcoming PRs. I will be open for a discussion on any change made.

There are several goals:

- consistent wording and use of terms
- use common IT wording
- be more precise and descriptive (if required and possible)

Very likely, I won't reach all goals in a single step so, this is work in progress.

Maybe you coudl split the task once you have a general idea, I am sure we find others that help.

Nevertheless, I'd like to discuss renaming of some very basic terms in advance. Some of them are located at quite prominent places in the UI and so, may affect German users that have been used to the old terms for quite a long time.

1. Layer Group

Inconsistently translated:

"Gruppenlayer"
"Layergruppe"

Will change to "Gruppenlayer" (I guess it's the more common term).

I like "Gruppenlayer"

2. Root Layer

Inconsistently translated:

"Hauptlayer" (in WMS global settings)
"Wurzellayer" (in Layer Group Editor, type 'Earth Observetion Tree')

I tend to use "Wurzellayer" (like in "Wurzelvereichnis"). Due to the double "ll", for better readability writing it with a hyphen "Wurzel-Layer" may be an option. Any suggestions?

I do not like "Wurzellayer" or "Wurzel-Layer" (the longer I look at the words the more odd the look). How about "Hauptlayer" (not a 100 % match) or "Basislayer"?

Hard to translate, TBH.

3. Dimensions

Context: Layer Editor Tab "Dimensions" to enable Time and Elevation dimensions and to add custom dimensions.

Translated as:

"Ausdehnung" ("expansion" in English)

I guess, this term is misleading. More correct may actually be "Dimensionen", since in all major German GIS, features also have two or more dimensions like they do in English.

Yes, please use "Dimensionen", thankee-sai.

4. Publishing

Translated as:

"Publizierung"

My suggestion is to change this into "Veröffentlichung", which I guess is the more common term in German. However, this change may not be part of the first batch of German translation changes.

Yeah why not, indifferent here.

Thanks again and best regards.

Marc

The 2.22.0 release is scheduled for Friday, November 18th. In turn, I will issue the first PR on that on Thursday, November 17th. So, please send any suggestions and/or vetos prior to that date. If I get no such responses, I will assume that you are all fine with my proposed changes.

Cheers
Carsten

3

Hi Marc,

Root Layer

I'm with you, "Wurzellayer" (with or without hyphen) is actually not a good choice. On the other hand, "Basislayer" is not much better, as its like "Base layer", which has a different (but well established) meaning in GIS (aka background/base layer and overlay layer, like in Open Layers).

Maybe we should distinguish the WMS Capabilities Root layer case and the Earth Observation tree layer group "Root layer" case. The latter case's root layer is defined as: (from the docs)

The first case is actually translated as "Hauptlayer" and likely we should leave it like that.

For the second case, the meaning of the Root layer likely comes from the Earth Observations requirements/specs:

Earth Observation tree: a special type of group created to manage the WMS Earth Observation requirements. This group does not render its nested layers and groups, but only a “preview layer” called Root Layer. When this mode is chosen, a new field “Root Layer” will be exposed in the configuration UI.

I suggest translating it simply

"Vorschau-Layer" (Preview layer in English)

At its first occurence in the dialog I would append " (Root Layer)" for explanation and recognition.

Split the task

I do neither have a "general idea" nor have I planned exactly what to change/edit and when or created a couple of distinct tasks. I actually started with just translating those many not yet translated messages. During that, I stumbled over a couple of messages that, according to my mind, need some updates (concerning typos, style, correctness, clarity and consistency). Actually, that all must be called a general translation overhaul?

I started with the /web/core/src/main/resources/GeoServerApplication_de.properties file, which is now approx. 70% done. I will likely not finish much more before the 2.22.0 release. I've not yet touched the other files.

Not sure whether more people working on this are of help for more (style) consistency...

Tomorrow, I could commit my changes to a temporary branch in my own repo. You and others could then compare my changes to the original version of the language file in order to get a rough idea of what I'm actually doing :slight_smile:

Greets
Carsten

Am 15.11.2022 um 17:23 schrieb Marc Jansen:

Hi Carsten, list,

please find some comments inline.

Am 15.11.22 um 13:04 schrieb Carsten Klein:

Hello GeoServer devs and German translators,

as recommended by Jody Garnett, I've translated the new messages on the welcome page for the 2.22.0 release.

After that, I started to complete the German translation. In order to give the German UI a consistent appearance, I also need to change some of the already localized messages. The whole process will take some time and I will contribute batches of changes from time to time.

+1 for the efforts towards consistency, nice!

This affects work done by others (maybe long) before so, I'd like to ask whether you are fine with that and/or like to participate concerning some basic wording decisions. Since it's about really a lot of messages, we cannot discuss every change in advance. However, you could always review my upcoming PRs. I will be open for a discussion on any change made.

There are several goals:

- consistent wording and use of terms
- use common IT wording
- be more precise and descriptive (if required and possible)

Very likely, I won't reach all goals in a single step so, this is work in progress.

Maybe you coudl split the task once you have a general idea, I am sure we find others that help.

Nevertheless, I'd like to discuss renaming of some very basic terms in advance. Some of them are located at quite prominent places in the UI and so, may affect German users that have been used to the old terms for quite a long time.

1. Layer Group

Inconsistently translated:

"Gruppenlayer"
"Layergruppe"

Will change to "Gruppenlayer" (I guess it's the more common term).

I like "Gruppenlayer"

2. Root Layer

Inconsistently translated:

"Hauptlayer" (in WMS global settings)
"Wurzellayer" (in Layer Group Editor, type 'Earth Observetion Tree')

I tend to use "Wurzellayer" (like in "Wurzelvereichnis"). Due to the double "ll", for better readability writing it with a hyphen "Wurzel-Layer" may be an option. Any suggestions?

I do not like "Wurzellayer" or "Wurzel-Layer" (the longer I look at the words the more odd the look). How about "Hauptlayer" (not a 100 % match) or "Basislayer"?

Hard to translate, TBH.

3. Dimensions

Context: Layer Editor Tab "Dimensions" to enable Time and Elevation dimensions and to add custom dimensions.

Translated as:

"Ausdehnung" ("expansion" in English)

I guess, this term is misleading. More correct may actually be "Dimensionen", since in all major German GIS, features also have two or more dimensions like they do in English.

Yes, please use "Dimensionen", thankee-sai.

4. Publishing

Translated as:

"Publizierung"

My suggestion is to change this into "Veröffentlichung", which I guess is the more common term in German. However, this change may not be part of the first batch of German translation changes.

Yeah why not, indifferent here.

Thanks again and best regards.

Marc

The 2.22.0 release is scheduled for Friday, November 18th. In turn, I will issue the first PR on that on Thursday, November 17th. So, please send any suggestions and/or vetos prior to that date. If I get no such responses, I will assume that you are all fine with my proposed changes.

Cheers
Carsten

_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

4

Hi Marc,

maybe we could determine a couple of rules that specify how German translation should preferably look like. A derived set of rules could describe how existing translation should be modified, if required.

Greets
Carsten

Am 15.11.2022 um 17:23 schrieb Marc Jansen:

Hi Carsten, list,

please find some comments inline.

Am 15.11.22 um 13:04 schrieb Carsten Klein:

Hello GeoServer devs and German translators,

as recommended by Jody Garnett, I've translated the new messages on the welcome page for the 2.22.0 release.

After that, I started to complete the German translation. In order to give the German UI a consistent appearance, I also need to change some of the already localized messages. The whole process will take some time and I will contribute batches of changes from time to time.

+1 for the efforts towards consistency, nice!

This affects work done by others (maybe long) before so, I'd like to ask whether you are fine with that and/or like to participate concerning some basic wording decisions. Since it's about really a lot of messages, we cannot discuss every change in advance. However, you could always review my upcoming PRs. I will be open for a discussion on any change made.

There are several goals:

- consistent wording and use of terms
- use common IT wording
- be more precise and descriptive (if required and possible)

Very likely, I won't reach all goals in a single step so, this is work in progress.

Maybe you coudl split the task once you have a general idea, I am sure we find others that help.

Nevertheless, I'd like to discuss renaming of some very basic terms in advance. Some of them are located at quite prominent places in the UI and so, may affect German users that have been used to the old terms for quite a long time.

1. Layer Group

Inconsistently translated:

"Gruppenlayer"
"Layergruppe"

Will change to "Gruppenlayer" (I guess it's the more common term).

I like "Gruppenlayer"

2. Root Layer

Inconsistently translated:

"Hauptlayer" (in WMS global settings)
"Wurzellayer" (in Layer Group Editor, type 'Earth Observetion Tree')

I tend to use "Wurzellayer" (like in "Wurzelvereichnis"). Due to the double "ll", for better readability writing it with a hyphen "Wurzel-Layer" may be an option. Any suggestions?

I do not like "Wurzellayer" or "Wurzel-Layer" (the longer I look at the words the more odd the look). How about "Hauptlayer" (not a 100 % match) or "Basislayer"?

Hard to translate, TBH.

3. Dimensions

Context: Layer Editor Tab "Dimensions" to enable Time and Elevation dimensions and to add custom dimensions.

Translated as:

"Ausdehnung" ("expansion" in English)

I guess, this term is misleading. More correct may actually be "Dimensionen", since in all major German GIS, features also have two or more dimensions like they do in English.

Yes, please use "Dimensionen", thankee-sai.

4. Publishing

Translated as:

"Publizierung"

My suggestion is to change this into "Veröffentlichung", which I guess is the more common term in German. However, this change may not be part of the first batch of German translation changes.

Yeah why not, indifferent here.

Thanks again and best regards.

Marc

The 2.22.0 release is scheduled for Friday, November 18th. In turn, I will issue the first PR on that on Thursday, November 17th. So, please send any suggestions and/or vetos prior to that date. If I get no such responses, I will assume that you are all fine with my proposed changes.

Cheers
Carsten

_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

5

Hi Carsten,

makes sense, but hard to do. I am not a professional translator myself …

Best

Marc

Am 16.11.22 um 08:12 schrieb Carsten Klein:

Hi Marc,

maybe we could determine a couple of rules that specify how German translation should preferably look like. A derived set of rules could describe how existing translation should be modified, if required.

Greets
Carsten

Am 15.11.2022 um 17:23 schrieb Marc Jansen:

Hi Carsten, list,

please find some comments inline.

Am 15.11.22 um 13:04 schrieb Carsten Klein:

Hello GeoServer devs and German translators,

as recommended by Jody Garnett, I've translated the new messages on the welcome page for the 2.22.0 release.

After that, I started to complete the German translation. In order to give the German UI a consistent appearance, I also need to change some of the already localized messages. The whole process will take some time and I will contribute batches of changes from time to time.

+1 for the efforts towards consistency, nice!

This affects work done by others (maybe long) before so, I'd like to ask whether you are fine with that and/or like to participate concerning some basic wording decisions. Since it's about really a lot of messages, we cannot discuss every change in advance. However, you could always review my upcoming PRs. I will be open for a discussion on any change made.

There are several goals:

- consistent wording and use of terms
- use common IT wording
- be more precise and descriptive (if required and possible)

Very likely, I won't reach all goals in a single step so, this is work in progress.

Maybe you coudl split the task once you have a general idea, I am sure we find others that help.

Nevertheless, I'd like to discuss renaming of some very basic terms in advance. Some of them are located at quite prominent places in the UI and so, may affect German users that have been used to the old terms for quite a long time.

1. Layer Group

Inconsistently translated:

"Gruppenlayer"
"Layergruppe"

Will change to "Gruppenlayer" (I guess it's the more common term).

I like "Gruppenlayer"

2. Root Layer

Inconsistently translated:

"Hauptlayer" (in WMS global settings)
"Wurzellayer" (in Layer Group Editor, type 'Earth Observetion Tree')

I tend to use "Wurzellayer" (like in "Wurzelvereichnis"). Due to the double "ll", for better readability writing it with a hyphen "Wurzel-Layer" may be an option. Any suggestions?

I do not like "Wurzellayer" or "Wurzel-Layer" (the longer I look at the words the more odd the look). How about "Hauptlayer" (not a 100 % match) or "Basislayer"?

Hard to translate, TBH.

3. Dimensions

Context: Layer Editor Tab "Dimensions" to enable Time and Elevation dimensions and to add custom dimensions.

Translated as:

"Ausdehnung" ("expansion" in English)

I guess, this term is misleading. More correct may actually be "Dimensionen", since in all major German GIS, features also have two or more dimensions like they do in English.

Yes, please use "Dimensionen", thankee-sai.

4. Publishing

Translated as:

"Publizierung"

My suggestion is to change this into "Veröffentlichung", which I guess is the more common term in German. However, this change may not be part of the first batch of German translation changes.

Yeah why not, indifferent here.

Thanks again and best regards.

Marc

The 2.22.0 release is scheduled for Friday, November 18th. In turn, I will issue the first PR on that on Thursday, November 17th. So, please send any suggestions and/or vetos prior to that date. If I get no such responses, I will assume that you are all fine with my proposed changes.

Cheers
Carsten

_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

6

Hi Marc,

I'm also not a professional translator but have quite some experiences with finding appropriate UI texts for my company's products and applications... In any case, it's a hard job :frowning:

I will commit current stage of the translation to my repo this day and create a (local) PR against the main branch, so people can easily see my changes. I'll send the corresponding URL to the dev list.

VG Carsten

Am 16.11.2022 um 10:26 schrieb Marc Jansen:

Hi Carsten,

makes sense, but hard to do. I am not a professional translator myself …

Best

Marc

Am 16.11.22 um 08:12 schrieb Carsten Klein:

Hi Marc,

maybe we could determine a couple of rules that specify how German translation should preferably look like. A derived set of rules could describe how existing translation should be modified, if required.

Greets
Carsten

Am 15.11.2022 um 17:23 schrieb Marc Jansen:

Hi Carsten, list,

please find some comments inline.

Am 15.11.22 um 13:04 schrieb Carsten Klein:

Hello GeoServer devs and German translators,

as recommended by Jody Garnett, I've translated the new messages on the welcome page for the 2.22.0 release.

After that, I started to complete the German translation. In order to give the German UI a consistent appearance, I also need to change some of the already localized messages. The whole process will take some time and I will contribute batches of changes from time to time.

+1 for the efforts towards consistency, nice!

This affects work done by others (maybe long) before so, I'd like to ask whether you are fine with that and/or like to participate concerning some basic wording decisions. Since it's about really a lot of messages, we cannot discuss every change in advance. However, you could always review my upcoming PRs. I will be open for a discussion on any change made.

There are several goals:

- consistent wording and use of terms
- use common IT wording
- be more precise and descriptive (if required and possible)

Very likely, I won't reach all goals in a single step so, this is work in progress.

Maybe you coudl split the task once you have a general idea, I am sure we find others that help.

Nevertheless, I'd like to discuss renaming of some very basic terms in advance. Some of them are located at quite prominent places in the UI and so, may affect German users that have been used to the old terms for quite a long time.

1. Layer Group

Inconsistently translated:

"Gruppenlayer"
"Layergruppe"

Will change to "Gruppenlayer" (I guess it's the more common term).

I like "Gruppenlayer"

2. Root Layer

Inconsistently translated:

"Hauptlayer" (in WMS global settings)
"Wurzellayer" (in Layer Group Editor, type 'Earth Observetion Tree')

I tend to use "Wurzellayer" (like in "Wurzelvereichnis"). Due to the double "ll", for better readability writing it with a hyphen "Wurzel-Layer" may be an option. Any suggestions?

I do not like "Wurzellayer" or "Wurzel-Layer" (the longer I look at the words the more odd the look). How about "Hauptlayer" (not a 100 % match) or "Basislayer"?

Hard to translate, TBH.

3. Dimensions

Context: Layer Editor Tab "Dimensions" to enable Time and Elevation dimensions and to add custom dimensions.

Translated as:

"Ausdehnung" ("expansion" in English)

I guess, this term is misleading. More correct may actually be "Dimensionen", since in all major German GIS, features also have two or more dimensions like they do in English.

Yes, please use "Dimensionen", thankee-sai.

4. Publishing

Translated as:

"Publizierung"

My suggestion is to change this into "Veröffentlichung", which I guess is the more common term in German. However, this change may not be part of the first batch of German translation changes.

Yeah why not, indifferent here.

Thanks again and best regards.

Marc

The 2.22.0 release is scheduled for Friday, November 18th. In turn, I will issue the first PR on that on Thursday, November 17th. So, please send any suggestions and/or vetos prior to that date. If I get no such responses, I will assume that you are all fine with my proposed changes.

Cheers
Carsten

_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

7
  1. Root Layer

Inconsistently translated:

“Hauptlayer” (in WMS global settings)
“Wurzellayer” (in Layer Group Editor, type ‘Earth Observetion Tree’)

I tend to use “Wurzellayer” (like in “Wurzelvereichnis”). Due to the
double “ll”, for better readability writing it with a hyphen
“Wurzel-Layer” may be an option. Any suggestions?

I do not like “Wurzellayer” or “Wurzel-Layer” (the longer I look at the
words the more odd the look). How about “Hauptlayer” (not a 100 % match)
or “Basislayer”?

Hard to translate, TBH.

The root indicates it is the root of the tree data structure; however that is more a computer science idea/concept.

If I explain the idea in english I indicate it is the top layer or the parent layer and all the other layers are children that inherit the values (such as the coordinate reference system list) from the top layer.

Google translate gives me “Oberstelayer” for upper or uppermost - may be a good fit?

8

Hi there,

now, theres a (local) PR in my repo to show, primarily to German translators, how I’m updating German translation.

https://github.com/cklein05/geoserver/pull/2

I will soon add in a PR comment that describes, what’s already finished and what not. Have a look at the changed files to get an idea of what my work is like. Feel free to comment…

@Jody: I decided to call it “Preview-Layer” (Vorschau-Layer in German) in the context of an Earth Observation tree Layer Group and leave it “Main-Layer” (Hauptlayer in German) in the context of the GetCapabilities response.

Google’s translation seems like a wrongly written version of “top-most layer” :slight_smile:

@Jody: If my changes are acceptable, I will issue the same PR (more or less, maybe including some last small changes) against the official GS main branch tomorrow, so you are able to include it in the 2.22.0 release on Friday. Although it’s not yet complete (maybe it will never be complete), its much better/more complete than before and, most important, the new messages on the welcome page have been translated successfully.

Cheers
Carsten

···

Am 16.11.2022 um 16:50 schrieb Jody Garnett:

  1. Root Layer

Inconsistently translated:

“Hauptlayer” (in WMS global settings)
“Wurzellayer” (in Layer Group Editor, type ‘Earth Observetion Tree’)

I tend to use “Wurzellayer” (like in “Wurzelvereichnis”). Due to the
double “ll”, for better readability writing it with a hyphen
“Wurzel-Layer” may be an option. Any suggestions?

I do not like “Wurzellayer” or “Wurzel-Layer” (the longer I look at the
words the more odd the look). How about “Hauptlayer” (not a 100 % match)
or “Basislayer”?

Hard to translate, TBH.

The root indicates it is the root of the tree data structure; however that is more a computer science idea/concept.

If I explain the idea in english I indicate it is the top layer or the parent layer and all the other layers are children that inherit the values (such as the coordinate reference system list) from the top layer.

Google translate gives me “Oberstelayer” for upper or uppermost - may be a good fit?

_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@lists.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)
9

Andrea is starting the release process tomorrow with geotools; so please make your PR and backport as soon as possible!

···

–
Jody Garnett

10

PR against main will be available tomorrow, 7:30 CET. I can’t add labels, so please, someone should kick off backports (2.22.x should be sufficient)

Carsten

Von meinem/meiner Galaxy gesendet

···

–
Jody Garnett

11

Final PR #6359 German Translation Overhaul Part 1 is now available and all green.

https://github.com/geoserver/geoserver/pull/6359

Please backport someone to 2.22.x, as I can’t add any labels without repo write access (thinking about requesting write access, as it could actually make some things a bit easier).

Cheers
Carsten

···

Am 16.11.2022 um 21:08 schrieb Carsten Klein:

PR against main will be available tomorrow, 7:30 CET. I can’t add labels, so please, someone should kick off backports (2.22.x should be sufficient)

Carsten

Von meinem/meiner Galaxy gesendet

-------- Ursprüngliche Nachricht --------
Von: Jody Garnett jody.garnett@anonymised.com
Datum: 16.11.22 20:38 (GMT+01:00)
An: Carsten Klein c.klein@anonymised.com
Cc: Marc Jansen jansen@anonymised.com, geoserver-devel@lists.sourceforge.net
Betreff: Re: [Geoserver-devel] Completing and Updating German translation

Andrea is starting the release process tomorrow with geotools; so please make your PR and backport as soon as possible!

–
Jody Garnett

On Wed, 16 Nov 2022 at 08:35, Carsten Klein <c.klein@anonymised.com> wrote:

Hi there,

now, theres a (local) PR in my repo to show, primarily to German translators, how I’m updating German translation.

https://github.com/cklein05/geoserver/pull/2

I will soon add in a PR comment that describes, what’s already finished and what not. Have a look at the changed files to get an idea of what my work is like. Feel free to comment…

@Jody: I decided to call it “Preview-Layer” (Vorschau-Layer in German) in the context of an Earth Observation tree Layer Group and leave it “Main-Layer” (Hauptlayer in German) in the context of the GetCapabilities response.

Google’s translation seems like a wrongly written version of “top-most layer” :slight_smile:

@Jody: If my changes are acceptable, I will issue the same PR (more or less, maybe including some last small changes) against the official GS main branch tomorrow, so you are able to include it in the 2.22.0 release on Friday. Although it’s not yet complete (maybe it will never be complete), its much better/more complete than before and, most important, the new messages on the welcome page have been translated successfully.

Cheers
Carsten

Am 16.11.2022 um 16:50 schrieb Jody Garnett:

  1. Root Layer

Inconsistently translated:

“Hauptlayer” (in WMS global settings)
“Wurzellayer” (in Layer Group Editor, type ‘Earth Observetion Tree’)

I tend to use “Wurzellayer” (like in “Wurzelvereichnis”). Due to the
double “ll”, for better readability writing it with a hyphen
“Wurzel-Layer” may be an option. Any suggestions?

I do not like “Wurzellayer” or “Wurzel-Layer” (the longer I look at the
words the more odd the look). How about “Hauptlayer” (not a 100 % match)
or “Basislayer”?

Hard to translate, TBH.

The root indicates it is the root of the tree data structure; however that is more a computer science idea/concept.

If I explain the idea in english I indicate it is the top layer or the parent layer and all the other layers are children that inherit the values (such as the coordinate reference system list) from the top layer.

Google translate gives me “Oberstelayer” for upper or uppermost - may be a good fit?

_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@lists.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)


_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@lists.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)
12

Thanks, applied and backported.

···

–
Jody Garnett

13

I just uploaded these new translations to Transifex.

Alexandre

···

Alexandre Gacon

14

OK, will have a look at Transifex.

@Alexandre Merci and thanks for helping out :slight_smile:

Carsten

···

Am 17.11.2022 um 08:06 schrieb Alexandre Gacon:

I just uploaded these new translations to Transifex.

Alexandre

Le jeu. 17 nov. 2022 à 07:19, Jody Garnett <jody.garnett@anonymised.com> a écrit :

Thanks, applied and backported.

–
Jody Garnett

On Wed, 16 Nov 2022 at 22:13, Carsten Klein <c.klein@anonymised.com> wrote:

Final PR #6359 German Translation Overhaul Part 1 is now available and all green.

https://github.com/geoserver/geoserver/pull/6359

Please backport someone to 2.22.x, as I can’t add any labels without repo write access (thinking about requesting write access, as it could actually make some things a bit easier).

Cheers
Carsten

Am 16.11.2022 um 21:08 schrieb Carsten Klein:

PR against main will be available tomorrow, 7:30 CET. I can’t add labels, so please, someone should kick off backports (2.22.x should be sufficient)

Carsten

Von meinem/meiner Galaxy gesendet

-------- Ursprüngliche Nachricht --------
Von: Jody Garnett jody.garnett@anonymised.com
Datum: 16.11.22 20:38 (GMT+01:00)
An: Carsten Klein c.klein@anonymised.com
Cc: Marc Jansen jansen@anonymised.com, geoserver-devel@lists.sourceforge.net
Betreff: Re: [Geoserver-devel] Completing and Updating German translation

Andrea is starting the release process tomorrow with geotools; so please make your PR and backport as soon as possible!

–
Jody Garnett

On Wed, 16 Nov 2022 at 08:35, Carsten Klein <c.klein@anonymised.com> wrote:

Hi there,

now, theres a (local) PR in my repo to show, primarily to German translators, how I’m updating German translation.

https://github.com/cklein05/geoserver/pull/2

I will soon add in a PR comment that describes, what’s already finished and what not. Have a look at the changed files to get an idea of what my work is like. Feel free to comment…

@Jody: I decided to call it “Preview-Layer” (Vorschau-Layer in German) in the context of an Earth Observation tree Layer Group and leave it “Main-Layer” (Hauptlayer in German) in the context of the GetCapabilities response.

Google’s translation seems like a wrongly written version of “top-most layer” :slight_smile:

@Jody: If my changes are acceptable, I will issue the same PR (more or less, maybe including some last small changes) against the official GS main branch tomorrow, so you are able to include it in the 2.22.0 release on Friday. Although it’s not yet complete (maybe it will never be complete), its much better/more complete than before and, most important, the new messages on the welcome page have been translated successfully.

Cheers
Carsten

Am 16.11.2022 um 16:50 schrieb Jody Garnett:

  1. Root Layer

Inconsistently translated:

“Hauptlayer” (in WMS global settings)
“Wurzellayer” (in Layer Group Editor, type ‘Earth Observetion Tree’)

I tend to use “Wurzellayer” (like in “Wurzelvereichnis”). Due to the
double “ll”, for better readability writing it with a hyphen
“Wurzel-Layer” may be an option. Any suggestions?

I do not like “Wurzellayer” or “Wurzel-Layer” (the longer I look at the
words the more odd the look). How about “Hauptlayer” (not a 100 % match)
or “Basislayer”?

Hard to translate, TBH.

The root indicates it is the root of the tree data structure; however that is more a computer science idea/concept.

If I explain the idea in english I indicate it is the top layer or the parent layer and all the other layers are children that inherit the values (such as the coordinate reference system list) from the top layer.

Google translate gives me “Oberstelayer” for upper or uppermost - may be a good fit?

_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@lists.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)


_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@lists.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

Alexandre Gacon

15

Does someone has changed the checks when we only change translations? I have only one check now.

···

Alexandre Gacon

16

On 17-11-2022 12:28, Alexandre Gacon wrote:

Does someone has changed the checks when we only change translations? I have only one check now.

the checks depend on the files changed, see

https://github.com/geoserver/geoserver/blob/c83a3f05d9b5d6eed16cc3b79071fd4e07a24ce8/.github/workflows/linux_jdk11.yml#L3-L7

so if only GeoServerApplication_*.properties (where * does not include fr_ the other build checks will be skipped and only the docs should run

17

Hello there,

is it correct, that new latest/current translations are in the GeoServer GitHub Integration project? If so, Alexandre, didn’t you update/upload German translation for project src/web/demo (web_demo in transifex)? Actually, the last update of web_demo is ~9 days ago (Nov, 9th 2022)… If not, I could update this resource (being my first transifex action…).

Cheers
Carsten

(attachments)

ATT223450.txt (2 Bytes)
Nachrichtenteil als Anhang (182 Bytes)

···

Am 17.11.2022 um 08:06 schrieb Alexandre Gacon:

I just uploaded these new translations to Transifex.

Alexandre

Le jeu. 17 nov. 2022 à 07:19, Jody Garnett <jody.garnett@anonymised.com> a écrit :

Thanks, applied and backported.

–
Jody Garnett

On Wed, 16 Nov 2022 at 22:13, Carsten Klein <c.klein@anonymised.com> wrote:

Final PR #6359 German Translation Overhaul Part 1 is now available and all green.

https://github.com/geoserver/geoserver/pull/6359

Please backport someone to 2.22.x, as I can’t add any labels without repo write access (thinking about requesting write access, as it could actually make some things a bit easier).

Cheers
Carsten

Am 16.11.2022 um 21:08 schrieb Carsten Klein:

PR against main will be available tomorrow, 7:30 CET. I can’t add labels, so please, someone should kick off backports (2.22.x should be sufficient)

Carsten

Von meinem/meiner Galaxy gesendet

-------- Ursprüngliche Nachricht --------
Von: Jody Garnett jody.garnett@anonymised.com
Datum: 16.11.22 20:38 (GMT+01:00)
An: Carsten Klein c.klein@anonymised.com
Cc: Marc Jansen jansen@anonymised.com, geoserver-devel@lists.sourceforge.net
Betreff: Re: [Geoserver-devel] Completing and Updating German translation

Andrea is starting the release process tomorrow with geotools; so please make your PR and backport as soon as possible!

–
Jody Garnett

On Wed, 16 Nov 2022 at 08:35, Carsten Klein <c.klein@anonymised.com> wrote:

Hi there,

now, theres a (local) PR in my repo to show, primarily to German translators, how I’m updating German translation.

https://github.com/cklein05/geoserver/pull/2

I will soon add in a PR comment that describes, what’s already finished and what not. Have a look at the changed files to get an idea of what my work is like. Feel free to comment…

@Jody: I decided to call it “Preview-Layer” (Vorschau-Layer in German) in the context of an Earth Observation tree Layer Group and leave it “Main-Layer” (Hauptlayer in German) in the context of the GetCapabilities response.

Google’s translation seems like a wrongly written version of “top-most layer” :slight_smile:

@Jody: If my changes are acceptable, I will issue the same PR (more or less, maybe including some last small changes) against the official GS main branch tomorrow, so you are able to include it in the 2.22.0 release on Friday. Although it’s not yet complete (maybe it will never be complete), its much better/more complete than before and, most important, the new messages on the welcome page have been translated successfully.

Cheers
Carsten

Am 16.11.2022 um 16:50 schrieb Jody Garnett:

  1. Root Layer

Inconsistently translated:

“Hauptlayer” (in WMS global settings)
“Wurzellayer” (in Layer Group Editor, type ‘Earth Observetion Tree’)

I tend to use “Wurzellayer” (like in “Wurzelvereichnis”). Due to the
double “ll”, for better readability writing it with a hyphen
“Wurzel-Layer” may be an option. Any suggestions?

I do not like “Wurzellayer” or “Wurzel-Layer” (the longer I look at the
words the more odd the look). How about “Hauptlayer” (not a 100 % match)
or “Basislayer”?

Hard to translate, TBH.

The root indicates it is the root of the tree data structure; however that is more a computer science idea/concept.

If I explain the idea in english I indicate it is the top layer or the parent layer and all the other layers are children that inherit the values (such as the coordinate reference system list) from the top layer.

Google translate gives me “Oberstelayer” for upper or uppermost - may be a good fit?

_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@lists.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)


_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@lists.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

Alexandre Gacon

18

Hi,

I indeed pushed the translation and source files this week before the release.

Did you make some changes you cannot find?

Alexandre

Le sam. 19 nov. 2022 à 11:56, Carsten Klein <c.klein@anonymised.com> a écrit :

Hello there,

is it correct, that new latest/current translations are in the GeoServer GitHub Integration project? If so, Alexandre, didn’t you update/upload German translation for project src/web/demo (web_demo in transifex)? Actually, the last update of web_demo is ~9 days ago (Nov, 9th 2022)… If not, I could update this resource (being my first transifex action…).

Cheers
Carsten

Am 17.11.2022 um 08:06 schrieb Alexandre Gacon:

I just uploaded these new translations to Transifex.

Alexandre

Le jeu. 17 nov. 2022 à 07:19, Jody Garnett <jody.garnett@anonymised.com> a écrit :

Thanks, applied and backported.

–
Jody Garnett

On Wed, 16 Nov 2022 at 22:13, Carsten Klein <c.klein@anonymised.com> wrote:

Final PR #6359 German Translation Overhaul Part 1 is now available and all green.

https://github.com/geoserver/geoserver/pull/6359

Please backport someone to 2.22.x, as I can’t add any labels without repo write access (thinking about requesting write access, as it could actually make some things a bit easier).

Cheers
Carsten

Am 16.11.2022 um 21:08 schrieb Carsten Klein:

PR against main will be available tomorrow, 7:30 CET. I can’t add labels, so please, someone should kick off backports (2.22.x should be sufficient)

Carsten

Von meinem/meiner Galaxy gesendet

-------- Ursprüngliche Nachricht --------
Von: Jody Garnett jody.garnett@anonymised.com
Datum: 16.11.22 20:38 (GMT+01:00)
An: Carsten Klein c.klein@anonymised.com
Cc: Marc Jansen jansen@anonymised.com, geoserver-devel@anonymised.comnet
Betreff: Re: [Geoserver-devel] Completing and Updating German translation

Andrea is starting the release process tomorrow with geotools; so please make your PR and backport as soon as possible!

–
Jody Garnett

On Wed, 16 Nov 2022 at 08:35, Carsten Klein <c.klein@anonymised.com> wrote:

Hi there,

now, theres a (local) PR in my repo to show, primarily to German translators, how I’m updating German translation.

https://github.com/cklein05/geoserver/pull/2

I will soon add in a PR comment that describes, what’s already finished and what not. Have a look at the changed files to get an idea of what my work is like. Feel free to comment…

@Jody: I decided to call it “Preview-Layer” (Vorschau-Layer in German) in the context of an Earth Observation tree Layer Group and leave it “Main-Layer” (Hauptlayer in German) in the context of the GetCapabilities response.

Google’s translation seems like a wrongly written version of “top-most layer” :slight_smile:

@Jody: If my changes are acceptable, I will issue the same PR (more or less, maybe including some last small changes) against the official GS main branch tomorrow, so you are able to include it in the 2.22.0 release on Friday. Although it’s not yet complete (maybe it will never be complete), its much better/more complete than before and, most important, the new messages on the welcome page have been translated successfully.

Cheers
Carsten

Am 16.11.2022 um 16:50 schrieb Jody Garnett:

  1. Root Layer

Inconsistently translated:

“Hauptlayer” (in WMS global settings)
“Wurzellayer” (in Layer Group Editor, type ‘Earth Observetion Tree’)

I tend to use “Wurzellayer” (like in “Wurzelvereichnis”). Due to the
double “ll”, for better readability writing it with a hyphen
“Wurzel-Layer” may be an option. Any suggestions?

I do not like “Wurzellayer” or “Wurzel-Layer” (the longer I look at the
words the more odd the look). How about “Hauptlayer” (not a 100 % match)
or “Basislayer”?

Hard to translate, TBH.

The root indicates it is the root of the tree data structure; however that is more a computer science idea/concept.

If I explain the idea in english I indicate it is the top layer or the parent layer and all the other layers are children that inherit the values (such as the coordinate reference system list) from the top layer.

Google translate gives me “Oberstelayer” for upper or uppermost - may be a good fit?

_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@lists.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)


_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@lists.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

Alexandre Gacon

19

Hi Alexandre,

yes, I#m missing some of my changes. I’ve fully translated the German messages file for project src/web/demo. In transifex this file is located in folder web_demo. However, this file seems not being updated in transifex:

It has been updated almost 10 days ago. Also, it says that only ~12% have been translated. None of my changes of this file are actually in transifex (I’ve downloaded the file). Maybe you just forgot updating this file? If so, I could upload the recent version of this file…

BTW, how’s the round-trip between transifex and GeoServer’s GitHub repository. I tend to edit message files in Eclipse, so I can immediately view results in the UI. After a bunch of messages files is complete, shall I issue a normal PR in GitHub AND upload the file to transifex? Or is it recommended to only upload to transifex and transifex will in turn update these files in GitHub? How to initiate this push in transifex? Likely it may be a problem that, I do not (yet) have write access to GeoServer’s repository.

Carsten

···

Am 19.11.2022 um 12:35 schrieb Alexandre Gacon:

Hi,

I indeed pushed the translation and source files this week before the release.

Did you make some changes you cannot find?

Alexandre

Le sam. 19 nov. 2022 à 11:56, Carsten Klein <c.klein@anonymised.com> a écrit :

Hello there,

is it correct, that new latest/current translations are in the GeoServer GitHub Integration project? If so, Alexandre, didn’t you update/upload German translation for project src/web/demo (web_demo in transifex)? Actually, the last update of web_demo is ~9 days ago (Nov, 9th 2022)… If not, I could update this resource (being my first transifex action…).

Cheers
Carsten

Am 17.11.2022 um 08:06 schrieb Alexandre Gacon:

I just uploaded these new translations to Transifex.

Alexandre

Le jeu. 17 nov. 2022 à 07:19, Jody Garnett <jody.garnett@anonymised.com> a écrit :

Thanks, applied and backported.

–
Jody Garnett

On Wed, 16 Nov 2022 at 22:13, Carsten Klein <c.klein@anonymised.com> wrote:

Final PR #6359 German Translation Overhaul Part 1 is now available and all green.

https://github.com/geoserver/geoserver/pull/6359

Please backport someone to 2.22.x, as I can’t add any labels without repo write access (thinking about requesting write access, as it could actually make some things a bit easier).

Cheers
Carsten

Am 16.11.2022 um 21:08 schrieb Carsten Klein:

PR against main will be available tomorrow, 7:30 CET. I can’t add labels, so please, someone should kick off backports (2.22.x should be sufficient)

Carsten

Von meinem/meiner Galaxy gesendet

-------- Ursprüngliche Nachricht --------
Von: Jody Garnett jody.garnett@anonymised.com
Datum: 16.11.22 20:38 (GMT+01:00)
An: Carsten Klein c.klein@anonymised.com
Cc: Marc Jansen jansen@anonymised.com, geoserver-devel@lists.sourceforge.net
Betreff: Re: [Geoserver-devel] Completing and Updating German translation

Andrea is starting the release process tomorrow with geotools; so please make your PR and backport as soon as possible!

–
Jody Garnett

On Wed, 16 Nov 2022 at 08:35, Carsten Klein <c.klein@anonymised.com> wrote:

Hi there,

now, theres a (local) PR in my repo to show, primarily to German translators, how I’m updating German translation.

https://github.com/cklein05/geoserver/pull/2

I will soon add in a PR comment that describes, what’s already finished and what not. Have a look at the changed files to get an idea of what my work is like. Feel free to comment…

@Jody: I decided to call it “Preview-Layer” (Vorschau-Layer in German) in the context of an Earth Observation tree Layer Group and leave it “Main-Layer” (Hauptlayer in German) in the context of the GetCapabilities response.

Google’s translation seems like a wrongly written version of “top-most layer” :slight_smile:

@Jody: If my changes are acceptable, I will issue the same PR (more or less, maybe including some last small changes) against the official GS main branch tomorrow, so you are able to include it in the 2.22.0 release on Friday. Although it’s not yet complete (maybe it will never be complete), its much better/more complete than before and, most important, the new messages on the welcome page have been translated successfully.

Cheers
Carsten

Am 16.11.2022 um 16:50 schrieb Jody Garnett:

  1. Root Layer

Inconsistently translated:

“Hauptlayer” (in WMS global settings)
“Wurzellayer” (in Layer Group Editor, type ‘Earth Observetion Tree’)

I tend to use “Wurzellayer” (like in “Wurzelvereichnis”). Due to the
double “ll”, for better readability writing it with a hyphen
“Wurzel-Layer” may be an option. Any suggestions?

I do not like “Wurzellayer” or “Wurzel-Layer” (the longer I look at the
words the more odd the look). How about “Hauptlayer” (not a 100 % match)
or “Basislayer”?

Hard to translate, TBH.

The root indicates it is the root of the tree data structure; however that is more a computer science idea/concept.

If I explain the idea in english I indicate it is the top layer or the parent layer and all the other layers are children that inherit the values (such as the coordinate reference system list) from the top layer.

Google translate gives me “Oberstelayer” for upper or uppermost - may be a good fit?

_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@lists.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)


_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@lists.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

Alexandre Gacon

20

Hi Carstein,

In fact I didn’t configure the transifex sync for this resource yet. That’s the reason why you don’t see your translations. I will fix it right now.

For the process you can either continue to edit the message files in Eclipse or you can work with Transifex : I am doing the synchronisation both ways. I don’t have either the write access to the GeoServer repo so I am doing PR when I want to do the sync. I have to use a local client to do the sync between Transifex and my fork. One of my goal is to migrate by a weblate instance managed by OSGEO in order to be able to have a direct sync between weblate and GitHub.

Regards
Alexandre

(attachments)

0cstvxdQnzzLhpZV.png

···

Alexandre Gacon