Update custom language from parent language [#1071760]

Hello,

I have to create custom languages when they do not exist on localize.drupal.org. Unfortunately, even if I'm able to manually import .po files from the localization server that will refer to these custom languages, I won't be able to automatically update them with Localization Update as they don't "really" exist.

I'd like to know if it would be possible to update a custom language from a chosen parent language in the future. Let's say you want to create a new language called "Columbia", it would be great to be able to automatically update from Spanish.

Thank you !

Comments

Comment #1

Gábor Hojtsy

he/him

Hungarian

Hungary

CreditAttribution: Gábor Hojtsy commented 24 February 2011 at 15:06

This is entirely possible to implement, yes. Not sure what would be the ideal UI for it. Maybe a setting on the language on the language setup UI that would actually be stored by l10n_update?

Comment #2

anavarre

French

🇪🇺

CreditAttribution: anavarre commented 24 February 2011 at 15:27

Thank you for the quick answer.

Actually, I've been thinking about two UI possibilities : one in core, one in localization update

1. In core, when you add a new custom language, there could be a language dropdown based on localize.drupal.org's available languages saying "Select parent language"

2. In the localization update "Update" tab, when a message says "No information" (with the warning picto), there could be a link saying "Choose parent language"

What do you think ?

Comment #3

Gábor Hojtsy

he/him

Hungarian

Hungary

CreditAttribution: Gábor Hojtsy commented 24 February 2011 at 16:00

Drupal core features can get to Drupal 8 at this point, so not sure we want to aim including the feature in core :) We can modify the built-in user interface as we need though, so we can make it look like it comes from core to the uninitiated. I think the language setup (core) UI would be good to extend/modify.

Comment #4

anavarre

French

🇪🇺

CreditAttribution: anavarre commented 24 February 2011 at 16:33

Oh sorry I shouldn't have said "core" as I meant exactly the same idea than you : being able to add a new element in the built-in interface when Localization Update is installed.

So, what's next ? ;-)

Comment #5

Gábor Hojtsy

he/him

Hungarian

Hungary

CreditAttribution: Gábor Hojtsy commented 24 February 2011 at 17:08

I think a very similar issue probably exists in the l10n_client queue too... But since l10n_update we can consider a very essential module for localized Drupal installs, this is probably a better place for the functionality. We should find a way to store the data and work on a patch I guess :) (I'm not signing up to do that in the short future).