translate-devel — translate.sourceforge.net development list

[Translate-devel] How do I extract tuv's prop nodes for ICE matches? (python)

[Manuel S. P. <ter...@gm...>]

Dear all,

I'm using translate toolkit in python to parse a tmx file with contains
OmegaT's alternative translations (called In-Context Exact translations in
common CAT tool jargon), e.g.

    <tu>
      <prop type="file">text1.txt</prop>
      <prop type="prev">Events or online activities organised by together.eu
</prop>
      <prop type="next">Contacting an MEP about an issue</prop>
      <tuv xml:lang="en">
        <seg>Petitions to the European Parliament</seg>
      </tuv>
      <tuv xml:lang="el" changeid="Reconciler" changedate="20210623T084913Z"
 creationid="Reconciler" creationdate="20210623T084913Z">
        <seg>Σε αιτήματα προς το Ευρωπαϊκό Κοινοβούλιο</seg>
      </tuv>
    </tu>

I can extract the source and the target segments but I can't find how I can
extract the prop nodes containing the context information about the match.

Is there an easy way to do this with translate toolkit or shall I use a
general xml parser?

My code is:

from translate.storage.tmx import tmxfile
with open("project_save.tmx", 'rb') as f:
    tm = tmxfile(f, 'en', 'el')

for tu in tm.unit_iter():
    print(tu.source, tu.target)

Thanks a lot.
Cheers, Manuel

Re: [Translate-devel] Virtaal -- Tag issues in Arabic

[F W. <fr...@tr...>]

Op Wo. 5 Feb. 2020 om 14:06 het Manuel Souto Pico <ter...@gm...>
geskryf:

> Dear all,
>
> There's an issue with tags (placeables) in RTL languages in Virtaal that I
> would like to report.
>
> To have the issue fixed or at least looked at, would it be useful to
> report it here, or shall I do it somewhere else?
>
> I just want to confirm before I spend time documenting the problem.
>

Hallo Manuel

In general, bugs are best tracked on the issue tracker on Github. Things
needing discussion might benefit from the expertise on the mailing list,
and I fear that RTL issues will likely be tricky to even get consensus on
what the right behaviour is. Additional practicalities are things like time
and platform limitations that might complicate these things.

All of that said, I'm not perfectly happy with the state of RTL support - I
can even guess what you might be referring to! The latest work on GTK3 also
as a regression or two in this area that I can't resolve yet. I don't think
Virtaal is necessarily much worse than other tools I have seen, but of
course, I have only "tested" it in RTL, not used it.

But feel free to mention the issues here or on Github as you want - we can
always move the discussion if required.

Keep well
Friedel

-- 
https://fwolff.net.za/

[Translate-devel] Virtaal -- Tag issues in Arabic

[Manuel S. P. <ter...@gm...>]

Dear all,

There's an issue with tags (placeables) in RTL languages in Virtaal that I
would like to report.

To have the issue fixed or at least looked at, would it be useful to report
it here, or shall I do it somewhere else?

I just want to confirm before I spend time documenting the problem.

Cheers, Manuel

Re: [Translate-devel] [ANN] Translate Toolkit 2.5.0 Final release

[Leandro R. <lea...@gm...>]

O dom., 19 de xan. de 2020 ás 05:33, Jean-Christophe Helary
(<jea...@tr...>) escribiu:
>
> It would be nice to have the whole documentation on one single (HTML or other) page.

Hi Jean-Cristophe,
Read The Docs is capable of generating it by using the link on the
pop-up in the corner. Here you have the link
https://readthedocs.org/projects/translate-toolkit/downloads/pdf/latest/


Bye,
Leandro Regueiro

>
> Jean-Christophe Helary
> -----------------------------------------------
> http://mac4translators.blogspot.com @brandelune
>
>
> > On Jan 19, 2020, at 2:35, Leandro Regueiro <lea...@gm...> wrote:
> >
> > Hi lists,
> > We are proud to announce the Translate Toolkit 2.5.0 release. This
> > release comes with some bugfixes and changes:
> >
> > - Fixes for multiple formats.
> > - Added support for Python 3.8. Python 2.7 is still supported.
> > - Added Sicilian language checks.
> >
> >
> > A full list of changes and new features is available in [1].
> >
> > You can download Translate Toolkit from [2]. Despite releasing a
> > stable product was one of our goals we might have missed anything, so
> > if you find any issue please report in [3] after checking it wasn't
> > reported earlier. We will try to do quick bugfix releases.
> >
> > If you need support please join [4] and for anything
> > development-related you can join [5].
> >
> >
> > Happy translating,
> > The Translate Toolkit team
> >
> > [1] http://docs.translatehouse.org/projects/translate-toolkit/en/latest/releases/2.5.0.html
> > [2] https://pypi.python.org/pypi/translate-toolkit/2.5.0
> > [3] https://github.com/translate/translate/issues/new
> > [4] https://gitter.im/translate/pootle
> > [5] https://gitter.im/translate/dev
>
>
>
> _______________________________________________
> Translate-devel mailing list
> Tra...@li...
> https://lists.sourceforge.net/lists/listinfo/translate-devel

Re: [Translate-devel] [ANN] Translate Toolkit 2.5.0 Final release

[Jean-Christophe H. <jea...@tr...>]

It would be nice to have the whole documentation on one single (HTML or other) page.


Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune


> On Jan 19, 2020, at 2:35, Leandro Regueiro <lea...@gm...> wrote:
> 
> Hi lists,
> We are proud to announce the Translate Toolkit 2.5.0 release. This
> release comes with some bugfixes and changes:
> 
> - Fixes for multiple formats.
> - Added support for Python 3.8. Python 2.7 is still supported.
> - Added Sicilian language checks.
> 
> 
> A full list of changes and new features is available in [1].
> 
> You can download Translate Toolkit from [2]. Despite releasing a
> stable product was one of our goals we might have missed anything, so
> if you find any issue please report in [3] after checking it wasn't
> reported earlier. We will try to do quick bugfix releases.
> 
> If you need support please join [4] and for anything
> development-related you can join [5].
> 
> 
> Happy translating,
> The Translate Toolkit team
> 
> [1] http://docs.translatehouse.org/projects/translate-toolkit/en/latest/releases/2.5.0.html
> [2] https://pypi.python.org/pypi/translate-toolkit/2.5.0
> [3] https://github.com/translate/translate/issues/new
> [4] https://gitter.im/translate/pootle
> [5] https://gitter.im/translate/dev

[Translate-devel] [ANN] Translate Toolkit 2.5.0 Final release

[Leandro R. <lea...@gm...>]

Hi lists,
We are proud to announce the Translate Toolkit 2.5.0 release. This
release comes with some bugfixes and changes:

- Fixes for multiple formats.
- Added support for Python 3.8. Python 2.7 is still supported.
- Added Sicilian language checks.


A full list of changes and new features is available in [1].

You can download Translate Toolkit from [2]. Despite releasing a
stable product was one of our goals we might have missed anything, so
if you find any issue please report in [3] after checking it wasn't
reported earlier. We will try to do quick bugfix releases.

If you need support please join [4] and for anything
development-related you can join [5].


Happy translating,
The Translate Toolkit team

[1] http://docs.translatehouse.org/projects/translate-toolkit/en/latest/releases/2.5.0.html
[2] https://pypi.python.org/pypi/translate-toolkit/2.5.0
[3] https://github.com/translate/translate/issues/new
[4] https://gitter.im/translate/pootle
[5] https://gitter.im/translate/dev

Re: [Translate-devel] News about Virtaal development

[F W. <fr...@tr...>]

Hi Michael

Are you referring to sentence segmentation that was discussed earlier
on this mailing list?

Friedel

2019-10-31 12:31 GMT+02:00, Michael Bauer <fi...@ak...>:
> That's great news!
>
> Any chance these changes might enable more efficient parsing of po files
> at punctuation as you'd expect, rather than keeping the sometimes
> massive chunks?
>
> Michael
>
> Sgrìobh F Wolff na leanas 31/10/2019 aig 05:46:
>> Hallo list
>>
>> For many years Virtaal development was going very slow, but that looks
>> like it might be changing!
>>
>> A big challenge facing the project in the last few years was that big
>> changes to the underlying platforms necessitated big changes to the
>> Virtaal code with very little benefit to users. I am happy to report
>> that we have a branch in git with the code mostly migrated to more up
>> to date platforms (the GObject introspection bindings, GTK3 and Python
>> 3). Many thanks to github user licamla that started this and thereby
>> inspired me to join the effort!
>>
>> A while ago I also reinstated the amagama API that Virtaal uses, so
>> even existing releases should have working Amagama translation memory
>> again. You can read more at my blog if you want:
>> https://fwolff.net.za/en/blog/
>>
>> The current work is in the "py3" branch. It is best tested with Python
>> 3.6 or higher and Gtk3. There are no installers available for any
>> platform at the moment.
>>
>> Now is a great time to test things and provide assistance to get this
>> to the next release. My time is limited, so I'm hoping there will be
>> more effort in helping to advance the state of the project.
>>
>> Hopefully I can give more news soon!
>>
>> Keep well
>> Friedel
>>
>>
>> --
>> https://fwolff.net.za/
>>
>>
>> _______________________________________________
>> Translate-devel mailing list
>> Tra...@li...
>> https://lists.sourceforge.net/lists/listinfo/translate-devel
>
> --
> *Akerbeltz <http://www.faclair.com/>*
> Goireasan Gàidhlig air an lìon
> Fòn: +44-141-946 4437
>
> *Tha Gàidhlig aig a' choimpiutair agad, siuthad, feuch e!*
> Iomadh rud eadar prògraman oifis, brabhsairean, predictive texting,
> geamannan is mòran a bharrachd. Tadhail oirnn aig www.iGàidhlig.net
> <http://www.iGaidhlig.net/>
>


-- 
https://fwolff.net.za/

Re: [Translate-devel] News about Virtaal development

[Michael B. <fi...@ak...>]

That's great news!

Any chance these changes might enable more efficient parsing of po files 
at punctuation as you'd expect, rather than keeping the sometimes 
massive chunks?

Michael

Sgrìobh F Wolff na leanas 31/10/2019 aig 05:46:
> Hallo list
>
> For many years Virtaal development was going very slow, but that looks 
> like it might be changing!
>
> A big challenge facing the project in the last few years was that big 
> changes to the underlying platforms necessitated big changes to the 
> Virtaal code with very little benefit to users. I am happy to report 
> that we have a branch in git with the code mostly migrated to more up 
> to date platforms (the GObject introspection bindings, GTK3 and Python 
> 3). Many thanks to github user licamla that started this and thereby 
> inspired me to join the effort!
>
> A while ago I also reinstated the amagama API that Virtaal uses, so 
> even existing releases should have working Amagama translation memory 
> again. You can read more at my blog if you want:
> https://fwolff.net.za/en/blog/
>
> The current work is in the "py3" branch. It is best tested with Python 
> 3.6 or higher and Gtk3. There are no installers available for any 
> platform at the moment.
>
> Now is a great time to test things and provide assistance to get this 
> to the next release. My time is limited, so I'm hoping there will be 
> more effort in helping to advance the state of the project.
>
> Hopefully I can give more news soon!
>
> Keep well
> Friedel
>
>
> -- 
> https://fwolff.net.za/
>
>
> _______________________________________________
> Translate-devel mailing list
> Tra...@li...
> https://lists.sourceforge.net/lists/listinfo/translate-devel

-- 
*Akerbeltz <http://www.faclair.com/>*
Goireasan Gàidhlig air an lìon
Fòn: +44-141-946 4437

*Tha Gàidhlig aig a' choimpiutair agad, siuthad, feuch e!*
Iomadh rud eadar prògraman oifis, brabhsairean, predictive texting,
geamannan is mòran a bharrachd. Tadhail oirnn aig www.iGàidhlig.net 
<http://www.iGaidhlig.net/>

[Translate-devel] News about Virtaal development

[F W. <fr...@tr...>]

Hallo list

For many years Virtaal development was going very slow, but that looks like
it might be changing!

A big challenge facing the project in the last few years was that big
changes to the underlying platforms necessitated big changes to the Virtaal
code with very little benefit to users. I am happy to report that we have a
branch in git with the code mostly migrated to more up to date platforms
(the GObject introspection bindings, GTK3 and Python 3). Many thanks to
github user licamla that started this and thereby inspired me to join the
effort!

A while ago I also reinstated the amagama API that Virtaal uses, so even
existing releases should have working Amagama translation memory again. You
can read more at my blog if you want:
https://fwolff.net.za/en/blog/

The current work is in the "py3" branch. It is best tested with Python 3.6
or higher and Gtk3. There are no installers available for any platform at
the moment.

Now is a great time to test things and provide assistance to get this to
the next release. My time is limited, so I'm hoping there will be more
effort in helping to advance the state of the project.

Hopefully I can give more news soon!

Keep well
Friedel


-- 
https://fwolff.net.za/

Re: [Translate-devel] Breaking up long segments

[Michael B. <fi...@ak...>]

Well, I posted not so much because I wanted to diss OmegaT but because - 
for specific reasons - I felt this would be a useful feature in Virtaal. 
The specific reason being that Virtaal wins hands down on out-of-the-box 
simplicity and is handy for FOSS po files. For anything else, I have 
access to Trados Studio and other industry standard tools. I am grateful 
you are trying to be helpful and point out all the options but OmegaT, 
certainly from where I'm coming, has neither the simplicity of Virtaal 
nor the power of Studio so just in order to get better parsing of po 
files, I am not going to switch to something I find really unwieldy.

> That's not the way it works. Files are not physically segmented in 
> OmegaT. OmegaT reads the files, extracts the translatable portions, 
> split that for display and translation, and uses the translation to 
> create files that are structurally equivalent to the original but with 
> the translated part.
Well, if OmegaT manages to extract the translatables AND parse them 
before presenting them for translation, it should be possible in Virtaal 
too, no?

Michael

-- 
*Akerbeltz <http://www.faclair.com/>*
Goireasan Gàidhlig air an lìon
Fòn: +44-141-946 4437
Facs: +44-141-945 2701

*Tha Gàidhlig aig a' choimpiutair agad, siuthad, feuch e!*
Iomadh rud eadar prògraman oifis, brabhsairean, predictive texting,
geamannan is mòran a bharrachd. Tadhail oirnn aig www.iGàidhlig.net 
<http://www.iGaidhlig.net/>

Re: [Translate-devel] Breaking up long segments

[Jean-Christophe H. <jea...@gm...>]

> On Apr 29, 2018, at 21:14, Michael Bauer <fi...@ak...> wrote:
> 
> Just gave it a whizz - yeah, exactly like that but inside Virtaal, at least as an option. I really don't like OmegaT to work it, I've given it a whizz so many times over the years and each time I end up pulling my hair ;)

Maybe you should try until you have no hair anymore, then then you can focus on actually using OmegaT :)

Really, there is nothing complex or weird about the way OmegaT works. You create an empty project (which is just a hierarchy of empty folder with 1 setting file) then you put the relevant files into the relevant folders (at least the source files in the source folder), then you reload the project.

OmegaT is not a translation "editor", it is a translation "integrated environment". That may be what looks unfamiliar about it, so if you have any question to help you get used to it, go ahead.

> Would the code from OmegaT port easily to Virtaal? Or could one run just the segmentation over po files from the command line?

That's not the way it works. Files are not physically segmented in OmegaT. OmegaT reads the files, extracts the translatable portions, split that for display and translation, and uses the translation to create files that are structurally equivalent to the original but with the translated part.

It would be nice to have have a number of FLOSS pro-tool for translation in general, but they simply don't exist. In terms of FLOSS, OmegaT and the Okapi Framework are what is best. I don't think there is any question about that.

Jean-Christophe 

> 
> Michael
> 
> Sgrìobh Jean-Christophe Helary na leanas 29/04/2018 aig 11:13:
>> OmegaT has default segmentation rules that are applied based on the source language.
>> When you translate files you either select to segment or to not segment them.
>> 
>> If you select to segment, the segmentation rules based segments are automatically created. If you do not, the segments are the file format "default", in the case of PO: "paragraph" (or msgid).
>> 
>> Jean-Christophe 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
> Translate-devel mailing list
> Tra...@li...
> https://lists.sourceforge.net/lists/listinfo/translate-devel

Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune

Re: [Translate-devel] Breaking up long segments

[Michael B. <fi...@ak...>]

Just gave it a whizz - yeah, exactly like that but inside Virtaal, at 
least as an option. I really don't like OmegaT to work it, I've given it 
a whizz so many times over the years and each time I end up pulling my 
hair ;)

Would the code from OmegaT port easily to Virtaal? Or could one run just 
the segmentation over po files from the command line?

Michael

Sgrìobh Jean-Christophe Helary na leanas 29/04/2018 aig 11:13:
> OmegaT has default segmentation rules that are applied based on the 
> source language.
> When you translate files you either select to segment or to not 
> segment them.
>
> If you select to segment, the segmentation rules based segments are 
> automatically created. If you do not, the segments are the file format 
> "default", in the case of PO: "paragraph" (or msgid).
>
> Jean-Christophe

Re: [Translate-devel] Breaking up long segments

[Jean-Christophe H. <jea...@gm...>]

> On Apr 29, 2018, at 18:46, Michael Bauer <fi...@ak...> wrote:
> 
> How did you manage to set up a segmentation rule that chops up po files?

OmegaT has default segmentation rules that are applied based on the source language.
When you translate files you either select to segment or to not segment them.

If you select to segment, the segmentation rules based segments are automatically created. If you do not, the segments are the file format "default", in the case of PO: "paragraph" (or msgid).

Jean-Christophe 


> 
> Michael
> 
> Sgrìobh Jean-Christophe Helary na leanas 29/04/2018 aig 00:43:
>> OmegaT, also free software, offers segmentation rules too. I use it all the time for PO work.
>> 
>> Jean-Christophe Helary
> 

Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune

Re: [Translate-devel] Breaking up long segments

[Michael B. <fi...@ak...>]

How did you manage to set up a segmentation rule that chops up po files?

Michael

Sgrìobh Jean-Christophe Helary na leanas 29/04/2018 aig 00:43:
> OmegaT, also free software, offers segmentation rules too. I use it 
> all the time for PO work.
>
> Jean-Christophe Helary

Re: [Translate-devel] Breaking up long segments

[Jean-Christophe H. <jea...@gm...>]

> On Apr 28, 2018, at 23:40, Michael Bauer <fi...@ak...> wrote:
> 
> i.e. break up these chunks wherever there is a . ! or ? and then before you upload the po, you run the reverse over it to stich them together again? It doesn't do it with po files but Trados Studio gives me the option of defining segmentation rules i.e. for instance, it allows me to tell it that I want it to treat \n as a segment break so it treats
> blablaa\nrhubarb
> as
> blabla
> \n
> rhubarb
> (i.e. three segments, you end up having to threat \n as a translatable once but that's easy enough.
> 
> Thoughts?

OmegaT, also free software, offers segmentation rules too. I use it all the time for PO work.

Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune

[Translate-devel] Breaking up long segments

[Michael B. <fi...@ak...>]

I don't know if this suggestions has been made before so I thought I'd 
make it anyway. By now, we have really good translation memories but the 
big spanner in the works is devs constantly pushing out huge chunks like 
this one:

#: activities/explore_monuments/resource/board/board6.qml:62
msgctxt "board6|"
msgid ""
"Red Pyramid was one of the finest and successful attempts by Pharaoh 
Sneferu"
" in building world’s first ever smooth sided pyramid during the Ancient "
"Egypt period. The height of the pyramid is 104 meters making it the 
world’s "
"4th largest pyramid in Egypt. The pyramid has been built with red 
limestone "
"stones and hence the name. The local people of Egypt called it as 
el-heram "
"el-watwaat meaning the Bat Pyramid."
msgstr ""

Given that it's almost impossible to re-educate devs on this (and it 
might even not be possible, technically), is there some magic step 
Virtaal could inject, purely for the purposes of translating locally 
that would create something like this:

#: activities/explore_monuments/resource/board/board6.qml:62(a)
msgctxt "board6|(a)"
msgid ""
"Red Pyramid was one of the finest and successful attempts by Pharaoh 
Sneferu"
" in building world’s first ever smooth sided pyramid during the Ancient "
"Egypt period."
msgstr ""

#: activities/explore_monuments/resource/board/board6.qml:62(b)
msgctxt "board6|(b)"
msgid ""
"The height of the pyramid is 104 meters making it the world’s "
"4th largest pyramid in Egypt.
msgstr ""

#: activities/explore_monuments/resource/board/board6.qml:62(c)
msgctxt "board6|(c)"
msgid ""
"The pyramid has been built with red limestone "
"stones and hence the name.
msgstr ""

i.e. break up these chunks wherever there is a . ! or ? and then before 
you upload the po, you run the reverse over it to stich them together 
again? It doesn't do it with po files but Trados Studio gives me the 
option of defining segmentation rules i.e. for instance, it allows me to 
tell it that I want it to treat \n as a segment break so it treats
blablaa\nrhubarb
as
blabla
\n
rhubarb
(i.e. three segments, you end up having to threat \n as a translatable 
once but that's easy enough.

Thoughts?

Michael

[Translate-devel] [ANN] Translate Toolkit 2.3.0 Final release

[Leandro R. <lea...@gm...>]

Hi lists,
We are proud to announce the Translate Toolkit 2.3.0 release. This
release comes with some bugfixes and changes:

- Full rewrite of the PHP format greatly extending the support.
- Added YAML format converters.
- Major refactor of converters code.

A full list of changes and new features is available in [1].

You can download Translate Toolkit from [2]. Despite releasing a
stable product was one of our goals we might have missed anything, so
if you find any issue please report in [3] after checking it wasn't
reported earlier. We will try to do quick bugfix releases.

If you need support please join [4] and for anything
development-related you can join [5].


Happy translating,
The Translate Toolkit team

[1] http://docs.translatehouse.org/projects/translate-toolkit/en/latest/releases/2.3.0.html
[2] https://pypi.python.org/pypi/translate-toolkit/2.3.0
[3] https://github.com/translate/translate/issues/new
[4] https://gitter.im/translate/pootle
[5] https://gitter.im/translate/dev

Re: [Translate-devel] Virtaal translate contribution project

[Leandro R. <lea...@gm...>]

On Tue, Oct 10, 2017 at 1:09 PM, Sara Beneito Satorres <
sar...@e-...> wrote:

> Hi,
>
> We are a group of several translators who would like to start contributing
> with a new translation of the CAT tool Virtaal.
>
> Our intention is to translate it into Catalan.
>
> Could you please check for us if Virtaal has already been translated into
> Catalan?
>

Hi,
it seems that Virtaal is already being translated:
https://pootle.locamotion.org/ca/pootle/

I suggest you get in touch with Softcatalà: https://www.softcatala.org/


Thanks



> Any information or help from your part, shall be appreciated.
>
> Looking forward to your reply.
>
> Thank you.
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Libre
> de virus. www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> <#m_4000128611279332719_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Translate-devel mailing list
> Tra...@li...
> https://lists.sourceforge.net/lists/listinfo/translate-devel
>
>

[Translate-devel] Virtaal translate contribution project

[Sara B. S. <sar...@e-...>]

Hi,

We are a group of several translators who would like to start contributing
with a new translation of the CAT tool Virtaal.

Our intention is to translate it into Catalan.

Could you please check for us if Virtaal has already been translated into
Catalan?

Any information or help from your part, shall be appreciated.

Looking forward to your reply.

Thank you.


<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Libre
de virus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

[Translate-devel] [ANN] Pootle 2.8.2 bugfix release

[Leandro R. <lea...@gm...>]

Hi,
Pootle 2.8.2 bugfix release is out! We strongly recommend to upgrade to it.

This release comes with the following changes:

- Bugfix for deployments without git command.
- UI language discovery tries simpler language codes before falling
back to default.
- Improved documentation.

Please read first the instructions on Installation [1] or Upgrading
[2] before proceeding, depending in your case, and it is also highly
advisable to check out the full list of changes [3]. Pootle package is
available on PyPI [4].

For support please join [5] and for anything development related you
can join [6]. If you find any issue please report in [7] after
ensuring it wasn't reported earlier.


Happy translating,
The Pootle team

[1] http://docs.translatehouse.org/projects/pootle/en/latest/server/installation.html
[2] http://docs.translatehouse.org/projects/pootle/en/latest/server/upgrading.html
[3] http://docs.translatehouse.org/projects/pootle/en/latest/releases/2.8.2.html
[4] https://pypi.python.org/pypi/Pootle/2.8.2
[5] https://gitter.im/translate/pootle
[6] https://gitter.im/translate/dev
[7] https://github.com/translate/pootle/issues

[Translate-devel] [ANN] Pootle 2.9.0rc1 candidate release

[Leandro R. <lea...@gm...>]

Hi,
Pootle 2.9.0rc1 is here. We are very close to the final release. This
release comes with:

- Stabler Pootle FS:
  - Pootle FS by default - update_stores and sync_stores remain for
backward compatibility but they will be running using Pootle FS.
  - Improved bi-directional merging of conflicting changes in both
database and disk.
- Bugfixes in serialization, internationalization and the editor.
- Performance boost in permissions forms.
- Major review of documentation.


We will be very grateful if people would help us by testing. If you
find any issue please report in [1] after ensuring it wasn't reported
earlier.

Please read first the instructions on Installation [2] or Upgrading
[3] before proceeding, depending in your case, and it is also highly
advisable to check out the full list of changes [4]. Pootle package is
available on PyPI [5].

For support please join [6] and for anything development related you
can join [7].


Happy translating,
The Pootle team

[1] https://github.com/translate/pootle/issues
[2] http://docs.translatehouse.org/projects/pootle/en/latest/server/installation.html
[3] http://docs.translatehouse.org/projects/pootle/en/latest/server/upgrading.html
[4] http://docs.translatehouse.org/projects/pootle/en/latest/releases/2.9.0.html
[5] https://pypi.python.org/pypi/Pootle/2.9.0rc1
[6] https://gitter.im/translate/pootle
[7] https://gitter.im/translate/dev

[Translate-devel] [ANN] Pootle 2.9.0b4 beta release

[Leandro R. <lea...@gm...>]

Hi,
Pootle 2.9.0b4 is here. We are getting closer to the RC. This release
comes with:

- Stabler Pootle FS:
  - Pootle FS by default - update_stores and sync_stores remain for
backward compatibility but they will be running using Pootle FS.
  - Improved bi-directional merging of conflicting changes in both
database and disk.
- Bugfixes in serialization, internationalization and the editor.
- Performance boost in permissions forms.
- Major review of documentation.


We will be very grateful if people would help us by testing. If you
find any issue please report in [1] after ensuring it wasn't reported
earlier.

Please read first the instructions on Installation [2] or Upgrading
[3] before proceeding, depending in your case, and it is also highly
advisable to check out the full list of changes [4]. Pootle package is
available on PyPI [5].

For support please join [6] and for anything development related you
can join [7].


Happy translating,
The Pootle team

[1] https://github.com/translate/pootle/issues
[2] http://docs.translatehouse.org/projects/pootle/en/latest/server/installation.html
[3] http://docs.translatehouse.org/projects/pootle/en/latest/server/upgrading.html
[4] http://docs.translatehouse.org/projects/pootle/en/latest/releases/2.9.0.html
[5] https://pypi.python.org/pypi/Pootle/2.9.0b4
[6] https://gitter.im/translate/pootle
[7] https://gitter.im/translate/dev

[Translate-devel] [ANN] Pootle 2.9.0b3 beta release

[Leandro R. <lea...@gm...>]

Hi,
Pootle 2.9.0b3 is here, coming with:

- Even more stable Pootle FS
- Improved bi-directional merging of conflicting changes in both
database and disk
- Pootle FS by default - update_stores and sync_stores remain for
backward compatibility but they will be running using Pootle FS.
- Bugfixes in serialization and internationalization


We will be very grateful if people would help us by testing. If you
find any issue please report in [1] after ensuring it wasn't reported
earlier.

Please read first the instructions on Installation [2] or Upgrading
[3] before proceeding, depending in your case, and it is also highly
advisable to check out the full list of changes [4]. Pootle package is
available on PyPI [5].

For support please join [6] and for anything development related you
can join [7].


Happy translating,
The Pootle team

[1] https://github.com/translate/pootle/issues
[2] http://docs.translatehouse.org/projects/pootle/en/latest/server/installation.html
[3] http://docs.translatehouse.org/projects/pootle/en/latest/server/upgrading.html
[4] http://docs.translatehouse.org/projects/pootle/en/latest/releases/2.9.0.html
[5] https://pypi.python.org/pypi/Pootle/2.9.0b3
[6] https://gitter.im/translate/pootle
[7] https://gitter.im/translate/dev

[Translate-devel] [ANN] Pootle 2.9.0b2 beta release

[Leandro R. <lea...@gm...>]

Hi,
Pootle 2.9.0b2 is out:

- More stable Pootle FS
- Pootle FS by default - we’ve moved away from update_stores and
sync_stores, while these remain for backward compatibility they’ll be
running using Pootle FS.
- Bugfixes in serialization


We will be very grateful if people would help us by testing. If you
find any issue please report in [1] after ensuring it wasn't reported
earlier.

Please read first the instructions on Installation [2] or Upgrading
[3] before proceeding, depending in your case, and it is also highly
advisable to check out the full list of changes [4]. Pootle package is
available on PyPI [5].

For support please join [6] and for anything development related you
can join [7].


Happy translating,
The Pootle team

[1] https://github.com/translate/pootle/issues
[2] http://docs.translatehouse.org/projects/pootle/en/latest/server/installation.html
[3] http://docs.translatehouse.org/projects/pootle/en/latest/server/upgrading.html
[4] http://docs.translatehouse.org/projects/pootle/en/latest/releases/2.9.0.html
[5] https://pypi.python.org/pypi/Pootle/2.9.0b2
[6] https://gitter.im/translate/pootle
[7] https://gitter.im/translate/dev

[Translate-devel] [ANN] Translate Toolkit 2.2.5 Final release

[Leandro R. <lea...@gm...>]

Hi lists,
We are proud to announce the Translate Toolkit 2.2.5 release. This
release comes with some bugfixes and changes:

- Added support for i18next JSON dialect.
- Improved WebExtension JSON dialect support.
- Bugfix for XLIFF format.

A full list of changes and new features is available in [1].

You can download Translate Toolkit from [2]. Despite releasing a
stable product was one of our goals we might have missed anything, so
if you find any issue please report in [3] after checking it wasn't
reported earlier. We will try to do quick bugfix releases.

If you need support please join [4] and for anything
development-related you can join [5].


Happy translating,
The Translate Toolkit team

[1] http://docs.translatehouse.org/projects/translate-toolkit/en/latest/releases/2.2.5.html
[2] https://pypi.python.org/pypi/translate-toolkit/2.2.5
[3] https://github.com/translate/translate/issues/new
[4] https://gitter.im/translate/pootle
[5] https://gitter.im/translate/dev