Add Dhivehi language to l.d.o

When you create a report, leave the status to active; using a different status could confuse people about the report.

I found a project for the translation of Drupal in Dhivehi language hosted at launchpad (https://launchpad.net/drupal-thana), which has been registered on February 2009 by Abdulla Musthafa.
The reported license for the project reports Common Public License, GNU LGPL v3, Public Domain.

How many people would work in the translation to Dhivehi language?

Also, what is your relation to / do you have any contact to the people at https://launchpad.net/drupal-thana ?

Still waiting for your answer.

Since we have an existing team, we should rather try and integrate existing work instead of starting from a clean slate. Translating Drupal core is a huge task. It would be vital to get existing people from https://launchpad.net/drupal-thana to join this effort. They might not be aware of our cool tools.

Abdulla Musthafa maintains that effort, and he seems to be registered on drupal.org as http://drupal.org/user/379830. Sending contact email to him.

Looks like requestor lost interest. Marking this postponed (vs closed) in the interest of someone else finding it later, and continuing our discussion.

Let me repeat that localize.drupal.org would welcome an active team to take this on.

guys, if you need help, I am willing to participate...

thanks

A little over 2 years after, the launchpad hosted translation project for Dhivehi (https://launchpad.net/drupal-thana) does not exist anymore. So as Gabor mentioned in October 2010, an active translation team is very much welcome for localize.drupal.org.

Ahmed, will you be willing to manage the Dhivehi translation team?

Moving to new queue.

No feedback

@hass: and so? What does closing this request serve? Leaving it here at least provides a way for someone else to find like-minded people who were at least interested to contribute earlier. Hiding it away does not really help anything.

I'm not commenting on all issues. I think a queue do not need to keep everything open for 5 years if there is no progress and a language marked as abandoned.

It is not to keep the the languages away from the server. I think cases can be easily found and reopened. Typically we close cases as won't fix if there is no feedback.

@hass: I don't agree that we don't want to add Dhivehi to the site.

I never said we do not want to add more languages on the server. I only said, if there is no maintainer I do not understand how translation should happen and we can close the case as we may stand on the same point in 5 more years.

On the other side - create the languages and leave them untranslated and we can close the cases here as the create job has been completed. Then you have the languages on the server, but no single line of translation. Not sure what you win... :-)

@hass: this issue is not "Add Dhivehi language to l.d.o only if so and so is the maintainer" it is "Add Dhivehi language to l.d.o", that's it.

As a localize.drupal.org maintainer, I

1. Don't want to tell Dhivehi that their language is not welcome. It is. Its not won't fix.
2. Don't want to do the research on language codes, plural forms, related other teams, etc. again each time someone proposes Dhivehi

As a potential Dhivehi translator, I

1. Don't want to see an issue closed won't fix for my language. Why do these people refuse to add it?
2. Don't want to need to do all that research about language code, plural forms, etc. all over again, that people already did and likely debated to death.
3. Would love to see who else proposed before, who has local translations, etc. so I can contact them, and even if they don't answer, it helps me prove there is more interest other than myself.

Enough reasons?

Again, I have not said won't fix to this issue in sense that we do not want it on the server. You should read my comments again.

"Add Dhivehi language to l.d.o", that's it.

Why the hell are you not adding it to the server? Just DO IT and close these 5 years old cases, please.

This would have saved the time for both of us.

@hass: I think you were among the people who complained about non-responsive team managers, where suggestions submitted were never reviewed. We can create any number of languages, but if there is no review process, no delegation of power, etc. then it is not going to work, people just submit things into a black hole. Is that what you are suggesting?

We can create any number of languages, but if there is no review process, no delegation of power, etc. then it is not going to work

That is why I closed the case after 5 years of inactivity. We have no perspective.

We will also run into the same situation if you create the language now and the current maintainer leaves the community 3 months later and the language is created. Than we are in the same - black hole - situation you are complaining about. We win nothing.

I suggest creating the language, place a message on the language group home that this is currently unmaintained and looking for new maintainers (and explain how to become one). Than we have the job done here and we only need to find one or more maintainers what is just a permission thing. We do not demotivate people waiting here 5 years to get the language added without success. The signal is clearer on the end of the day - the language exists and we try to provide it to users. We only have a manpower problem in these languages and looking for help. A translator will not search the localize.drupal.org issue queue first if there is already a request pending. They see localize.drupal.org site and their language is missing and it looks like we do not support the language - the wrong signal.

Aside - it is also hard for me to find this queue here. The name changed so often that you cannot remember anything. And newbies will not find it at all. If there has been no reference on l10n_server I would have missed the queue again.

https://localize.drupal.org/ has a sidebar titled "Set up your group here!", with a link to https://www.drupal.org/project/issues/search/localizedrupalorg?status%5B... which is the canonical list of all the languages that someone sometime proposed but they are not yet added. I don't share the view that its hard to find.

What about the rest?

@hass: I don't think I left anything out. I already explained why we have these issues open in #18. I can re-word it with why we don't create the languages for you if that helps, but it was already explained in #18.

We not only ask technical questions but ask about momentum as well (whether there are others you would work with and whether there is prior art). As in this case, Dhivehi had prior art. We lack Dhivehi talent to tell the quality of said prior art. Yet we don't want Drupal translators to start from scratch on localize.drupal.org if there is prior art. Why make them suffer more when they don't need to. People speaking Dhivehi can do the vetting of the prior art and start using it. We intend to help start off translation teams with people devoted to the cause and if there was prior art, a head-start. That is all lost if we ignore those and just open teams. We would still need to link back to these issues and hope people read them for information on who else has local translations on their site and where is prior translation to import. Why make their life harder?