I agree with Rafaella that there are IU issues that are not translation.
An example of this (which I have not yet reported) is for example that
when a language uses fonts that have a lot of vertical height (such as
Khmer) the document recovery window (for the rare occassion in which OOo
Hi Rafaella,
On Mon, Apr 03, 2006 at 13:44:19 +0200, Rafaella Braconi wrote:
I am not quite sure to understand the reasons why we should replace UI
with translation
I thought 'translation' would be a more self-speaking name than 'UI' to
report bugs about wrong wording and spelling
Hi Pavel,
I am not quite sure to understand the reasons why we should replace UI
with translation
Rafaella
Pavel Janík wrote On 04/01/06 18:38,:
From: Eike Rathke [EMAIL PROTECTED]
Date: Tue, 7 Mar 2006 14:52:18 +0100
Hi,
So, to summarize, the new structure would be:
From: Eike Rathke [EMAIL PROTECTED]
Date: Tue, 7 Mar 2006 14:52:18 +0100
Hi,
So, to summarize, the new structure would be:
BIDIsba
codeihi
helpcontent iano
i18npooler
localedata er
translation iano(replaces
Hi all,
Eike Rathke wrote:
5. code and www components will stay
I'll take www component and we are looking for someone who will take
care about code component. Any volunteers?
Additionally to creating a 'localedata' subcomponent where I would be
the owner of, which we already agreed on,
Hi Pavel,
Your proposal appears to be a response to two problems:
1. ft leaving OOo
2. the increase in translation related issues as a result of more
thorough translation efforts
It seems appropriate to me. We (he project) do have one request. The BIDI
category allows us to differentiate
