website translation experiments

[Dirk Hohndel]

This may not go anywhere - but it might, so please bear with me...

I have spent a few hours (mostly because I suck at Perl) and wrote a couple of scripts to try to connect our current git based translation system for the website with Transifex.

There's a new resource on Transifex that is called "about" and that contains the strings of our landing page. For the website we currently have translations to de_DE fr_FR es_ES it_IT nl_NL pl_PL ru_RU pt_PT fi_FI so these are the ones that have been populated. The closer the translations were to the English version, the better these imports will be. While eventually we can consider other translations, right now I'm not asking for people to add more translations!

If you would like to help me figure out if this is feasible and you speak (doesn't matter at this point how fluently) one of these languages, you could help me by logging into Transifex and cleaning up the translations of that "about" resource. The biggest issue likely will be "translations" that are on the wrong source string. Because of the way I extract these preliminary translations from the existing translations, if the "grouping" of the HTML in the translation doesn't match the grouping in English, things will go poorly. I had to break up a couple of longer paragraphs in German to match the paragraph breaks in English, for example.
Then tomorrow I'll try to pull these translations again and see if I can feed them into git and push them from there into WordPress in order for them to show up on our website.

This initial process is labor intensive on my part, that's why I did it for only one of the pages. But once I have this part taken care of (= one time investment of my time) the continued maintenance should be rather scriptable / low touch. Which is REALLY the part that I want to test. Because if this does work then we can do the website translations on Transifex as well, we can translate announcements before they go out and overall create a much better experience for our users.

Admittedly, the initial process is also a bit annoying for the translators, but having done it for German it's actually not too bad because it is pretty obvious what is happening (since you have the source strings right there on the web site).
The main reason for this convoluted process is that I want to preserve as much of the existing translation work as possible. It would have been MUCH easier for me to throw away all the existing translations and start from scratch, but that seemed entirely unreasonable towards the translators and all the efforts they have already put into translating the website.

Anyway, if all this works out, maybe the AMAZING group of translators that we already have for the application can help us keep the website better translated as well.

If you have the time and want to help, respond here, tell us when you are happy with the translation (and what language) and I'll take the experiment from there. If you don't have a Transifex account, signing up is easy and then ask to join the subsurface team - I or one of the language coordinators will add you (there is a manual approval step involved - sorry).

For now, none of the automation is hooked up, so none of these translations will show up on the website unless I process them here (just to avoid unmet expectations) :-)

Thanks as always!

/D

[Dirk Hohndel]

> On Jul 15, 2018, at 5:31 PM, Dirk Hohndel <***@hohndel.org> wrote:
>
>
> This may not go anywhere - but it might, so please bear with me...
>
> I have spent a few hours (mostly because I suck at Perl) and wrote a couple of scripts to try to connect our current git based translation system for the website with Transifex.
>
> There's a new resource on Transifex that is called "about" and that contains the strings of our landing page. For the website we currently have translations to de_DE fr_FR es_ES it_IT nl_NL pl_PL ru_RU pt_PT fi_FI so these are the ones that have been populated. The closer the translations were to the English version, the better these imports will be. While eventually we can consider other translations, right now I'm not asking for people to add more translations!
>
> If you would like to help me figure out if this is feasible and you speak (doesn't matter at this point how fluently) one of these languages, you could help me by logging into Transifex and cleaning up the translations of that "about" resource. The biggest issue likely will be "translations" that are on the wrong source string. Because of the way I extract these preliminary translations from the existing translations, if the "grouping" of the HTML in the translation doesn't match the grouping in English, things will go poorly. I had to break up a couple of longer paragraphs in German to match the paragraph breaks in English, for example.
> Then tomorrow I'll try to pull these translations again and see if I can feed them into git and push them from there into WordPress in order for them to show up on our website.

For example, I don't speak Finnish... but it's quite obvious that some of the strings were missing and that therefore the translations are not matching the source strings. For example "Hieman historian:" apparently is Finnish for string #17, "A bit of background", but it shows up as the translation of string #9...

/D

[Miika Turkia]

On Mon, Jul 16, 2018 at 3:39 AM, Dirk Hohndel <***@hohndel.org> wrote:

>
> On Jul 15, 2018, at 5:31 PM, Dirk Hohndel <***@hohndel.org> wrote:
>
>
> This may not go anywhere - but it might, so please bear with me...
>
> I have spent a few hours (mostly because I suck at Perl) and wrote a
> couple of scripts to try to connect our current git based translation
> system for the website with Transifex.
>
> There's a new resource on Transifex that is called "about" and that
> contains the strings of our landing page. For the website we currently have
> translations to de_DE fr_FR es_ES it_IT nl_NL pl_PL ru_RU pt_PT fi_FI so
> these are the ones that have been populated. The closer the translations
> were to the English version, the better these imports will be. While
> eventually we can consider other translations, right now I'm not asking for
> people to add more translations!
>
> If you would like to help me figure out if this is feasible and you speak
> (doesn't matter at this point how fluently) one of these languages, you
> could help me by logging into Transifex and cleaning up the translations of
> that "about" resource. The biggest issue likely will be "translations" that
> are on the wrong source string. Because of the way I extract these
> preliminary translations from the existing translations, if the "grouping"
> of the HTML in the translation doesn't match the grouping in English,
> things will go poorly. I had to break up a couple of longer paragraphs in
> German to match the paragraph breaks in English, for example.
> Then tomorrow I'll try to pull these translations again and see if I can
> feed them into git and push them from there into WordPress in order for
> them to show up on our website.
>
>
> For example, I don't speak Finnish... but it's quite obvious that some of
> the strings were missing and that therefore the translations are not
> matching the source strings. For example "Hieman historian:" apparently
> is Finnish for string #17, "A bit of background", but it shows up as the
> translation of string #9...
>
>
FI is translated. The biggest challenge was to add the formatting commands
within the string without copying the original English text first. But it
ended up being simple enough, just typing the <strong></strong> tags and
once the string is accepted the tag is marked with the running number and
grey background...

miika

[Dirk Hohndel]

> On Jul 15, 2018, at 9:31 PM, Miika Turkia <***@gmail.com> wrote:
>
> FI is translated. The biggest challenge was to add the formatting commands within the string without copying the original English text first. But it ended up being simple enough, just typing the <strong></strong> tags and once the string is accepted the tag is marked with the running number and grey background...

So apparently you should be able to copy them using Ctrl-Alt-Number - I tried this on my Mac and it worked fine...
Thanks for doing the translation - and thanks to Salvador for verifying Spanish. I hope a few more people can take a look while I'm asleep and then I'll try to pull the finished translation over to WordPress tomorrow :-)

/D

[Guillaume Gardet]

Hi,


Le 16/07/2018 à 07:47, Dirk Hohndel a écrit :
>> On Jul 15, 2018, at 9:31 PM, Miika Turkia <***@gmail.com> wrote:
>>
>> FI is translated. The biggest challenge was to add the formatting commands within the string without copying the original English text first. But it ended up being simple enough, just typing the <strong></strong> tags and once the string is accepted the tag is marked with the running number and grey background...
> So apparently you should be able to copy them using Ctrl-Alt-Number - I tried this on my Mac and it worked fine...
> Thanks for doing the translation - and thanks to Salvador for verifying Spanish. I hope a few more people can take a look while I'm asleep and then I'll try to pull the finished translation over to WordPress tomorrow :-)

Done for French.

Guillaume


> /D
>
> _______________________________________________
> subsurface mailing list
> ***@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

[Salvador Cuñat]

Hi.

El lun., 16 jul. 2018 2:31, Dirk Hohndel <***@hohndel.org> escribió:

>
>
> If you would like to help me figure out if this is feasible and you speak
> (doesn't matter at this point how fluently) one of these languages, you
> could help me by logging into Transifex and cleaning up the translations of
> that "about" resource. The biggest issue likely will be "translations" that
> are on the wrong source string. Because of the way I extract these
> preliminary translations from the existing translations, if the "grouping"
> of the HTML in the translation doesn't match the grouping in English,
> things will go poorly. I had to break up a couple of longer paragraphs in
> German to match the paragraph breaks in English, for example.
>

Nothing to do in Spanish. The import has gone 100% fine. All 20 strings
has been correctly grouped.

Best regards.

Salva.

[Pedro Neves]

Dirk:

I've completed the translation for pt_PT. I had to adjust a few strings,
but it was no big deal.

Hope this helps...

Cheers:

Pedro

[Peter Zaal]

Dutch done, almost all strings were already correctly transferred.
Btw for the formatting placeholders, ctrl-alt-number didn't work for me, no
clue why not, but you can also simply click on the number in the original
text en it is then copied to the translated text.
Another question, should and can we use html entities for special
characters, e.g. if I want to use an é in the text, can I just put an é, or
should we use &eacute; or would this be encoded once more on the site (and
literally show "&eacute;") ? And I know this is just an experiment for now,
but maybe it would be nice to have all the webpage resources within a
'Subsurface website' parent if possible. The about resource is now on the
same level as subsurface4 and others, but i would be a bit cluttered if all
the webpages would come here.

Peter

On Mon, Jul 16, 2018 at 9:26 AM Pedro Neves <***@gmail.com> wrote:

> Dirk:
>
> I've completed the translation for pt_PT. I had to adjust a few strings,
> but it was no big deal.
>
> Hope this helps...
>
> Cheers:
>
> Pedro
> _______________________________________________
> subsurface mailing list
> ***@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>


--
Met vriendelijke groeten,

Peter Zaal

[Dirk Hohndel]

> On Jul 16, 2018, at 3:07 AM, Peter Zaal <***@gmail.com> wrote:
>
> Dutch done, almost all strings were already correctly transferred.

Cool

> Btw for the formatting placeholders, ctrl-alt-number didn't work for me, no clue why not, but you can also simply click on the number in the original text en it is then copied to the translated text.

Thanks for that tip, we should collect those as hints for the translators.

> Another question, should and can we use html entities for special characters, e.g. if I want to use an é in the text, can I just put an é, or should we use &eacute; or would this be encoded once more on the site (and literally show "&eacute;") ?

That's exactly the kind of thing I want to find out. Feel free to try different things - I'll transfer the result over to the website this morning and then we'll see what works and what doesn't.

> And I know this is just an experiment for now, but maybe it would be nice to have all the webpage resources within a 'Subsurface website' parent if possible. The about resource is now on the same level as subsurface4 and others, but i would be a bit cluttered if all the webpages would come here.

I had problems with Transifex over the weekend. I created a new website project but wasn't able to add resources to it. In the end the only thing I could make work was to put it right where it is now. I agree that this would end up being very cluttered.

Thanks for everyone's help!

Now let's see how this went :-)

/D

[Dirk Hohndel]

As always, nothing is as easy as it should be :-)

First my database server crashed - I believe this was unrelated, but am not 100% sure.
Then 2/3 of the updates worked, but three didn't - also not sure why, the error message is truly enlightening: "Received an error object"... gee, thanks for letting me know.

But it was easy enough to create another commit that caused an update of those three and now the website has been updated.

> On Jul 16, 2018, at 7:57 AM, Dirk Hohndel <***@hohndel.org> wrote:
>
>> Another question, should and can we use html entities for special characters, e.g. if I want to use an é in the text, can I just put an é, or should we use &eacute; or would this be encoded once more on the site (and literally show "&eacute;") ?
>
> That's exactly the kind of thing I want to find out. Feel free to try different things - I'll transfer the result over to the website this morning and then we'll see what works and what doesn't.

I took a quick look and while this ends up looking strange in the git repo, it seems it renders fine on WordPress. Can you take a look and see if this is what you wanted it to be?

Either way, while not everything worked the way I wanted, this first attempt actually is really promising. Some issues to figure out for sure, but by and large this seems to work.

I will now add a post (an announcement) and try the same things again. Stay tuned :-)

/D

[Miika Turkia]

> On 16 Jul 2018, at 19.32, Dirk Hohndel <***@hohndel.org> wrote:
>
>
> As always, nothing is as easy as it should be :-)
>
> First my database server crashed - I believe this was unrelated, but am not 100% sure.
> Then 2/3 of the updates worked, but three didn't - also not sure why, the error message is truly enlightening: "Received an error object"... gee, thanks for letting me know.
>
> But it was easy enough to create another commit that caused an update of those three and now the website has been updated.
>
>>> On Jul 16, 2018, at 7:57 AM, Dirk Hohndel <***@hohndel.org> wrote:
>>>
>>> Another question, should and can we use html entities for special characters, e.g. if I want to use an é in the text, can I just put an é, or should we use &eacute; or would this be encoded once more on the site (and literally show "&eacute;") ?
>>
>> That's exactly the kind of thing I want to find out. Feel free to try different things - I'll transfer the result over to the website this morning and then we'll see what works and what doesn't.
>
> I took a quick look and while this ends up looking strange in the git repo, it seems it renders fine on WordPress. Can you take a look and see if this is what you wanted it to be?

I only see english and dutch when looking with mobile phone.

miika

[Dirk Hohndel]

> On Jul 16, 2018, at 9:45 AM, Miika Turkia <***@gmail.com> wrote:
>>
>> I took a quick look and while this ends up looking strange in the git repo, it seems it renders fine on WordPress. Can you take a look and see if this is what you wanted it to be?
>
> I only see english and dutch when looking with mobile phone.

At the bottom of the homepage, I see this:


So all languages seem to be there. You can see by the text that I'm looking at the home page in Portuguese right now).
If I click on Suomi this turns into

[Miika Turkia]

> On 16 Jul 2018, at 19.48, Dirk Hohndel <***@hohndel.org> wrote:
>
>
>>> On Jul 16, 2018, at 9:45 AM, Miika Turkia <***@gmail.com> wrote:
>>>
>>> I took a quick look and while this ends up looking strange in the git repo, it seems it renders fine on WordPress. Can you take a look and see if this is what you wanted it to be?
>>
>> I only see english and dutch when looking with mobile phone.
>
> At the bottom of the homepage, I see this:
>
> <Screen Shot 2018-07-16 at 9.46.55 AM.png>
>
> So all languages seem to be there. You can see by the text that I'm looking at the home page in Portuguese right now).
> If I click on Suomi this turns into
>
> <Screen Shot 2018-07-16 at 9.48.41 AM.png>

here is what I have on mobile

[Dirk Hohndel]

That's Deutsch as in German, not Dutch :-)

Common mistake to make, a lot of things that are called "Dutch" in the US are actually German...

But I'm confused by that. I wonder why this isn't working. I can reproduce it here, and clicking on Deutsch has no effect. If you scroll all the way down you see our language selection and that works...

On July 16, 2018 9:58:00 AM PDT, Miika Turkia <***@gmail.com> wrote:
>
>
>> On 16 Jul 2018, at 19.48, Dirk Hohndel <***@hohndel.org> wrote:
>>
>>
>>>> On Jul 16, 2018, at 9:45 AM, Miika Turkia <***@gmail.com>
>wrote:
>>>>
>>>> I took a quick look and while this ends up looking strange in the
>git repo, it seems it renders fine on WordPress. Can you take a look
>and see if this is what you wanted it to be?
>>>
>>> I only see english and dutch when looking with mobile phone.
>>
>> At the bottom of the homepage, I see this:
>>
>> <Screen Shot 2018-07-16 at 9.46.55 AM.png>
>>
>> So all languages seem to be there. You can see by the text that I'm
>looking at the home page in Portuguese right now).
>> If I click on Suomi this turns into
>>
>> <Screen Shot 2018-07-16 at 9.48.41 AM.png>
>
>here is what I have on mobile

--
from my phone.

[Peter Zaal]

I'm confused, I thought that meant that the website was updated with the
about resource? This is not the case for the dutch strings, because I made
a very small change (I added a colon after the translation for the 'A bit
of background:'), but that is not visible on the website?

Peter

On Mon, Jul 16, 2018 at 6:45 PM Miika Turkia <***@gmail.com> wrote:

>
>
> On 16 Jul 2018, at 19.32, Dirk Hohndel <***@hohndel.org> wrote:
>
>
> As always, nothing is as easy as it should be :-)
>
> First my database server crashed - I believe this was unrelated, but am
> not 100% sure.
> Then 2/3 of the updates worked, but three didn't - also not sure why, the
> error message is truly enlightening: "Received an error object"... gee,
> thanks for letting me know.
>
> But it was easy enough to create another commit that caused an update of
> those three and now the website has been updated.
>
> On Jul 16, 2018, at 7:57 AM, Dirk Hohndel <***@hohndel.org> wrote:
>
> Another question, should and can we use html entities for special
> characters, e.g. if I want to use an é in the text, can I just put an é, or
> should we use &eacute; or would this be encoded once more on the site
> (and literally show "&eacute;") ?
>
>
> That's exactly the kind of thing I want to find out. Feel free to try
> different things - I'll transfer the result over to the website this
> morning and then we'll see what works and what doesn't.
>
>
> I took a quick look and while this ends up looking strange in the git
> repo, it seems it renders fine on WordPress. Can you take a look and see if
> this is what you wanted it to be?
>
>
> I only see english and dutch when looking with mobile phone.
>
> miika
>


--
Met vriendelijke groeten,

Peter Zaal

[Dirk Hohndel]

> On Jul 16, 2018, at 11:32 AM, Peter Zaal <***@gmail.com> wrote:
>
> I'm confused, I thought that meant that the website was updated with the about resource? This is not the case for the dutch strings, because I made a very small change (I added a colon after the translation for the 'A bit of background:'), but that is not visible on the website?

Yes, it should be. So let's see:

Here's what I see:

Enige historie en achtergrond
In het najaar van 2011, gaf een gedwongen pauze in de kernel ontwikkeling Linux bedenker Linus Torvalds de gelegenheid een nieuw project te starten, om zijn frustratie over het gebrek aan een fatsoenlijk duiklog programma onder Linux op te pakken.
Linus werkte samen met een team van ontwikkelaars, en Subsurface is het resultaat. Het biedt nu ondersteuning voor Linux, Windows en MacOS en maakt het mogelijk gegevens te importeren uit vele duikcomputers en een aantal bestaande duikprogramma’s. Het biedt een snelle en gemakkelijke manier om de belangrijkste informatie die door een moderne duikcomputer vastgelegd worden te laten zien en bewerken. In het najaar van 2012 nam Dirk Hohndel de rol als Subsurface verantwoordelijke over.
Licentie: GPLv2


Which seems to match what I see on Transifex.

What do you see? Am I missing what's different?

/D

[Peter Zaal]

Ok that's weird. It's the header text, after which I added a colon. This
translation:
https://www.transifex.com/subsurface/subsurface/translate/#nl_NL/about/148894965
:

[image: image.png]
Am I in the wrong resource or what am I missing?


On Mon, Jul 16, 2018 at 9:52 PM Dirk Hohndel <***@hohndel.org> wrote:

>
> On Jul 16, 2018, at 11:32 AM, Peter Zaal <***@gmail.com> wrote:
>
> I'm confused, I thought that meant that the website was updated with the
> about resource? This is not the case for the dutch strings, because I made
> a very small change (I added a colon after the translation for the 'A bit
> of background:'), but that is not visible on the website?
>
>
> Yes, it should be. So let's see:
>
> Here's what I see:
>
> Enige historie en achtergrond
> In het najaar van 2011, gaf een gedwongen pauze in de kernel ontwikkeling
> Linux bedenker Linus Torvalds de gelegenheid een nieuw project te starten,
> om zijn frustratie over het gebrek aan een fatsoenlijk duiklog programma
> onder Linux op te pakken.
> Linus werkte samen met een team van ontwikkelaars, en Subsurface is het
> resultaat. Het biedt nu ondersteuning voor Linux, Windows en MacOS en maakt
> het mogelijk gegevens te importeren uit vele duikcomputers en een aantal
> bestaande duikprogramma’s. Het biedt een snelle en gemakkelijke manier om
> de belangrijkste informatie die door een moderne duikcomputer vastgelegd
> worden te laten zien en bewerken. In het najaar van 2012 nam Dirk Hohndel
> de rol als Subsurface verantwoordelijke over.
> Licentie: GPLv2
>
>
> Which seems to match what I see on Transifex.
>
> What do you see? Am I missing what's different?
>
> /D
>


--
Met vriendelijke groeten,

Peter Zaal

[Dirk Hohndel]

Thanks, I misunderstood what was supposed to be changed.

This was correctly transferred from Transifex to my intermediate format.
From there it went correctly into GitHub: https://github.com/Subsurface-divelog/Subsurface-website/blob/master/_pages/about.nl#L93
And the upload from there to WordPress showed no error. Yet it didn't get updated. That's even more frustrating as that makes it harder for me to know when to retry...

So I made a whitespace change and pushed it again.
This time I got a "could not update post in the database" error.

And digging through the logs it turns out that it is indeed the encoding of the "één" that's the problem. Wordpress rejects what I am sending to it. So now I need to figure out how to work around that...

THANKS for the eagle eyes and for making sure I catch this. That would have been rather embarrassing.

/D

> On Jul 16, 2018, at 1:00 PM, Peter Zaal <***@gmail.com> wrote:
>
> Ok that's weird. It's the header text, after which I added a colon. This translation: https://www.transifex.com/subsurface/subsurface/translate/#nl_NL/about/148894965 <https://www.transifex.com/subsurface/subsurface/translate/#nl_NL/about/148894965> :
>
>
> Am I in the wrong resource or what am I missing?
>
>
> On Mon, Jul 16, 2018 at 9:52 PM Dirk Hohndel <***@hohndel.org <mailto:***@hohndel.org>> wrote:
>
>> On Jul 16, 2018, at 11:32 AM, Peter Zaal <***@gmail.com <mailto:***@gmail.com>> wrote:
>>
>> I'm confused, I thought that meant that the website was updated with the about resource? This is not the case for the dutch strings, because I made a very small change (I added a colon after the translation for the 'A bit of background:'), but that is not visible on the website?
>
> Yes, it should be. So let's see:
>
> Here's what I see:
>
> Enige historie en achtergrond
> In het najaar van 2011, gaf een gedwongen pauze in de kernel ontwikkeling Linux bedenker Linus Torvalds de gelegenheid een nieuw project te starten, om zijn frustratie over het gebrek aan een fatsoenlijk duiklog programma onder Linux op te pakken.
> Linus werkte samen met een team van ontwikkelaars, en Subsurface is het resultaat. Het biedt nu ondersteuning voor Linux, Windows en MacOS en maakt het mogelijk gegevens te importeren uit vele duikcomputers en een aantal bestaande duikprogramma’s. Het biedt een snelle en gemakkelijke manier om de belangrijkste informatie die door een moderne duikcomputer vastgelegd worden te laten zien en bewerken. In het najaar van 2012 nam Dirk Hohndel de rol als Subsurface verantwoordelijke over.
> Licentie: GPLv2
>
>
> Which seems to match what I see on Transifex.
>
> What do you see? Am I missing what's different?
>
> /D
>
>
> --
> Met vriendelijke groeten,
>
> Peter Zaal

[Dirk Hohndel]

> On Jul 16, 2018, at 1:15 PM, Dirk Hohndel <***@hohndel.org> wrote:
>
> Thanks, I misunderstood what was supposed to be changed.
>
> This was correctly transferred from Transifex to my intermediate format.
> From there it went correctly into GitHub: https://github.com/Subsurface-divelog/Subsurface-website/blob/master/_pages/about.nl#L93 <https://github.com/Subsurface-divelog/Subsurface-website/blob/master/_pages/about.nl#L93>
> And the upload from there to WordPress showed no error. Yet it didn't get updated. That's even more frustrating as that makes it harder for me to know when to retry...
>
> So I made a whitespace change and pushed it again.
> This time I got a "could not update post in the database" error.
>
> And digging through the logs it turns out that it is indeed the encoding of the "één" that's the problem. Wordpress rejects what I am sending to it. So now I need to figure out how to work around that...
>
> THANKS for the eagle eyes and for making sure I catch this. That would have been rather embarrassing.

This is indeed very strange. Files from Transifex are supposed to arrive in UTF-8. Nothing in my processing should have changed things to ISO8859-1 - yet about.nl is the one file that was incorrectly encoded.
Right now I have no explanation. Add this to the list of things that I'm worried about, I guess.

Manually converted and re-uploaded, all good now. Please check the website if anything else got damaged - especially look at the non-ASCII letters in the text, please.

/D

[Peter Zaal]

Regarding the diacritic characters, I noticed that when you use the literal diacritics in the translated text, this does not show correctly on the website.

E.g. in the translated text ‘BÃŒhlmann’ shows as ‘BÌhlmann’ on the website, or ‘geïntegreerd’ in Transifex shows as ‘geïntegreerd’ on the website.

Using encoded text in Transifex shows correctly on the website (although not encoded there), e.g. ‘&eacute;&eacute;n’ shows as ‘één’. ‘&amp;’ shows as ‘&’.

So I guess this means we should use html encoding for the ‘special’ characters.



Peter







On Jul 16, 2018, at 1:15 PM, Dirk Hohndel <***@hohndel.org <mailto:***@hohndel.org> > wrote:



Thanks, I misunderstood what was supposed to be changed.



This was correctly transferred from Transifex to my intermediate format.

From there it went correctly into GitHub: https://github.com/Subsurface-divelog/Subsurface-website/blob/master/_pages/about.nl#L93

And the upload from there to WordPress showed no error. Yet it didn't get updated. That's even more frustrating as that makes it harder for me to know when to retry...



So I made a whitespace change and pushed it again.

This time I got a "could not update post in the database" error.



And digging through the logs it turns out that it is indeed the encoding of the "één" that's the problem. Wordpress rejects what I am sending to it. So now I need to figure out how to work around that...



THANKS for the eagle eyes and for making sure I catch this. That would have been rather embarrassing.



This is indeed very strange. Files from Transifex are supposed to arrive in UTF-8. Nothing in my processing should have changed things to ISO8859-1 - yet about.nl <http://about.nl> is the one file that was incorrectly encoded.

Right now I have no explanation. Add this to the list of things that I'm worried about, I guess.



Manually converted and re-uploaded, all good now. Please check the website if anything else got damaged - especially look at the non-ASCII letters in the text, please.



/D

[Miika Turkia]

On Tue, Jul 17, 2018 at 8:37 AM, Peter Zaal <***@gmail.com> wrote:

> Regarding the diacritic characters, I noticed that when you use the
> literal diacritics in the translated text, this does not show correctly on
> the website.
>
> E.g. in the translated text ‘BÃŒhlmann’ shows as ‘BÌhlmann’ on the
> website, or ‘geïntegreerd’ in Transifex shows as ‘geïntegreerd’ on the
> website.
>
> Using encoded text in Transifex shows correctly on the website (although
> not encoded there), e.g. ‘&eacute;&eacute;n’ shows as ‘één’. ‘&amp;’ shows
> as ‘&’.
>
> So I guess this means we should use html encoding for the ‘special’
> characters.
>

Seems to be working at least on Finnish and German, so this is probably a
text encoding issue in the tooling as Dirk mentions.

miika

> On Jul 16, 2018, at 1:15 PM, Dirk Hohndel <***@hohndel.org> wrote:
>
>
>
> Thanks, I misunderstood what was supposed to be changed.
>
>
>
> This was correctly transferred from Transifex to my intermediate format.
>
> From there it went correctly into GitHub: https://github.com/
> Subsurface-divelog/Subsurface-website/blob/master/_pages/about.nl#L93
>
> And the upload from there to WordPress showed no error. Yet it didn't get
> updated. That's even more frustrating as that makes it harder for me to
> know when to retry...
>
>
>
> So I made a whitespace change and pushed it again.
>
> This time I got a "could not update post in the database" error.
>
>
>
> And digging through the logs it turns out that it is indeed the encoding
> of the "één" that's the problem. Wordpress rejects what I am sending to it.
> So now I need to figure out how to work around that...
>
>
>
> THANKS for the eagle eyes and for making sure I catch this. That would
> have been rather embarrassing.
>
>
>
> This is indeed very strange. Files from Transifex are supposed to arrive
> in UTF-8. Nothing in my processing should have changed things to ISO8859-1
> - yet about.nl is the one file that was incorrectly encoded.
>
> Right now I have no explanation. Add this to the list of things that I'm
> worried about, I guess.
>
>
>
> Manually converted and re-uploaded, all good now. Please check the website
> if anything else got damaged - especially look at the non-ASCII letters in
> the text, please.
>
>
>
> /D
>
>
>
> _______________________________________________
> subsurface mailing list
> ***@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
>

[Davide DB]

I'm a bit late to the party and i'm having some difficulties to
understand how to proceed.
I've reviewed and modified most of the Italian strings in the about
file of the subsurface project.

Should I continue with the "announcing-subsurface-4-8" and
"announcing-subsurface-4-8-1" files?

I see that there is another project website but it seems I cannot
partecipate. I'm part of the team but I cannot request Italian
language and other problems... so before I proceed better aim at the
right target :)

Thanks

[Miika Turkia]

On Tue, Jul 17, 2018 at 12:53 PM, Davide DB <***@gmail.com> wrote:

> I'm a bit late to the party and i'm having some difficulties to
> understand how to proceed.
> I've reviewed and modified most of the Italian strings in the about
> file of the subsurface project.
>
> Should I continue with the "announcing-subsurface-4-8" and
> "announcing-subsurface-4-8-1" files?
>

Currently these are the ones we are testing the translation with.


> I see that there is another project website but it seems I cannot
> partecipate. I'm part of the team but I cannot request Italian
> language and other problems... so before I proceed better aim at the
> right target :)
>

If I have understood correctly, Dirk attempted to create another project
for the web site, but failed to add resources there. So that is why we are
currently prototyping within the Subsurface project.

miika

[Peter Zaal]

On Tue, Jul 17, 2018 at 12:18 PM Miika Turkia <***@gmail.com>
wrote:

> On Tue, Jul 17, 2018 at 12:53 PM, Davide DB <***@gmail.com> wrote:
>
>> I'm a bit late to the party and i'm having some difficulties to
>> understand how to proceed.
>> I've reviewed and modified most of the Italian strings in the about
>> file of the subsurface project.
>>
>> Should I continue with the "announcing-subsurface-4-8" and
>> "announcing-subsurface-4-8-1" files?
>>
>
> Currently these are the ones we are testing the translation with.
>
>
>> I see that there is another project website but it seems I cannot
>> partecipate. I'm part of the team but I cannot request Italian
>> language and other problems... so before I proceed better aim at the
>> right target :)
>>
>
> If I have understood correctly, Dirk attempted to create another project
> for the web site, but failed to add resources there. So that is why we are
> currently prototyping within the Subsurface project.
>

Yesterday at some point that seemed to work, because there was actually a
resource under de website project (also announcing-subsurface-4-8-1).
I already started translating some strings in that resource, but noticed
that the resource was gone this morning, and two new announcing resources
where added under subsurface project.

[Pedro Neves]

On 17-07-2018 11:35, Peter Zaal wrote:
>
>
> Yesterday at some point that seemed to work, because there was
> actually a resource under de website project(also
> announcing-subsurface-4-8-1).
> I already started translating some strings in that resource, but
> noticed that the resource was gone this morning, and two new
> announcing resources where added under subsurface project.

Ahh, OK. So I wasn't dreaming! I knew I had translated a file
yesterday... ;-)

Nevertheless, I've finished the pt_PT translations...

Cheers:

Pedro

[Pedro Neves]

Does anyone know how we can translate the headers that are shown
together with the images on the main page (e.g.: "Multiplatform", "Log
all your dives", etc.)? The captions are on the strings on the "About"
page, mas the header are missing...

Thanks in advance:

Pedro

[Dirk Hohndel]

> On Jul 17, 2018, at 7:26 AM, Pedro Neves <***@gmail.com> wrote:
>
> Does anyone know how we can translate the headers that are shown together with the images on the main page (e.g.: "Multiplatform", "Log all your dives", etc.)? The captions are on the strings on the "About" page, mas the header are missing...

Because of the way we extract the strings (and the way the "theme" for our website works) they aren't extracted for translation.
I realize this is annoying, but if you just send me the five strings I can manually fix this up.

Thanks for catching this

D

[Pedro Neves]

On 17-07-2018 16:19, Dirk Hohndel wrote:
>
> I realize this is annoying, but if you just send me the five strings I
> can manually fix this up.

Hi Dirk:

It's not annoying. It's just for the sake of completion ;-)  Here they
go, for pt_PT:

Multiplatform: Multi-plataforma

Log all your dives: Registe todos os seus mergulhos

Dive planner: Planeamento de mergulhos

Cloud storage: Armazenamento remoto

No translation needed for Subsurface-mobile...

Cheers:

Pedro

[Miika Turkia]

On Tue, Jul 17, 2018 at 5:26 PM, Pedro Neves <***@gmail.com> wrote:

> Does anyone know how we can translate the headers that are shown together
> with the images on the main page (e.g.: "Multiplatform", "Log all your
> dives", etc.)? The captions are on the strings on the "About" page, mas the
> header are missing...
>

This is not yet possible. Dirk will have to do some more manual work to get
it all ready for translation.

Dirk, there seems to be a bug in the announcement of 4.8.1. The following
sentence has wrong version number
---8<---
Some of the changes in Subsurface 4.8:
---8<---

miika

[Dirk Hohndel]

> On Jul 17, 2018, at 8:21 AM, Miika Turkia <***@gmail.com> wrote:
>
> On Tue, Jul 17, 2018 at 5:26 PM, Pedro Neves <***@gmail.com <mailto:***@gmail.com>> wrote:
> Does anyone know how we can translate the headers that are shown together with the images on the main page (e.g.: "Multiplatform", "Log all your dives", etc.)? The captions are on the strings on the "About" page, mas the header are missing...
>
> This is not yet possible. Dirk will have to do some more manual work to get it all ready for translation.
>
> Dirk, there seems to be a bug in the announcement of 4.8.1. The following sentence has wrong version number
> ---8<---
> Some of the changes in Subsurface 4.8:
> ---8<---

So true.

Things like that are easy to fix with a PR to subsurface-website :-)

But I already fixed it. Thanks Miika.

And Transifex Support has responded to my question about the new project that will include all of the text for the website.
So please don't be surprised if the resources move around suddenly.

I will try REALLY HARD not to lose any translations in the process :-)

/D

[Miika Turkia]

On Wed, Jul 18, 2018 at 12:44 AM, Dirk Hohndel <***@hohndel.org> wrote:

>
> On Jul 17, 2018, at 8:21 AM, Miika Turkia <***@gmail.com> wrote:
>
> On Tue, Jul 17, 2018 at 5:26 PM, Pedro Neves <***@gmail.com> wrote:
>
>> Does anyone know how we can translate the headers that are shown together
>> with the images on the main page (e.g.: "Multiplatform", "Log all your
>> dives", etc.)? The captions are on the strings on the "About" page, mas the
>> header are missing...
>>
>
> This is not yet possible. Dirk will have to do some more manual work to
> get it all ready for translation.
>
> Dirk, there seems to be a bug in the announcement of 4.8.1. The following
> sentence has wrong version number
> ---8<---
> Some of the changes in Subsurface 4.8:
> ---8<---
>
>
> So true.
>
> Things like that are easy to fix with a PR to subsurface-website :-)
>
> But I already fixed it. Thanks Miika.
>
> And Transifex Support has responded to my question about the new project
> that will include all of the text for the website.
> So please don't be surprised if the resources move around suddenly.
>

i see that the titles are now available in Transifex under the website
project. Subsurface project still contains the older version of the about
page. I am assuming we are moving our efforts under the website part.


> I will try REALLY HARD not to lose any translations in the process :-)
>

One problem that would be nice to be changed is that currently untranslated
pages end up with English texts in the foreign language resulting in
transifex claiming all strings to be translated. Would be great if these
were empty in Transifex side.

I am also not certain how well this is going to work when pages get
updated. I.e. previously I have commented that it should be easy to see
what is falling out of sync on Transifex, but currently I am unsure if this
is true or not. But we will know more when the prototyping continues.

miika

[Dirk Hohndel]

On July 17, 2018 8:38:10 PM PDT, Miika Turkia <***@gmail.com> wrote:
>
>>> Does anyone know how we can translate the headers that are shown
>together
>>> with the images on the main page (e.g.: "Multiplatform", "Log all
>your
>>> dives", etc.)? The captions are on the strings on the "About" page,
>mas the
>>> header are missing...


These are now available, but I broke something else... As I said, these are all experiments...

>> And Transifex Support has responded to my question about the new
>project
>> that will include all of the text for the website.
>> So please don't be surprised if the resources move around suddenly.
>>
>
>i see that the titles are now available in Transifex under the website
>project. Subsurface project still contains the older version of the
>about
>page. I am assuming we are moving our efforts under the website part.

Yes please. I wanted to make sure I didn't lose anything before deleting them under subsurface

>> I will try REALLY HARD not to lose any translations in the process
>:-)
>>
>
>One problem that would be nice to be changed is that currently
>untranslated
>pages end up with English texts in the foreign language resulting in
>transifex claiming all strings to be translated. Would be great if
>these
>were empty in Transifex side.

That seems impossible given the way I set things up. I'm still trying to figure out why.

Right now I get errors when I try to create the translations "empty"

>I am also not certain how well this is going to work when pages get
>updated. I.e. previously I have commented that it should be easy to see
>what is falling out of sync on Transifex, but currently I am unsure if
>this
>is true or not. But we will know more when the prototyping continues.

That's why we are doing it :-)

/D

[Dirk Hohndel]

>> i see that the titles are now available in Transifex under the website
>> project. Subsurface project still contains the older version of the
>> about
>> page. I am assuming we are moving our efforts under the website part.
>
> Yes please. I wanted to make sure I didn't lose anything before deleting them under subsurface

I just removed those.

>>> I will try REALLY HARD not to lose any translations in the process
>> :-)
>>>
>>
>> One problem that would be nice to be changed is that currently
>> untranslated
>> pages end up with English texts in the foreign language resulting in
>> transifex claiming all strings to be translated. Would be great if
>> these
>> were empty in Transifex side.
>
> That seems impossible given the way I set things up. I'm still trying to figure out why.
>
> Right now I get errors when I try to create the translations "empty"

Haven't solved this one, yet, for documents where we already have translations. For new strings this seems to work already.

I think I have just pushed all the current translations of the 4.8.1 announcement to Wordpress.
Please verify that these are correct - let me know if things are missing, garbled, incorrectly encoded, etc.
I have stared at these for so long now that I'm not seeing clearly anymore - especially with all those that I can't read in the first place...

>> I am also not certain how well this is going to work when pages get
>> updated. I.e. previously I have commented that it should be easy to see
>> what is falling out of sync on Transifex, but currently I am unsure if
>> this
>> is true or not. But we will know more when the prototyping continues.
>
> That's why we are doing it :-)

I've played with this briefly and it's actually quite nice in Transifex - at least for the cases where we don't end up with English text as "translation".

/D

[Peter Zaal]

On Wed, Jul 18, 2018 at 8:28 AM Dirk Hohndel <***@hohndel.org> wrote:

>
> >> i see that the titles are now available in Transifex under the website
> >> project. Subsurface project still contains the older version of the
> >> about
> >> page. I am assuming we are moving our efforts under the website part.
> >
> > Yes please. I wanted to make sure I didn't lose anything before deleting
> them under subsurface
>
> I just removed those.
>

They are still there


> I think I have just pushed all the current translations of the 4.8.1
> announcement to Wordpress.
> Please verify that these are correct - let me know if things are missing,
> garbled, incorrectly encoded, etc.
> I have stared at these for so long now that I'm not seeing clearly anymore
> - especially with all those that I can't read in the first place...
>

The dutch (nl_NL) translations are not on the website...

Peter

[Peter Zaal]

On Wed, Jul 18, 2018 at 8:43 AM Peter Zaal <***@gmail.com> wrote:

>
> On Wed, Jul 18, 2018 at 8:28 AM Dirk Hohndel <***@hohndel.org> wrote:
>
>>
>> >> i see that the titles are now available in Transifex under the website
>> >> project. Subsurface project still contains the older version of the
>> >> about
>> >> page. I am assuming we are moving our efforts under the website part.
>> >
>> > Yes please. I wanted to make sure I didn't lose anything before
>> deleting them under subsurface
>>
>> I just removed those.
>>
>
> They are still there
>
>
>> I think I have just pushed all the current translations of the 4.8.1
>> announcement to Wordpress.
>> Please verify that these are correct - let me know if things are missing,
>> garbled, incorrectly encoded, etc.
>> I have stared at these for so long now that I'm not seeing clearly
>> anymore - especially with all those that I can't read in the first place...
>>
>
> The dutch (nl_NL) translations are not on the website...
>
>
Sorry, they are actually on the website, but the link from the dutch about
page is to the english annoucing page.

[Dirk Hohndel]

> On Jul 17, 2018, at 11:49 PM, Peter Zaal <***@gmail.com> wrote:
>
> On Wed, Jul 18, 2018 at 8:43 AM Peter Zaal <***@gmail.com <mailto:***@gmail.com>> wrote:
>
> On Wed, Jul 18, 2018 at 8:28 AM Dirk Hohndel <***@hohndel.org <mailto:***@hohndel.org>> wrote:
>
> >> i see that the titles are now available in Transifex under the website
> >> project. Subsurface project still contains the older version of the
> >> about
> >> page. I am assuming we are moving our efforts under the website part.
> >
> > Yes please. I wanted to make sure I didn't lose anything before deleting them under subsurface
>
> I just removed those.
>
> They are still there

Hrmpf. Fixed.


> I think I have just pushed all the current translations of the 4.8.1 announcement to Wordpress.
> Please verify that these are correct - let me know if things are missing, garbled, incorrectly encoded, etc.
> I have stared at these for so long now that I'm not seeing clearly anymore - especially with all those that I can't read in the first place...
>
> The dutch (nl_NL) translations are not on the website...
>
>
> Sorry, they are actually on the website, but the link from the dutch about page is to the english annoucing page.


Interesting. More things to fix...

/D

[Dirk Hohndel]

> On Jul 18, 2018, at 7:01 AM, Dirk Hohndel <***@hohndel.org> wrote:
>> The dutch (nl_NL) translations are not on the website...
>>
>> Sorry, they are actually on the website, but the link from the dutch about page is to the english annoucing page.
>
>
> Interesting. More things to fix...

In order to adjust this I ended up going into Raw Editor mode on Transifex (the 'gear' symbol in the top right corner and then Editor Preferences). Now you can edit the link.
I did this for the languages where it was missing.

/D

[Peter Zaal]

On Wed, Jul 18, 2018 at 7:38 PM Dirk Hohndel <***@hohndel.org> wrote:

>
> On Jul 18, 2018, at 7:01 AM, Dirk Hohndel <***@hohndel.org> wrote:
>
> The dutch (nl_NL) translations are not on the website...
>>
>
> Sorry, they are actually on the website, but the link from the dutch about
> page is to the english annoucing page.
>
>
> Interesting. More things to fix...
>
>
> In order to adjust this I ended up going into Raw Editor mode on Transifex
> (the 'gear' symbol in the top right corner and then Editor Preferences).
> Now you can edit the link.
> I did this for the languages where it was missing.
>
> /D
>

Ah nice, I didn't noticed that option before! At first I was under the
impression that somewhere in the process the links where automagically
updated to their localized url. But I found out that in GitHub the links
were already to the specific localized url, so we should do that in
Transifex as well.
There were some more links to pages that were not localized (e.g. links on
the annoucing pages to the User Form or Downloads page), so I updated these
as well.
Thanks, I really like where this is going!

Peter

[Dirk Hohndel]

> On Jul 18, 2018, at 11:23 AM, Peter Zaal <***@gmail.com> wrote:
>
> Ah nice, I didn't noticed that option before! At first I was under the impression that somewhere in the process the links where automagically updated to their localized url. But I found out that in GitHub the links were already to the specific localized url, so we should do that in Transifex as well.
> There were some more links to pages that were not localized (e.g. links on the annoucing pages to the User Form or Downloads page), so I updated these as well.
> Thanks, I really like where this is going!

One step forward, two steps back.

I'm having a very hard time not destroying the encoding of non-ASCII characters. And right now I have no idea why.
It all looks good when printed to stdout, and turns into garbage when printed to a file.

/D

[Dirk Hohndel]

This is a request for really quick and easy help from people who speak one of our website languages (Dutch,
Finnish, French, German, Italian, Polish, Portuguese, Russian, and Spanish)...

> On Jul 18, 2018, at 1:04 PM, Dirk Hohndel <***@hohndel.org> wrote:
>
> I'm having a very hard time not destroying the encoding of non-ASCII characters. And right now I have no idea why.
> It all looks good when printed to stdout, and turns into garbage when printed to a file.

I gave up on perl and rewrote the parser / transformation utility with C++/Qt :-)

I re-ran things against the three files currently on Transifex and as far as I can tell the results look good.
I'd appreciate if people could check them in the various translations and tell me if they can spot issues

https://subsurface-divelog.org/
https://subsurface-divelog.org/2018/07/announcing-subsurface-4-8-1/
https://subsurface-divelog.org/2018/06/announcing-subsurface-4-8/

If your browser is set up in a non-English language that we support, it should show the localized version
as you click on those links (does that still work? I haven't tested that in a while). And in any case, you can
just use the language-selector at the bottom of each page...

One thing that I noticed (and am fixing as we speak) is that in the round-trip through GitHub the announcement
posts are still losing their correct translated category. I thought I had that fixed, but apparently I was wrong.
This is a GitHub/WordPress integration bug, not a problem with Transifex, though.

Thanks for everyone's help. Once we have these three pages/posts reviewed I can put the other pages up for
translation. As I mentioned before, I don't see much value in trying to translate all the older announcements.

/D

[Pedro Neves]

On 23-07-2018 17:32, Dirk Hohndel wrote:
> This is a request for really quick and easy help from people who speak one of our website languages (Dutch,
> Finnish, French, German, Italian, Polish, Portuguese, Russian, and Spanish)...
>
>
> I re-ran things against the three files currently on Transifex and as far as I can tell the results look good.
> I'd appreciate if people could check them in the various translations and tell me if they can spot issues
>

Hi Dirk:

Looks good for pt_PT.

Cheers:

Pedro

[Salvador Cuñat]

Hi Dirk.

El lun., 23 jul. 2018 18:32, Dirk Hohndel <***@hohndel.org> escribió:

>
> I re-ran things against the three files currently on Transifex and as far
> as I can tell the results look good.
> I'd appreciate if people could check them in the various translations and
> tell me if they can spot issues
>

100% done for Spanish. Although ...
There were some new strings in the about page wich. Those showed as
translated but they were in English instead. This can make that some
untranslated strings go unnoticed if transifex claims 100% translated.

Best regards.

Salva.

>

[Dirk Hohndel]

On July 23, 2018 11:33:14 AM PDT, "Salvador Cuñat" <***@gmail.com> wrote:
>Hi Dirk.
>
>>
>
>100% done for Spanish. Although ...
>There were some new strings in the about page wich. Those showed as
>translated but they were in English instead. This can make that some
>untranslated strings go unnoticed if transifex claims 100% translated.

Yes, that's a flaw with how the uploading of existing translations works. Next on my list to figure out how to fix.

My main concern right now is if the rendered pages look correct. The were so many issues with the last set that I did a week ago...

/D

[Peter Zaal]

On Mon, Jul 23, 2018 at 6:32 PM Dirk Hohndel <***@hohndel.org> wrote:

> This is a request for really quick and easy help from people who speak one
> of our website languages (Dutch,
> Finnish, French, German, Italian, Polish, Portuguese, Russian, and
> Spanish)...
>
> > On Jul 18, 2018, at 1:04 PM, Dirk Hohndel <***@hohndel.org> wrote:
> >
> > I'm having a very hard time not destroying the encoding of non-ASCII
> characters. And right now I have no idea why.
> > It all looks good when printed to stdout, and turns into garbage when
> printed to a file.
>
> I gave up on perl and rewrote the parser / transformation utility with
> C++/Qt :-)
>
> I re-ran things against the three files currently on Transifex and as far
> as I can tell the results look good.
> I'd appreciate if people could check them in the various translations and
> tell me if they can spot issues
>
> https://subsurface-divelog.org/
> https://subsurface-divelog.org/2018/07/announcing-subsurface-4-8-1/
> https://subsurface-divelog.org/2018/06/announcing-subsurface-4-8/


Pages look good for Dutch (nl_NL), no issues with encoding, diacritics as
far as I can see, great!

If your browser is set up in a non-English language that we support, it
> should show the localized version
> as you click on those links (does that still work? I haven't tested that
> in a while). And in any case, you can
> just use the language-selector at the bottom of each page...
>

This doesn't work for the announcing pages, they are redirect to
https://subsurface-divelog.org/2018/07/announcing-subsurface-4-8-1__trashed/
https://subsurface-divelog.org/2018/06/announcing-subsurface-4-8__trashed/


> One thing that I noticed (and am fixing as we speak) is that in the
> round-trip through GitHub the announcement
> posts are still losing their correct translated category. I thought I had
> that fixed, but apparently I was wrong.
> This is a GitHub/WordPress integration bug, not a problem with Transifex,
> though.
>

I don't really understand this, but is this the reason for the incorrect
redirecting?


> Thanks for everyone's help. Once we have these three pages/posts reviewed
> I can put the other pages up for
> translation. As I mentioned before, I don't see much value in trying to
> translate all the older announcements.
>
> /D
> _______________________________________________
> subsurface mailing list
> ***@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>

Peter

[Sergey Starosek]

Hi Dirk,

On Mon, Jul 23, 2018 at 7:32 PM Dirk Hohndel <***@hohndel.org> wrote:

> I re-ran things against the three files currently on Transifex and as far
> as I can tell the results look good.
> I'd appreciate if people could check them in the various translations and
> tell me if they can spot issues
>
> https://subsurface-divelog.org/
> https://subsurface-divelog.org/2018/07/announcing-subsurface-4-8-1/
> https://subsurface-divelog.org/2018/06/announcing-subsurface-4-8/
>
> If your browser is set up in a non-English language that we support, it
> should show the localized version
> as you click on those links (does that still work? I haven't tested that
> in a while). And in any case, you can
> just use the language-selector at the bottom of each page...
>

I observe two problems here:

1) redirects to announcement pages are broken, doesn't matter whether
Accept-Language HTTP header is present or not.

[image: image.png]

2) Home page does not handle Accept-Language header at all, English page is
always returned. I have to manually click language selector at the bottom.

Sergey

[Dirk Hohndel]

Sorry I'm so slow responding. Busy with my day job...

> On Jul 24, 2018, at 4:14 AM, Sergey Starosek <***@gmail.com> wrote:
> On Mon, Jul 23, 2018 at 7:32 PM Dirk Hohndel <***@hohndel.org <mailto:***@hohndel.org>> wrote:
> I re-ran things against the three files currently on Transifex and as far as I can tell the results look good.
> I'd appreciate if people could check them in the various translations and tell me if they can spot issues
>
> https://subsurface-divelog.org/ <https://subsurface-divelog.org/>
> https://subsurface-divelog.org/2018/07/announcing-subsurface-4-8-1/ <https://subsurface-divelog.org/2018/07/announcing-subsurface-4-8-1/>
> https://subsurface-divelog.org/2018/06/announcing-subsurface-4-8/ <https://subsurface-divelog.org/2018/06/announcing-subsurface-4-8/>
>
> If your browser is set up in a non-English language that we support, it should show the localized version
> as you click on those links (does that still work? I haven't tested that in a while). And in any case, you can
> just use the language-selector at the bottom of each page...
>
> I observe two problems here:
>
> 1) redirects to announcement pages are broken, doesn't matter whether Accept-Language HTTP header is present or not.
>
>

You can see that it sets a cookie to remember that you want English as preferred language (that's the icl_visitor_lang_js= en).
But I don't understand why it tries to forward you to a __transhed page. That's weird.
Ah, database corruption. The main post thought that its translations were trashed. WTF?

>
> 2) Home page does not handle Accept-Language header at all, English page is always returned. I have to manually click language selector at the bottom.

The language plugin SHOULD handle that, but it doesn't right now. I'm trying to figure out why...
Fixed it


/D

[Dirk Hohndel]

Next round. I have now added the "Download" page. And for this one I didn't pre-populate the translations because that was too much of a mess.
Please make sure that you leave all of the [s-var...] blocks unchanged. They currently are used to handle the version numbers and download links... I'm considering replacing those at some point with the original text (to make it easier for me to update the site when making a release), but for now those are needed.

Thanks for everyone's patience and support with this slow moving project. I hope that in the end this will make things a lot easier for all the translators. Right now it seems to create a fair bit of growing pain, TBH.

/D

[Miika Turkia]

On Mon, Jul 30, 2018 at 3:23 AM, Dirk Hohndel <***@hohndel.org> wrote:

>
> Next round. I have now added the "Download" page. And for this one I
> didn't pre-populate the translations because that was too much of a mess.
> Please make sure that you leave all of the [s-var...] blocks unchanged.
> They currently are used to handle the version numbers and download links...
> I'm considering replacing those at some point with the original text (to
> make it easier for me to update the site when making a release), but for
> now those are needed.
>

I cannot parse the following text:

Ubuntu (14.04 -- only up to Subsurface 4.6.4, 16.04, 16.10 (up to 4.6.4),
and 17.04), LinuxMint (17 (up to 4.6.4) and 18), and Debian Jessie (up to
4.6.4) and Stretch

Thanks for everyone's patience and support with this slow moving project. I
> hope that in the end this will make things a lot easier for all the
> translators. Right now it seems to create a fair bit of growing pain, TBH.
>

At least now it is easy to see what is translated and what is not.

miika

[Dirk Hohndel]

> On Jul 29, 2018, at 8:36 PM, Miika Turkia <***@gmail.com> wrote:
>
> On Mon, Jul 30, 2018 at 3:23 AM, Dirk Hohndel <***@hohndel.org <mailto:***@hohndel.org>> wrote:
>
> Next round. I have now added the "Download" page. And for this one I didn't pre-populate the translations because that was too much of a mess.
> Please make sure that you leave all of the [s-var...] blocks unchanged. They currently are used to handle the version numbers and download links... I'm considering replacing those at some point with the original text (to make it easier for me to update the site when making a release), but for now those are needed.
>
> I cannot parse the following text:
>
> Ubuntu (14.04 -- only up to Subsurface 4.6.4, 16.04, 16.10 (up to 4.6.4), and 17.04), LinuxMint (17 (up to 4.6.4) and 18), and Debian Jessie (up to 4.6.4) and Stretch

Our support for Ubuntu 14.04 and 16.10 ended with Subsurface 4.6.4. Same for LinuxMint 17 and Debian Jesse.

> Thanks for everyone's patience and support with this slow moving project. I hope that in the end this will make things a lot easier for all the translators. Right now it seems to create a fair bit of growing pain, TBH.
>
> At least now it is easy to see what is translated and what is not.

Yes, and that will be the case moving forward.

I just added another file (bugtracker) and am about to add 'thanks' as well.

/D

[Dirk Hohndel]

> On Jul 16, 2018, at 10:37 PM, Peter Zaal <***@gmail.com> wrote:
>
> Regarding the diacritic characters, I noticed that when you use the literal diacritics in the translated text, this does not show correctly on the website.
> E.g. in the translated text ‘BÃŒhlmann’ shows as ‘BÌhlmann’ on the website, or ‘geïntegreerd’ in Transifex shows as ‘geïntegreerd’ on the website.
> Using encoded text in Transifex shows correctly on the website (although not encoded there), e.g. ‘&eacute;&eacute;n’ shows as ‘één’. ‘&amp;’ shows as ‘&’.
> So I guess this means we should use html encoding for the ‘special’ characters.

I don't think that is the case. There is still something "off" here. But I'm not sure where in the (way too many step) pipeline it is going wrong.
But no, we should definitely use UTF-8 correct text in Transifex. And I need to figure out how to do the other steps without mangling the encoding.

/D

[Dirk Hohndel]

> On Jul 16, 2018, at 9:32 AM, Dirk Hohndel <***@hohndel.org> wrote:
>
>
> As always, nothing is as easy as it should be :-)

I continue to run into weird error messages trying to upload resources to Transifex - something that I've never experienced with the resources for the app translation.
I will continue to play with this, but I'll admit that I'm getting rather frustrated as there appears to be absolutely no useful feedback...

/D

[Miika Turkia]

On Mon, Jul 16, 2018 at 9:14 PM, Dirk Hohndel <***@hohndel.org> wrote:

>
> > On Jul 16, 2018, at 9:32 AM, Dirk Hohndel <***@hohndel.org> wrote:
> >
> >
> > As always, nothing is as easy as it should be :-)
>
> I continue to run into weird error messages trying to upload resources to
> Transifex - something that I've never experienced with the resources for
> the app translation.
> I will continue to play with this, but I'll admit that I'm getting rather
> frustrated as there appears to be absolutely no useful feedback...


Bummer. Anyway, indeed all the languages are available when viewing with a
real browser. And if it turns out that this is going to work, there are a
couple of titles that needs to be added to be translated. Otherwise the
translation seems to be pretty good. We would probably see quite a bit more
effort in the web site translations if it was done via transifex. Easier to
see what is not in sync.

miika

[Dirk Hohndel]

> On Jul 16, 2018, at 11:35 AM, Miika Turkia <***@gmail.com> wrote:
> > As always, nothing is as easy as it should be :-)
>
> I continue to run into weird error messages trying to upload resources to Transifex - something that I've never experienced with the resources for the app translation.
> I will continue to play with this, but I'll admit that I'm getting rather frustrated as there appears to be absolutely no useful feedback...
>
> Bummer.

You can say that again. I'm trying to get support from them, but of course we're on a free account, so... not holding my breath.

> Anyway, indeed all the languages are available when viewing with a real browser. And if it turns out that this is going to work, there are a couple of titles that needs to be added to be translated. Otherwise the translation seems to be pretty good. We would probably see quite a bit more effort in the web site translations if it was done via transifex. Easier to see what is not in sync.

Well, yes. Except that what makes it easy to see this is part of the manual processing that I need to do to get things into Transifex in the first place. But I view this as a one time cost since after that it does indeed become much easier.

/D

[g***@free.fr]

----- Peter Zaal <***@gmail.com> a écrit :
> Dutch done, almost all strings were already correctly transferred.
> Btw for the formatting placeholders, ctrl-alt-number didn't work for me, no

Please try Alt-number or AltGr-number.


Guillaume

[Sergey Starosek]

On Mon, Jul 16, 2018 at 3:31 AM Dirk Hohndel <***@hohndel.org> wrote:

>
> If you have the time and want to help, respond here, tell us when you are
> happy with the translation (and what language) and I'll take the experiment
> from there. If you don't have a Transifex account, signing up is easy and
> then ask to join the subsurface team - I or one of the language
> coordinators will add you (there is a manual approval step involved -
> sorry).
>
> Done for ru_RU.

Sergey

[Guillaume GARDET]

Hi,

----- Dirk Hohndel <***@hohndel.org> a écrit :
> This is a request for really quick and easy help from people who speak one of our website languages (Dutch,
> Finnish, French, German, Italian, Polish, Portuguese, Russian, and Spanish)...
>
> > On Jul 18, 2018, at 1:04 PM, Dirk Hohndel <***@hohndel.org> wrote:
> >
> > I'm having a very hard time not destroying the encoding of non-ASCII characters. And right now I have no idea why.
> > It all looks good when printed to stdout, and turns into garbage when printed to a file.
>
> I gave up on perl and rewrote the parser / transformation utility with C++/Qt :-)
>
> I re-ran things against the three files currently on Transifex and as far as I can tell the results look good.
> I'd appreciate if people could check them in the various translations and tell me if they can spot issues
>
> https://subsurface-divelog.org/
> https://subsurface-divelog.org/2018/07/announcing-subsurface-4-8-1/
> https://subsurface-divelog.org/2018/06/announcing-subsurface-4-8/

All looks good, event if this is a partial translation, as expected.

>
> If your browser is set up in a non-English language that we support, it should show the localized version
> as you click on those links (does that still work? I haven't tested that in a while). And in any case, you can
> just use the language-selector at the bottom of each page...
>
> One thing that I noticed (and am fixing as we speak) is that in the round-trip through GitHub the announcement
> posts are still losing their correct translated category. I thought I had that fixed, but apparently I was wrong.
> This is a GitHub/WordPress integration bug, not a problem with Transifex, though.
>
> Thanks for everyone's help. Once we have these three pages/posts reviewed I can put the other pages up for
> translation. As I mentioned before, I don't see much value in trying to translate all the older announcements.

Thanks,

Guillaume


>
> /D
> _______________________________________________
> subsurface mailing list
> ***@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface