| Language files [message #8249] |
Tue, 10 July 2007 18:31  |
 drank 
Messages: 1324
Registered: June 2007 |
Senior Master |
|
|
Hi,
There is a problem with the language files for languages different than English. For example, the string "Update Home" is not a single item in the language file but rather it is composed of two items - "Update" and "Home". But in Bulgarian for example the meaning of Update Home cannot be presented by putting together the Bulgarian translations of the words Update and Home. It is completely different expression and in the current implementation of the language files there is no way of correctly translating this.
The same goes for "Client Home" and other composite expressions.
Is it possible that you review the language files and set all kinds of such composite expressions to be single items in the language files? Like this:
$__description["update_home"] = array("Update Home");
$__description["client_home"] = array("Client Home");
I would also suggest instead of using a function for plurals, to use simply two items in the language file - one for the singular form and one for the plural (if there is a need for plural). This way you will make it easier for translations.
Thank you.
Dragomir Denev
DGM
www.dgm.bg
|
|
|
| Re: Language files [message #8251 is a reply to message #8249] |
Tue, 10 July 2007 21:10  |
Lxhelp
Messages: 23691
Registered: July 2006 |
The Champion |
|
|
update home is not English either, it is a computer science term, :-) . Our language is built into the code itself. For instance, 'update home' is defined nowhere, instead lxadmin gets the description of the class--'update', and then adds 'home' to it. Of course, you can override it by redefining it. This is how we are able to add a lot of features so fast. Lxadmin has a framework that will automatically generate everything if we don't specifically define it. As such, I think it should work in all languages.
"domain Home", basically means the root display of the object domain. So, it could as well be 'domain root', 'domain show' etc. The thing is that the terminology is consistent. For instance, 'home' for any object--client, domain, vps--means the core place.
But it can be overriden by specifically creating a description for the 'show action'. I will add it if it is needed.
| Quote: |
> There is a problem with the language files for languages different than English. For example, the string "Update Home" is not a single item in the language file but rather it is composed of two items - "Update" and "Home". But in Bulgarian for example the meaning of Update Home cannot be presented by putting together the Bulgarian translations of the words Update and Home. It is completely different expression and in the current implementation of the language files there is no way of correctly translating this.
>
> The same goes for "Client Home" and other composite expressions.
>
> Is it possible that you review the language files and set all kinds of such composite expressions to be single items in the language files? Like this:
>
>
> $__description["update_home"] = array("Update Home");
> $__description["client_home"] = array("Client Home");
>
|
| Quote: |
> I would also suggest instead of using a function for plurals, to use simply two items in the language file - one for the singular form and one for the plural (if there is a need for plural). This way you will make it easier for translations.
>
|
You can always define the problem words in an array, --if you have a language that's plural unfriendly.
You can define 'get_plural' as
function get_plural($word)
{
$list = array("peculiar word" => 'plural for peculiar word');
if (isset($list[$word])) {
return $list[$word];
}
return "{$word}s";
}
The work involved for you would be same, whether you are using the above method or we have plural explicitly defined in the language files. But it will make it easy for simple languages like english.
Thanks.
|
|
|
|
|
| Re: Language files [message #8372 is a reply to message #8362] |
Thu, 12 July 2007 20:39 |
Lxhelp
Messages: 23691
Registered: July 2006 |
The Champion |
|
|
I will need some time to fix the language problems. I am working on rewriting the entire interface, and dumping simple_xml, that will allow you to have meta-chars too. But it will take another 3-4 weeks. And also allow help properly in individual language etc.
Thanks.
On Thu, Jul 12, 2007 at 08:29:23PM -0000, Dragomir Denev wrote:
>
>
> Why do you not answer? Please, this is important for me. Thank you.
|
|
|
|
| Re: Language files [message #9955 is a reply to message #8446] |
Sat, 04 August 2007 16:03 |
Lxhelp
Messages: 23691
Registered: July 2006 |
The Champion |
|
|
Hi,
The interface has been completely rewritten, and all xml has been removed. Now you should be able to add meta characters in the input.
Thanks.
On Sat, Jul 14, 2007 at 01:16:25PM -0000, Dragomir Denev wrote:
>
>
> Thank you for the reply. I will bump this topic after 4 weeks then :)
>
> Best regards
|
|
|
| Re: Language files [message #9980 is a reply to message #9955] |
Sun, 05 August 2007 04:40 |
|
Hi,
Great new that you have rewrite the interface.
I have tested in Admin Home, on the option "informations", i put "Informações" and on showing the buttons works... but when i press for see informations, only load page until "informa", dont show "Informations for admin"
Thanks
Samuel
Thanks,
Samuel
|
|
|
|
HyperVM & Kloxo Support
Members
Search
Help
Register
Login
Home
