Testimonials: Add Tom Yates #119

Merged
max.mehl merged 1 commits from janwey/fsfe-website:yates into master 2019-02-01 12:59:33 +00:00
Contributor

~There was no image provided. Before merging this, let's discuss, if we want placeholder images?~

Edit: I just realized, that Tom Yates already had a quote, the file was named after hist first name, though (inconsistency sigh). So I deleted all of the old files for him.
I did not change his image-name as that may be in use somewhere else too(?)

~There was no image provided. **Before merging this**, let's discuss, if we want placeholder images?~ Edit: I just realized, that Tom Yates already had a quote, the file was named after hist first name, though (inconsistency *sigh*). So I deleted all of the old files for him. I did not change his image-name as that may be in use somewhere else too(?)
Owner

Hm, it's sad that by that we'll lose some translations...

What does anyone think about the quotes. Is the "new" quote much better than the old which could justify removing the translations?

Hm, it's sad that by that we'll lose some translations... What does anyone think about the quotes. Is the "new" quote much better than the old which could justify removing the translations?
max.mehl added the
wait/misc
label 2018-02-07 08:29:57 +00:00
Author
Contributor

I'll add some more quotes that are still in my queue and will contact translators@ afterwards. That way, we may be able to get all languages again and use the new quote.
You can probably leave this PR open until then :)

I'll add some more quotes that are still in my queue and will contact translators@ afterwards. That way, we may be able to get all languages again and use the new quote. You can probably leave this PR open until then :)
Contributor

Could the approach outlined below work as an alternative that does not lose the old translations, but still update the English quote by giving a chance to the different teams to update later on?

  1. Instead of removing the tom.??.xml files, rename them all to yates.??.xml (including the English version), and push it.
  2. Update yates.en.xml with the new English quote and push it, so that translators can see that their version is outdated from http://status.fsfe.org/translations.html and update to the best of each teams' availability (assuming .xml files are listed there too)
Could the approach outlined below work as an alternative that does not lose the old translations, but still update the English quote by giving a chance to the different teams to update later on? 1. Instead of removing the tom.??.xml files, rename them all to yates.??.xml (including the English version), and push it. 2. Update yates.en.xml with the new English quote and push it, so that translators can see that their version is outdated from http://status.fsfe.org/translations.html and update to the best of each teams' availability (assuming .xml files are listed there too)
Owner

Hm, but wouldn't it be the same effect if we just updated tom.en.xml with the new text here? This should also outdate existing translations.

But as you implied, I'm quite sure XML files are not taken into consideration on the status page. So I'm rather thinking of deleting the old translations and send a mail to the translators list to ask for a review and translation of all quotes.

Since the new text is completely different from the old, I don't see many reasons to keep the old translation, apart from the fact that there would be at least some native text on the translated pages (but a heavily outdated one).

What do you think?

Hm, but wouldn't it be the same effect if we just updated tom.en.xml with the new text here? This should also outdate existing translations. But as you implied, I'm quite sure XML files are not taken into consideration on the status page. So I'm rather thinking of deleting the old translations and send a mail to the translators list to ask for a review and translation of all quotes. Since the new text is completely different from the old, I don't see many reasons to keep the old translation, apart from the fact that there would be at least some native text on the translated pages (but a heavily outdated one). What do you think?
Contributor

Fair enough. Also, if the status page doesn't show XML files, it's true the required translations might easily be missed.

Fair enough. Also, if the status page doesn't show XML files, it's true the required translations might easily be missed.
max.mehl approved these changes 2019-02-01 12:58:24 +00:00
max.mehl approved these changes 2019-02-01 12:58:51 +00:00
max.mehl left a comment
Owner

Let's get this finally off the table ;)

Let's get this finally off the table ;)
max.mehl closed this pull request 2019-02-01 12:59:33 +00:00
max.mehl deleted branch yates 2019-02-01 13:00:03 +00:00
Sign in to join this conversation.
No description provided.