WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-api

Re: [Xen-API] New Xen.org Community Manager

To: Todd Deshane <todd.deshane@xxxxxxx>
Subject: Re: [Xen-API] New Xen.org Community Manager
From: George Shuklin <george.shuklin@xxxxxxxxx>
Date: Mon, 20 Dec 2010 06:31:50 +0300
Cc: xen-api@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 19 Dec 2010 19:31:24 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=8VgSmH8GHmXY6QmcAaZsjd9gFK3P1sct3MBuWWOYXn4=; b=Tdk3tcyblgLmexHRfZ/yMk/XRsHFxa/GggXZrVLTl3u1M8pMwOQlhBb/7FUtxxlYNv mA6G3p20aSbCsORkf8C5TcU2IJRKzE7O92/6gKcLXeLiYVmQADEYYn9yuf0YVyEibsj+ fbgB2XU5l9WFrIyVYNWEJKaELRgmt16c15tCE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=P4u4KNzHJupx4SgHTi/NJjwecX7kk+vGnnYNxBlYkti9y5jC9Q1LqerZKjdy7z12+o O3fJPWW0+GOBzJcxEqpqFWrndQSuMTaYnKjWo6JW2C66r3s2ftBZrfbn4B+kUQHgKFwL ePJBZxeegxVjp3MfrFYgdugFG7XQ2+ZYS83D0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTikzN=168ADWu9uCxT2-i3ZSes-4=AYY-3NyLuJa@xxxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <4FA716B1526C7C4DB0375C6DADBC4EA38D80964184@xxxxxxxxxxxxxxxxxxxxxxxxx> <1292802895.11718.32.camel@xxxxxxxxxxxxxxxx> <AANLkTikzN=168ADWu9uCxT2-i3ZSes-4=AYY-3NyLuJa@xxxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Good day.

Well, about Russian translation for wiki I can say one thing: better
English than that Russian (I think anyway English is essential to read
xen documentation - to be priestly - fragments of documentation, so we
can freely throw away wiki translation).

Some samples of incorrect russian translation:

Attachment translated as 'приложения' (reverse translation is
'application') instead 'вложения' (something that put inside, attached).

In attachment list first action named as 'взять' (I can even image what
it was in original), from russian it translate as 'take away'.

'Clear cache' translated as 'убрать из кеша' (take way from cache).

Lexically incorrect phrase 'Чтобы создать пользователя или восстановить
пароль служит страница' (word translated correctly but put together in
strange form and order).

One more: almost half of text is non-translated, so i looks something
like this sometimes: If want to re-login, just use Полное имя and Пароль
and click on Войти.

So, I think there is no need for interface localization (many efforts
with little payback) and it can be (at least, for Russian) simply left
English, this will be much easily compare to samples above.

В Вск, 19/12/2010 в 21:48 -0500, Todd Deshane пишет:
> On Sun, Dec 19, 2010 at 6:54 PM, George Shuklin
> <george.shuklin@xxxxxxxxx> wrote:
> >
> > Good.
> >
> > That man will be response for differ xen documentation and site content?
> > I have tons of ...um... bug-reports for wiki (with horrifying Russian
> > interface translation, worse than simple google-translate) and some
> > requests for XCP documentation systematization...
> 
> Please send these wiki bug reports to me, so we at xen.org can start
> looking into them.
> 
> We are also in the process of improving the XCP documentation process.
> Feel free to send me your suggests and requests, so that we can
> discuss them with you. We can then bring results and questions back to
> the appropriate parties and mailing lists as appropriate.
> 
> We'll refine this overall process over time and document the proper
> procedures and contact persons as needed.
> 
> Thanks,
> Todd



_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

<Prev in Thread] Current Thread [Next in Thread>