Topic: [ALERT] -- Several languages will be removed from the SME server!

[bpados]

Hello! Please don't remove hungarian translation yet! I've spent a lot of time for it! Now I'm hardly working on it to finish in time! About 1 week and the process is ended!

THX

As much as my time allows i should be able to help you with Hungarian translation. Let me know how I can help?

Szevasztok.

Bela.

[e[nt]e]

As much as my time allows i should be able to help you with Hungarian translation. Let me know how I can help?

Szevasztok.

Bela.

Register at http://translate.contribs.org/. You will then be able to login and suggest translations. That means these suggestions won't be applied but need someone who reviews and accepts them. For Hungarian that is only tacsaby at the moment. So when you want to translate directly please follow the instructions found in the wiki:
http://wiki.contribs.org/Translations#Pootle_for_translators

Regards,
Niklas

[tacsaby]

Hi!

I've recently installed an SME system. I'm noticed that, after updating, the server manager turned into a semi-hungarian-translated state. It's so sticky. Every hungarian SME server turns into same state? Some items are translated, some not. Hungarian translation are 100% ready. Would somebody update the hungarian locale rpm in SME repositories with the new translation? It would be nice, if next update fix this problem. 

[Normando]

For test the last updates before they are released do:

Code: [Select]

yum update --enablerepo=smeupdates-testing smeserver-locale-*
signal-event post-upgrade
signal-event reboot

[MAuVE]

I tested the new Greek locale.

I found out that some chunks of text still appear untranslated.

I went to poodle to find-out that new content had been added in emailsettings.po and backup.po.

I will translate the additional entries.

Apparently, poodle is not updated:

a) The button in the Collaboration/Groups entitled "Add Group" appears in Greek as "CLICK_TO_CREATE"

b) The bulk of Security/User remote access remains untranslated while poodle shows  remoteaccess.po as 100% finished.

c) "Domains" remains still in English although translated.

Please confirm that poodle depicts latest programme status, so that I can run a full check of the Greek translation

[Normando]

Yes Mauve, me too. I have some words untranslated at my server-manager, but in Pootle are all 100% translated. I hva no time today, but I will report a bug about this issue.
Are you updated your locale rpms from smeupdates-testing repo?

[tacsaby]

I've noticed similar problems in hungarian translation like MAuVE 

[Normando]

Please Mauve and tacsaby, report a bug

[cactus]

Yes Mauve, me too. I have some words untranslated at my server-manager, but in Pootle are all 100% translated. I hva no time today, but I will report a bug about this issue.
Are you updated your locale rpms from smeupdates-testing repo?

The latest releases with all translations (excluding the ones in tha waiting patches) should be in smeupdates-testing. You can install them on your test server like this:

Code: [Select]

yum update smeserver-locale* --enablerepo=smeupdates-testingPlease only do this on test machines and not on production servers.

[MAuVE]

What I referred to as "additional" entries proved to be existing entries marked-up as fuzzy for reviewing.

Thanks to the person that made those annotations, I corrected some obvious errors* but failed to see the reasoning for others.

If he or she is reading this, please give some more explanation regarding the latter.

Now poodle shows again 100% finished.

When this version is made availalable to the smeupdates-testing repository I will check what was fixed and what remains to be.

I will open a bug ticket for anything it seems not normal to me.

(*) In Greek, like in French, we have genders i.e: male, female and neutral

When translating sectioned and artificially composed sentences it is very easy to mix the genders.

Example:
Allow access: a) private b) public c) disabled (here disabled should take it's female form, because it follows access which is female)

but:
User account: a) disabled should be in it's male form because account is male

and last:
Protocol: a) disabled -> neutral

I will circumvent this problem of multiple use in different genders by juxtaposing all 3 suffixes to words, like disabled, that are used in many ocassions.

[e[nt]e]

When this version is made availalable to the smeupdates-testing repository I will check what was fixed and what remains to be.

I will open a bug ticket for anything it seems not normal to me.

I've seen you've done so already. Next time please post the link to the bug here as a reference.
http://bugs.contribs.org/show_bug.cgi?id=4759

Currently there is version 2.0.0-10 of the 7th November in the smeupdates-testing repo. So if you you updated from there to test the translations you wouldn't have the actual version installed as that one's not released to the repos yet. May be that the problem is fixed with the next version released and then this would be just needless, but there's no offence taken and I appreciate your efforts and that you opened a bug for this.

(*) In Greek, like in French, we have genders i.e: male, female and neutral

When translating sectioned and artificially composed sentences it is very easy to mix the genders.

Example:
Allow access: a) private b) public c) disabled (here disabled should take it's female form, because it follows access which is female)

but:
User account: a) disabled should be in it's male form because account is male

and last:
Protocol: a) disabled -> neutral

I will circumvent this problem of multiple use in different genders by juxtaposing all 3 suffixes to words, like disabled, that are used in many ocassions.

That got nothing to do with the problem mentioned before, does it? If so please clarify what you're talking about. For me that seem to be just translation problems which would need to be discussed elsewhere, but not in this thread I'd say.

Regards,
Niklas

[MAuVE]

e
That got nothing to do with the problem mentioned before, does it? If so please clarify what you're talking about. For me that seem to be just translation problems which would need to be discussed elsewhere, but not in this thread I'd say.

Regards,
Niklas

It is only very-very remotely related. I will explain myself:

When writing code to be translated into languages other then English, it's a good practice to "match text pairs".

As per my example a universal "disabled" can't fit all bills and ideally there should be a different "disabled" for "Allow access", "User account" etc.

If this is the right place to mention this or not, I do not know, but I know that someone tried the Greek translation and didn't like what he/she read because of this. 

[cactus]

If this is the right place to mention this or not, I do not know, but I know that someone tried the Greek translation and didn't like what he/she read because of this.

No this should be reported in the bugtracker so we can deside if we are to do anyhting about it, which I doubt as it will make maintaining translations complicated like it was before.
The best suggestion IMHO is to make translations as general as possible, like suggested in an earlier post in this thread.

[Normando]

For test the last updates before they are released do:

Code: [Select]

yum update --enablerepo=smeupdates-testing smeserver-locale-*
signal-event post-upgrade
signal-event reboot

Me wrong! Sorry guys.

For test the last translations you must check under testing server, and shoul be SME7.4, NOT 7.3!

[MAuVE]

Where is the following residing so I can have it translated ?

"Warning: a reboot is required before proceeding! Failure to reboot now may leave your system in an unknown state!"