We added configurable walk & bike speeds to OTP, and now all of the
translations are out-of-date. I updated them as best as I could, but I
am only fluent in English, so mostly they are whatever Google Translate
gave me.
I had a look into the German translations.
I attach a patch created from within the opentripplanner-webapp project. It is the first one I have ever made with git... so let me know if I should do it differently.
Also I found a couple of strings that I would like to revise while seeing it on screen. Is there a way/setting to force OTP to start with a certain language? (client side or server side?)
With respect to the problems with some strings. I got in particularly confused with (from the English.js) :
format : "F jS, Y @ g:ia",
date_format : "n/j/Y",
time_format : "g:ia",
What does @ and g:ia mean? why is there "jS" what is an "n" => I would have expected D M Y h:s, or so for english?
And I got also confused with the single letters provided for the bike triangle.
Maybe you need to re-adjust these strings - if these are key strokes or java format settings???
> We added configurable walk & bike speeds to OTP, and now all of the
> translations are out-of-date. I updated them as best as I could, but I
> am only fluent in English, so mostly they are whatever Google Translate
> gave me.
> I had a look into the German translations.
> I attach a patch created from within the opentripplanner-webapp project. It is the first one I have ever made with git... so let me know if I should do it differently.
> Also I found a couple of strings that I would like to revise while seeing it on screen. Is there a way/setting to force OTP to start with a certain language? (client side or server side?)
> With respect to the problems with some strings. I got in particularly confused with (from the English.js) :
> format : "F jS, Y @ g:ia",
> date_format : "n/j/Y",
> time_format : "g:ia",
> What does @ and g:ia mean? why is there "jS" what is an "n" => I would have expected D M Y h:s, or so for english?
> And I got also confused with the single letters provided for the bike triangle.
> Maybe you need to re-adjust these strings - if these are key strokes or java format settings???
> cheers,
> stefan
> Am 16.10.12 18:09, schrieb David Turner:
>> We added configurable walk & bike speeds to OTP, and now all of the
>> translations are out-of-date. I updated them as best as I could, but I
>> am only fluent in English, so mostly they are whatever Google Translate
>> gave me.
On Mon, 2012-10-22 at 15:24 -0300, Stefan Steiniger wrote:
> Hi David,
> I had a look into the German translations.
> I attach a patch created from within the opentripplanner-webapp project. > It is the first one I have ever made with git... so let me know if I > should do it differently.
That's perfect, thanks.
> Also I found a couple of strings that I would like to revise while > seeing it on screen. Is there a way/setting to force OTP to start with a > certain language? (client side or server side?)
Yes, in config.js, replace English with German.
> With respect to the problems with some strings. I got in particularly > confused with (from the English.js) :
> format : "F jS, Y @ g:ia",
> date_format : "n/j/Y",
> time_format : "g:ia",
> What does @ and g:ia mean? why is there "jS" what is an "n" => I would > have expected D M Y h:s, or so for english?
@ means "@". g is the 12-hour time (so, instead of 22:00, 8:00, and a
is "am" or "pm").
n is 9 instead of 09 for September; j is the same for days.
> And I got also confused with the single letters provided for the bike > triangle.
Those go at the corners of the triangle as a hint to users of what the
corners mean.
I have made some more improvements to the German language file.
Please find the patch attached.
I also notice missing translation options for:
- Trip tab title/header: There is a "X to Y". So "to" would need to be replaced
- for corner situations/snaps it is written "corner of X and Y". Couldn't see how to replace that.
> On Mon, 2012-10-22 at 15:24 -0300, Stefan Steiniger wrote:
>> Hi David,
>> I had a look into the German translations.
>> I attach a patch created from within the opentripplanner-webapp project.
>> It is the first one I have ever made with git... so let me know if I
>> should do it differently.
> That's perfect, thanks.
>> Also I found a couple of strings that I would like to revise while
>> seeing it on screen. Is there a way/setting to force OTP to start with a
>> certain language? (client side or server side?)
> Yes, in config.js, replace English with German.
>> With respect to the problems with some strings. I got in particularly
>> confused with (from the English.js) :
>> format : "F jS, Y @ g:ia",
>> date_format : "n/j/Y",
>> time_format : "g:ia",
>> What does @ and g:ia mean? why is there "jS" what is an "n" => I would
>> have expected D M Y h:s, or so for english?
> @ means "@". g is the 12-hour time (so, instead of 22:00, 8:00, and a
> is "am" or "pm").
> n is 9 instead of 09 for September; j is the same for days.
>> And I got also confused with the single letters provided for the bike
>> triangle.
> Those go at the corners of the triangle as a hint to users of what the
> corners mean.
On Thu, 2012-11-01 at 14:57 -0300, Stefan Steiniger wrote:
> Hi David,
> I have made some more improvements to the German language file.
> Please find the patch attached.
Applied, thanks! If you like, I can just give you commit access so that
you can push the changes yourself. Just let me know your github
username and I'll add you to the project.
> I also notice missing translation options for:
> - Trip tab title/header: There is a "X to Y". So "to" would need to be > replaced
OK, we'll look into that.
> - for corner situations/snaps it is written "corner of X and Y". > Couldn't see how to replace that.
That's in
opentripplanner-routing/src/main/resources/internals_de.properties
See opentripplanner-routing/src/main/resources/internals.properties
for an example
I just made this internationalizable a week or two ago; your translation
will be the first.
> On Thu, 2012-11-01 at 14:57 -0300, Stefan Steiniger wrote:
>> Hi David,
>> I have made some more improvements to the German language file.
>> Please find the patch attached.
> Applied, thanks! If you like, I can just give you commit access so that
> you can push the changes yourself. Just let me know your github
> username and I'll add you to the project.
>> I also notice missing translation options for:
>> - Trip tab title/header: There is a "X to Y". So "to" would need to be
>> replaced
> OK, we'll look into that.
>> - for corner situations/snaps it is written "corner of X and Y".
>> Couldn't see how to replace that.
> That's in
> opentripplanner-routing/src/main/resources/internals_de.properties
> See
> opentripplanner-routing/src/main/resources/internals.properties
> for an example
> I just made this internationalizable a week or two ago; your translation
> will be the first.
On Thu, 2012-11-01 at 17:30 -0300, Stefan Steiniger wrote:
> Hi again,
> I couldn't find an unnamed road in my data to see how it looks like - > but the corner description is resolved/translated :)
> Find attached the new internals_de.properties file.
> cheers,
> stefan
> Am 01.11.12 15:38, schrieb David Turner:
> > On Thu, 2012-11-01 at 14:57 -0300, Stefan Steiniger wrote:
> >> Hi David,
> >> I have made some more improvements to the German language file.
> >> Please find the patch attached.
> > Applied, thanks! If you like, I can just give you commit access so that
> > you can push the changes yourself. Just let me know your github
> > username and I'll add you to the project.
> >> I also notice missing translation options for:
> >> - Trip tab title/header: There is a "X to Y". So "to" would need to be
> >> replaced
> > OK, we'll look into that.
> >> - for corner situations/snaps it is written "corner of X and Y".
> >> Couldn't see how to replace that.
> > That's in
> > opentripplanner-routing/src/main/resources/internals_de.properties
> > See
> > opentripplanner-routing/src/main/resources/internals.properties
> > for an example
> > I just made this internationalizable a week or two ago; your translation
> > will be the first.
