Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


Hi :)
The main man to chat with about OmegaT is Milos errr, i dunno his surname!
:(  He has done a huge amount of work with them to set-up something for
LibreOffice.

It is good that you started translating by starting on the Base Handbook.
It means you really can work at your own pace because i seriously doubt
anyone else is working on it.  As you point out it is a good thing to work
on but i think people tend to be a bit scared of database programs
generally (probably thanks to needless complexity that Access exposes
normal users to far too early).  On this mailing list we found that it was
after the Faq section about Base and the first chapter of the Base Guide
were both completed that there were suddenly a lot more threads discussing
Base.  It led to a resurgence of interest with people joining in and
getting to know it and even becoming devs for it.

Errr, i guess i should have mentioned that there is a more up-to-date
version of the Handbook available through the Documentation Team (extremely
low-traffic mailing list at the moment) - but they would have to register
you at ODFauthors for you to get at the pre-released version of the 4.2.x
version.

Regards from
Tom :)




On 9 March 2015 at 13:34, Ralf Kersanach <dmbralf@furg.br> wrote:

Hi Tom,

Well, I'm translating it to brazilian portuguese. I know that there is an
libreoffice site available for Brazil, but since my time is really limited,
I'd rather to it in my pace than on any time shedule. Anyway, thanks for
the
tip, I'll have a look at this international list and find out exactly what
"OmegaT" is.

At the moment I'm already through half of the introduction chapter.
Anyway, as
I said im my previous posting, I am very happy in finally finding a manual
that really explains Base in an updated software version. At moment I'm
using
the the TradutorOOoText extension. It has several pitfalls in translating
from
german to portuguese, but it's quite a help. It sounds that "OmegaT" is
more
professional for translations, so I'll contact them and see how I can help.

The reason why I'm starting the translation with Base is because I need to
build an database to mine some data out of DNA sequences. I was doing it
using
SQL statement with mysqlworkbench. It was nice, but I wanted to do a more
beautiful and user friendly layout and I am not prepared (due to lack of
time)
to learn an script and HTML languages just to build an GUI for this
database.
I searched a lot between possibilities which were similar to Filemaker
(I've
used it a lot before I changed to Opensource), and the two most friendly,
in
my opinion, where Base and Kexi.

Personally, I don't use the portuguese version of LO, I use the
english(UK)user interface, because of the help file which does not come
with
the (USA). For the locale setting I use portuguese (Brazil), well because
is
where I live.

Well, once more thanks for the tip.

On Monday 09 March 2015 11:22:55 you wrote:
Hi :)
The international translator's mailing list is just starting to
experiment
with translating the "Published Guides", such as the "Base Handbook",
using
"OmegaT".

OmegaT helps in many ways but just one of them is that it seems to track
(or identify) what has changed in a newer release of the same guide so
that
only the changes need to be translated to bring your translation
up-to-date.

I suspect that they will probably start with the "Getting Started with
LibreOffice" guide, then do the "Writer Guide", then the one for Calc and
then work through all the rest before ever getting to the Base one(s).

If you are alread working on translating the Base Handbook then you would
be a huge asset to the translation team of whichever language you are
working on.

There are a few teams that have worked on translating the guides but it
is
a struggle, especially until using a decent tool such as OmegaT.

The international translators mailing list address is;
L10n@Global.LibreOffice.org
(capital letters, upper-case and lower-case all get converted to just
lower-case by emailing systems so they are only useful for human readers
and it really doesn't matter if you get upper and lower case muddled up).

Regards from
Tom :)

On 6 March 2015 at 14:21, Ralf Kersanach <dmbralf@furg.br> wrote:
I guess Andreas is right in all his observations. I'll never expected
LO
or
similars to be an top Databse development front end (although if it
would
reach filemakers level would be nice). What I expect, as a non IT
person,
from
such kind of platform, is to help me out to delevelop relative simple
to
medium simple personal and sometimes professional problems without
having
to
learn several programming languages to achive the same through web
pages.
I
have some friends which simply gave up building such DB just because it
was to
cumberson to learn several different thinks to achieve one purpose
only.

I thing every tool is a right tool if we keep their limitation in mind
and
I
think Base is in the absolute right direction. After starting to read
the
4.4
manual, Tom pointed me out, I got over enthusiastic again, because I
saw
how
much progress the Base team has done (good work folks). I got so
enthusiastic
that I started to translate it to my native language (as soon I reach
some
chapter translated I'll make the drafts available).

I think that one of the major draw backs of Base and why people isn't
using it
is the lack of up to date manuals. There more up to date literature and
information is available more people can understand power and
limitations
of
base and how to employ it. I know there are some tutorials around, but
there
more there better so people can see what is possible to do with base. I
know
the develop and documentation team might be small for this herculean
work
but
as I said before "good job folks", the rest comes with time.

On Friday 06 March 2015 13:15:13 Andreas Säger wrote:
Am 05.03.2015 um 18:36 schrieb SOS:
1. I cannot use

2. LO Base is missing options

LibreOffice Base is not a database development platform. It is hardly
more than a bridge between databases and office documents. Yes,
there is
a limited set of form controls and yes, it comes with macro languages
anyway. The core functionality is built around the ODF standard.
Database connectivity is a *simple* give-away which can be used in
various ways, mainly to fill ODF documents with external data.
Filemaker and Access are a completely different category.

--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems?
http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more:
http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be
deleted


--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems?
http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be
deleted



-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.