On 31/05/2008, at 12:49 AM, Rafaella Braconi wrote:
Dear Localizers,
this is for all the ones who wonder where to find the strings for a
specific extension
I've created a wiki with a short overview of the CVS modules
containing the UI and Help strings for the extensions. Also, I
Hi everyone :)
I'm a little confused about codelines. Thanks to Pavel's excellent
presentation [1], I do understand that we branch the main codeline for
releases (and branch it even more for child workspaces), but I don't
know if the main codeline also includes the newer features and
On Sat, May 31, 2008 at 11:25 AM, Clytie Siddall
[EMAIL PROTECTED] wrote:
Hi everyone :)
I'm a little confused about codelines. Thanks to Pavel's excellent
presentation [1], I do understand that we branch the main codeline for
releases (and branch it even more for child workspaces), but I
On 31/05/2008, at 6:36 PM, Ain Vagula wrote:
On Sat, May 31, 2008 at 11:25 AM, Clytie Siddall
[EMAIL PROTECTED] wrote:
Hi everyone :)
I'm a little confused about codelines. Thanks to Pavel's excellent
presentation [1], I do understand that we branch the main codeline
for
releases (and
Hi Clytie,
For example, we have been testing the DEV300 codeline, which will
eventually become the OpenOffice.org 3.0 release. The BEA300 codeline so
far has contained the 3.0 Beta m1 and m2 builds.
you can see the DEV300 codeline as TRUNK for all development that is
done for versions
On 31/05/2008, at 6:36 PM, Ain Vagula wrote:
On Sat, May 31, 2008 at 11:25 AM, Clytie Siddall
[EMAIL PROTECTED] wrote:
Hi everyone :)
I'm a little confused about codelines. Thanks to Pavel's excellent
presentation [1], I do understand that we branch the main codeline
for
releases (and
Hi all,
While into dev300 pot files, there is next file,
/sdext/source/presenter/registry/data/org/openoffice/Office.pot
there isn't any localize.sdf file into OOo dev300 source. Let see:
$ ls
ooo_DEV300_m14_src/sdext/source/presenter/registry/data/org/openoffice/Office/
Addons.xcu CVS
Hi all,
Even a GSI file has all UI messages trsnalated, when I'm running:
localize -m -l eu -f GSI_eu.dfs
it not merge back messages into next file:
ooo_DEV300_m14_src/svtools/source/contnr/localize.sdf
can be fixed for m15?
Thanks and best regards,
dooteo
Hi,
please do not start new threads by replying to old mails. If you do
so, please do it correctly and do not set In-Reply-To and similar
headers.
On 31.5.2008, at 16:45, dooteo wrote:
Even a GSI file has all UI messages trsnalated, when I'm running:
localize -m -l eu -f GSI_eu.dfs
it
Hi everyone :)
Do we have a wiki page or other doc explaining where to find, and how
to translate the OpenOffice.org interface strings which lie outside
our current GSI file?
I made a note some time ago, that kami said:
Note: not all translatable elements in GSI / PO files. Some
On 31/05/2008, at 6:51 PM, Joost Andrae wrote:
Hi Clytie,
For example, we have been testing the DEV300 codeline, which will
eventually become the OpenOffice.org 3.0 release. The BEA300
codeline so far has contained the 3.0 Beta m1 and m2 builds.
you can see the DEV300 codeline as TRUNK
11 matches
Mail list logo
