Posted by akis p on October 28, 2008 at 7:12pm
Jump to:
| Project: | Localization server |
| Version: | 6.x-2.x-dev |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Is it possible?
Also can be there a permission option for the submitting remote translations?
Without accepting theme as suggestion but as approved?
Thanks.
Comments
#1
If you don't enable l10n_remote, you don't allow people to use the remote feature. Otherwise you'd like to limit who can do local but not remote suggestion? What types of users would get permission to be able to submit local but not remote?
The remote translations are accepted as suggestions.
#2
By server i mean localization server, if you have
a localization server running locally or on a custom domain for your own use or whatever,and you want to submit
the input translations to the team server also.
As suggestion or what other permissions you will have by the team.
Exactly, an extra option to allow to the privileged users to submit them as approved?
#3
#4
Updating issue. For now, you can still export .po files on a server, and import them easily on another one. No automated way to do this. This might become interesting with distributions possibly having their own flavors of translations feeding upstream.
#5
Suppose server could export strings not only importing. it's just another xml-rpc call.
This feature could extend l10n_client with ability to call server for suggestions of string (just another button in UI)
#6
The server already has l10_packager and localize.drupal.org has all the packages nicely in line on ftp.drupal.org for download. So its a matter of automation of import. We already have export automated.
#7
I about full export but mostly there's no need in all-core-modules-export-file
I think server should have ability to return a one string or set of strings with suggestions via rpc-call
#8
Can you please explain how to correctly configure l10n_server to automatically retrieve translations from l10n_client?!
I have one local environment needed to be translated and another acting as localization server. I have configured l10n_client as needed, entered API key, pointed to localization server and checked to share translations.
On server side installed:
- 10n_server
- jquery_update 2.х
- potx
- l10n_pconfig
But from available connector I do have only:
- Drupal packages from the file system
- Drupal packages from file uploads
- Gettext files from file uploads
No option to retrieve translations from l10n_client or via XML-RPC?!... Am I doing something wrong?! But I cannot get l10n_client sending translations to server :( Please help.
#9
@chaugi: this issue is not about your request, but basically, you can look up the database log messages for the site you are running l10n_client on. The way it works is that each string you enter on the l10n_client interface gets submitted right away to the server. The server will only save it if (a) you have permission to submit suggestions in that language (b) the source string is present on the server. Make sure that these are correct. If you'd like to submit more than one translation at a time, you can just export a .po file in Drupal and import that to the server by hand. Easy and quick :)
#10
@Gabor
(a) you have permission to submit suggestions in that language
On both environments I am under user/1 should be fine but I have granted all permissions for test purpose in order to be 100% sure
(b) the source string is present on the server
It mean that on server I have to install all the samo modules and recreate all the same content to submit suggestion and I am not able to add my own translation if there is no source string?! Insane... So no way to remotely submit source string as well?!
I have tried to submit translation for build-in "Home" in bredcrumb, but no luck, seems that I have something missing on server side :( Any ideas?!
!!!I have found in client side log:
Translation rejected by remote server. Reason: Source string not found on server, translation not saved.
1. How can I move source strings from client environment to server?!
As I have no option to export PO files in English on client environment
2. How should I import these file to Server, should I use using Translate Interface->Import?
#11
Yes, the concept of the server includes relating strings to projects. If you just submit source strings free form to the server, it will have no data to relate the strings to projects. The idea is that you set up the source strings for translations on the server. You can set those up with the gettext connector by importing the .po files for the modules or with the Drupal connector with local files by getting it parse the source code of the modules.
BTW not sure why you even set up a localization server, would you like to reuse those translations or share with someone else? From what I've read so far, I'm not sure you need to run a server.
#12
@Gabor:
The idea is following. I work for company, we create websites for clients, few projects each month. We build purely on Drupal. 99% of website are multilingual, almost no single language. And the main thing is, that when we do give access for client to their website, we do not give Full access, we give limited permissions to certain parts of CMS (using SimpleMenu, FormFilter) just to manage content and not to screw up Drupal settings, this way we maintain guarantee. This way we do not need to translate all the parts of the website in CMS only the part visible for clients + front-end for end users of course.
This way no it looks like we have to re-translate each project from scratch, what is inconvenient. So we would like to automate this somehow. But we don't want to translate all modules just some parts of them. I thought (looks like I was wrong), that enrolling l10n_server I could create a central repository for our translations and submit translation copy directly on it, so it is going to be filled with translations gradually, and existing translations are going to be reused in next projects. So I wanted to avoid parsing whole modules and trying to translate them phrase by phrase as l10_client approach for translation is comfortable, to translate only visible parts (easy to search for untranslated strings).
Please guide to the right path, as my conceptions seems to be incorrect.
Thank you.
#13
Well, why don't you use localize.drupal.org itself? The community would benefit AND help out with the work.
Even if you go your own server, setting up a localization server and parsing all projects completely does not mean you need to translate them all. You can still only use it with l10n_client as the input UI and then only those strings will be translated. If you set up l10n_packager (included with l10n_server) on the client, you can feed the translations to client sites with l10n_update. Just set it to use your server, not localize.drupal.org.
Ultimately I think it would be best to work with the community, you'll help them, they'll help you. Also, you'll not need to maintain this whole infrastructure.
#14
I do agree, sound reasonable. But what about Interface translations, we build own webforms translate them, or we create CCK and translate them, this also goes to the community? Or just modules translation?!
#15
The localization server is designed for interface translation. It can be tweaked to do webform and CCK translation in some ways, but that might or might not be easy to do.