Sign off commits in Nextcloud Notes for iOS

[i2h3]

See commit message.

[rakekniven]

@i2h3 On Transifex we use de_DE for all mobile apps and desktop client as well.

[i2h3]

On Transifex we use de_DE for all mobile apps and desktop client as well.

@rakekniven @nickvergessen Can you please explain? On Transifex, there is only de used for the resources like notes-ios-localizable, not de_DE:
https://app.transifex.com/nextcloud/nextcloud/notes-ios-localizable/

[rakekniven]

On Transifex we use de_DE for all mobile apps and desktop client as well.

@rakekniven @nickvergessen Can you please explain? On Transifex, there is only de used for the resources like notes-ios-localizable, not de_DE: https://app.transifex.com/nextcloud/nextcloud/notes-ios-localizable/

No, it is different.
See the informal german version de at:
https://app.transifex.com/nextcloud/nextcloud/translate/#de/notes-ios-localizable/565679215

All strings are translated with "Benötigt keine Übersetzung. Hier wird nur die formelle Übersetzung verwendet (de_DE)."

See formal german version de_DE at:
https://app.transifex.com/nextcloud/nextcloud/translate/#de_DE/notes-ios-localizable/565679215 Here are the translations.

[i2h3]

Why is it set up like that? That does not sound like locale codes are supposed to be used (or at least localization tools usually have other mechanisms to offer variations like formal and informal). Personal and formal variants are not covered by locale codes. de is the general German language itself while de_DE is the more specific and region aware locale to distinguish from, in example, de_CH with its partially different orthography and vocabulary. Why isn't the German localization simply in de? That would save unnecessary steps and simplify the process. Is this a caveat from setting up all resources from different products in the same project on Transifex (thus inheriting organization from technically independent products to have consistency)?

[rakekniven]

Why is it set up like that?

History.

This has been the case since the start of the project (IIRC Joas told me it has been that way before the fork as well). There is no support for formal and informal German in ISO 639 (1, 2, 3) and POSIX locale does not prohibit our use (as far as I understand it).

The only good thing about our implementation is that we use the same for Android, iOS and desktop and talk client.

A change has been part of discussions from time to time ... but so far nothing has been planned.

Why isn't the German localization simply in de?

Which one? We have two.

to have consistency

Please think in the view of translators. Actuall all resources in project "Nextcloud" of language de is informal and de_DE is formal. The translator does not need to have any knowledge of the technology used to decide which variant to use for each project.

[i2h3]

History.

I thought so. 😁

Which one? We have two.

Not for the iOS apps, as you wrote yourself.

All strings are translated with "Benötigt keine Übersetzung. Hier wird nur die formelle Übersetzung verwendet (de_DE)."

But I get that translators (and that is what I meant) just look at the app resources the same way with the additional detail of just ignoring de in those cases.

Now the bigger picture makes sense. Is this documented somehow or free floating knowledge so far?

[nickvergessen]

Is this documented somehow or free floating knowledge so far?

It's documented in the process and knowledge transfered to all people involved in the syncing process (tobi and me)

[i2h3]

@nickvergessen @tobiasKaminsky Please review again. The amendments have been made.

[i2h3]

@nickvergessen I cannot test these scripts so I discarded most changes and reduced it to the initial motivation of just fixing the sign off and bringing the commit message in line with the server repository.