Re: [libreoffice-l10n] How to define a dictionary for new language?

[Rimas Kudelis]

Hi,

2013.07.31 14:03, Tom Davies wrote:

Hi :)
I was wondering if the LibreOffice translators team could help Sergio Martino.  
Ubuntu translators might find the dictionary useful to if aff and dic 
file-types are usable.  My guess is that oxt is unique to LibreOffice so this 
is mostly for LibreOffice translators.


OXT is just an extension package format that LibreOffice inherited from 
OpenOffice.org. It's just a zip file with predefined internal 
file/folder hierarchy.



So, is it possible to "register" a 'new language', really a dialect spoken in 
the Bari area of Italy.  How do you get it to appear in the combo-box in the 
spelling-checker dialog?


I guess the problem Sergio's friend is facing could be related to 
https://bugs.freedesktop.org/show_bug.cgi?id=66341 . Right now, LibO 
only supports ll-CC locale identifiers for dictionaries, and all other 
identifiers are ignored. If the language code used for that dialect is 
different (e.g. it-IT@Bari), that could be the issue you've stumbled 
upon here.


Rimas

--
ubuntu-translators mailing list
ubuntu-translators@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators

Re: Tajik Language - Adding support for a new language

[Dmitrijs Ledkovs]

On 1 August 2013 13:30, Christian PERRIER  wrote:
> Quoting Victor Ibragimov (victor.ibragi...@gmail.com):
>
>> But how about Gnome and KDE? Recently, we did a great job for Gnome
>> https://l10n.gnome.org/languages/tg/gnome-3-10/ui/, but I still see
>> incomplete translations of those 100% files on Debian pages
>> http://www.debian.org/international/l10n/po/tg  . How often PO files
>> from the upstream are updated for Debian? Should I update those files
>> manually or it is done automatically at a certain time?
>
> It depends on several factors:
> 1) first of all, what is done in Launchpad has to go upstream
> 2) then, once upstream incorporates the translation in a new release,
> that new upstream release has to be packaged for Debian (and indeed
> Ubuntu as well).
>

Ubuntu specific packages should be translated in Launchpad, and
translations there are merged/imported from packages thus stuff that
tinkers into debian/upstream gets merged together.

Updating languages packs (translations) post-ubuntu release only
happens mostly via launchpad translations exports, so it's the
preffered way to update translations post-release. (think e.g. 12.04
LTS)


> Step 1) is something I don't really know how it's working and if even
> someone in the Canonical/Ubuntu/Launchpad world guarantuees it really
> happens.
>

Moving things upstream is well manual work. I know kubuntu team
closely forward / redirect translators to kde & generate kde
translation packs post-release.
At one time gnome translations were actively forwarded, not sure
who/where/what is coordinated at the moment.
For debian specific packages, e.g. d-i, DDs who work in Ubuntu
redirect translators to debian =) like I did for Tajik ;-)

> If it does, fine. If it doesn't, then work is partly lost.
>

I'd rather say is stuck in one distribution only (e.g. Ubuntu) and
degrades with time (bit rots...).

> This is precisely the reason for which, we (Debian i18n folks) do NOT
> encourage people to work on upstream translation in the downstream
> distributions.
>
> Translation of software has to be done with upstreams: KDE, Gnome,
> LibreOffice and (imho) not in distros.
>
> I know Launchpad/rosetta seems appealing, attractive, etc. But as long
> as nothing guarantees that localization work done there ends up in
> upstream projects (and then later in all distros : Debian, Fedora,
> RHEM, CentOS, etc.) I would not encourage anyone to work there *unless
> the upstream authors have chosen to use Launchpad as their development
> and localization framework*.
>

I like using rosetta as a translation repository. Since it imports all
strings from all projects known to launchpad, it offers many
translation suggestions. Surprisingly there are a lot of common
strings in all projects (New, Ok, Open, Save, Exit, etc.) such that
bulk of initial translations can be done very quickly with launchpad
suggestions. Then export it & take it up upstream.


> As a consequence, when it comes at Debian i18n, we only focus on
> things where Debian *is* the upstream: the installer, our native
> packages (dpkg, apt, debconf and dozens of others), our webpages, our
> communication material (such as Debian News), etc.
>
> What you mention about Gnome is probably because not all of Gnome 3.10
> is in Debian yet. Transitions for environments such as Gnome and KDE
> take a very significant time for packagers to work on them (for
> instance, KDE 4.10 just landed in Debian usntable) so that explains
> why it takes time for your l1n work to end up in the distribution.
>
>

Regards,

Dmitrijs.

-- 
ubuntu-translators mailing list
ubuntu-translators@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators

Re: Blueprint: Ubuntu Server Guide development (LTS only)

[John Kim]

Hi,

Although I don't run a server myself, I really like this idea. Sticking 
to stability saves us a lot of effort.


On 2013? 07? 16? 10:46, William Van Hevelingen wrote:

+1

I think this a great idea. I run all LTS servers and I often just look 
at the most recent serverguide for up to date stuff because the LTS 
one is usually missing 6+ months of fixes.


William

p.s

Any chance we can switch to Markdown or Restructed text? I've 
contributed a few times before and I would really appreciate it if I 
didn't have to work with XML.



On Tue, Jul 16, 2013 at 8:33 AM, Peter Matulis 
mailto:peter.matu...@canonical.com>> wrote:


Hi, I have created a blueprint [1] that affects the Ubuntu Server
Guide
development schedule.  After several years of observation both Doug
Smythies and I have decided it makes more sense to publish the
Guide for
LTS releases only.  There would be occasional (unofficial)
publications
of the current development branch (snapshots).  If this sounds to you
like the rolling release model you are correct, this is what we are
proposing.  Other changes include relaxing the string freeze and
translation schedules.  I hope to see you there.

peter matulis

[1]:

https://blueprints.launchpad.net/serverguide/+spec/community-1308-serverguide-development

--
ubuntu-server mailing list
ubuntu-ser...@lists.ubuntu.com 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam




--
Thanks,
William




--
John Kim
Ubuntu Doc & Ubuntu QA contributor
IRC: kotux
"Most folks are as happy as they make up their minds to be." -Abraham Lincoln

-- 
ubuntu-translators mailing list
ubuntu-translators@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators

Re: Blueprint: Ubuntu Server Guide development (LTS only)

[William Van Hevelingen]

+1

I think this a great idea. I run all LTS servers and I often just look at
the most recent serverguide for up to date stuff because the LTS one is
usually missing 6+ months of fixes.

William

p.s

Any chance we can switch to Markdown or Restructed text? I've contributed a
few times before and I would really appreciate it if I didn't have to work
with XML.


On Tue, Jul 16, 2013 at 8:33 AM, Peter Matulis
wrote:

> Hi, I have created a blueprint [1] that affects the Ubuntu Server Guide
> development schedule.  After several years of observation both Doug
> Smythies and I have decided it makes more sense to publish the Guide for
> LTS releases only.  There would be occasional (unofficial) publications
> of the current development branch (snapshots).  If this sounds to you
> like the rolling release model you are correct, this is what we are
> proposing.  Other changes include relaxing the string freeze and
> translation schedules.  I hope to see you there.
>
> peter matulis
>
> [1]:
>
> https://blueprints.launchpad.net/serverguide/+spec/community-1308-serverguide-development
>
> --
> ubuntu-server mailing list
> ubuntu-ser...@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam
>



-- 
Thanks,
William
-- 
ubuntu-translators mailing list
ubuntu-translators@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators

Re: Tajik Language - Adding support for a new language

[Christian PERRIER]

Quoting Victor Ibragimov (victor.ibragi...@gmail.com):

> But how about Gnome and KDE? Recently, we did a great job for Gnome
> https://l10n.gnome.org/languages/tg/gnome-3-10/ui/, but I still see
> incomplete translations of those 100% files on Debian pages
> http://www.debian.org/international/l10n/po/tg  . How often PO files
> from the upstream are updated for Debian? Should I update those files
> manually or it is done automatically at a certain time? 

It depends on several factors:
1) first of all, what is done in Launchpad has to go upstream
2) then, once upstream incorporates the translation in a new release,
that new upstream release has to be packaged for Debian (and indeed
Ubuntu as well).

Step 1) is something I don't really know how it's working and if even
someone in the Canonical/Ubuntu/Launchpad world guarantuees it really
happens.

If it does, fine. If it doesn't, then work is partly lost.

This is precisely the reason for which, we (Debian i18n folks) do NOT
encourage people to work on upstream translation in the downstream
distributions.

Translation of software has to be done with upstreams: KDE, Gnome,
LibreOffice and (imho) not in distros.

I know Launchpad/rosetta seems appealing, attractive, etc. But as long
as nothing guarantees that localization work done there ends up in
upstream projects (and then later in all distros : Debian, Fedora,
RHEM, CentOS, etc.) I would not encourage anyone to work there *unless
the upstream authors have chosen to use Launchpad as their development
and localization framework*.

As a consequence, when it comes at Debian i18n, we only focus on
things where Debian *is* the upstream: the installer, our native
packages (dpkg, apt, debconf and dozens of others), our webpages, our
communication material (such as Debian News), etc.

What you mention about Gnome is probably because not all of Gnome 3.10
is in Debian yet. Transitions for environments such as Gnome and KDE
take a very significant time for packagers to work on them (for
instance, KDE 4.10 just landed in Debian usntable) so that explains
why it takes time for your l1n work to end up in the distribution.




signature.asc
Description: Digital signature
-- 
ubuntu-translators mailing list
ubuntu-translators@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators

Re: Tajik Language - Adding support for a new language

[helix84]

On Thu, Aug 1, 2013 at 7:03 PM, Victor Ibragimov
 wrote:
> Could you please, send some more information about rosetta?

Rosetta is just the name of the translation software the Launchpad
website runs. You simply know it as "Launchpad".

Regards,
~~helix84

-- 
ubuntu-translators mailing list
ubuntu-translators@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators