<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.misc.translate.devel">
    <title>gmane.comp.misc.translate.devel</title>
    <link>http://blog.gmane.org/gmane.comp.misc.translate.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.misc.translate.devel/2660"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.misc.translate.devel/2644"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.misc.translate.devel/2643"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.misc.translate.devel/2642"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.misc.translate.devel/2636"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.misc.translate.devel/2630"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.misc.translate.devel/2629"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.misc.translate.devel/2627"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.misc.translate.devel/2622"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.misc.translate.devel/2615"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.misc.translate.devel/2610"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.misc.translate.devel/2607"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.misc.translate.devel/2606"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.misc.translate.devel/2604"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.misc.translate.devel/2603"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.misc.translate.devel/2600"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.misc.translate.devel/2597"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.misc.translate.devel/2597"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.misc.translate.devel/2590"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.misc.translate.devel/2589"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2660">
    <title>Deprecations</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2660</link>
    <description>&lt;pre&gt;Hallo everybody

Several of the products have been enjoying some code cleanups, and I
think it is time to raise the topic of deprecating some older features.

I'm often one to hold onto old features, because I don't want to take
anything away from anybody, but here are a few things that I'm thinking
of that can improve things. I'd like to hear other people's opinions.
Please reply where you have an opinion or where you might be impacted.

A related topic might be to raise our required versions for our
dependencies, but there aren't any specific ones that come to mind,
except that we had to raise the requirement for Django to version 1.2
for the upcoming version of Pootle.


So these are some suggestions for removal:


  - Old .ts format converter to PO.  We got a bug report today about
lack of support for some features in ts2po. Since Pootle and Virtaal
supports .ts files natively, the converter didn't get much attention
again. I'd actually like for someone to write a basic converter that
uses the new TS support we have (ts2.py) - it should be a fairly basic
converter, I think. Anybody interested?


  - Symbian, Trados, Tikiwiki support. I'm not sure what the state of
these converters are, and how many people use these. Maybe I just
haven't heard people discussing/using this, so I'm happy to keep them if
they work well and other people can maintain them well. Documentation
and test cases are more than welcome, of course.


  - Windows .rc.  I think the Wine project might have been interested in
this, but I almost think they now use their own converter.  There have
been bug reports with regards to this, although I guess it worked for
several cases, especially in the Wine project.


  - phppo2pypo.  I think this was part of a big once-off migration
inside Mozilla between two uses of the PO format. I have a suspicion
this kind of thing can actually be useful to other people , but I doubt
anybody will find it. Ideas?


  - Old KDE style comments. Who stil remembers these?  They looked
something like this:

msgid ""
"_: Noun\n"
"convert"
msgstr ""

That was the solution to disambiguate otherwise identical source strings
before msgctxt was introduced in gettext.  We already removed it as a
choice for the --duplicates option from the converters in Translate
Toolkit some time ago, and I doubt that anybody is still using this. 

One of the reasons I want to let go of this is that it will bring a
slight simplification and speedup in our PO parsing. Probably not a big
difference, but it would be nice to get rid of something if it is not
useful.

That said, I know some projects still use custom context markers (the
Battle for Wesnoth comes to mind). We don't support it at the moment,
but it would be useful to do so, of course, since it affects TM, quality
checks, etc. if the source text is not clean.


  - "mozfunny" formats.  This strangely named module provided support
for .inc and .it files in the Mozilla project. Are they still used?


Any others we should be discussing?

Friedel

&lt;/pre&gt;</description>
    <dc:creator>F Wolff</dc:creator>
    <dc:date>2012-05-24T13:30:19</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2644">
    <title>Are Virtaal tutorial hints translatable?</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2644</link>
    <description>&lt;pre&gt;Hi,
when I was playing this morning with Virtaal I noticed that the
Virtaal tutorial hints doesn't appear in the Virtaal interface
language. Are Virtaal tutorial hints translatable?

Bye

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Leandro Regueiro</dc:creator>
    <dc:date>2012-05-10T16:18:19</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2643">
    <title>Virtaal documentation</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2643</link>
    <description>&lt;pre&gt;Hi,
this morning I was playing with Virtaal and I realized that the
installed version I have (.deb package) doesn't provide any local
documentation. I don't know if the packages for other operating
systems include the docs, but for people like me who don't have an
Internet connection at home it is really necessary to have local docs.

Bye

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Leandro Regueiro</dc:creator>
    <dc:date>2012-05-10T16:13:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2642">
    <title>About Virtaal tutorial</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2642</link>
    <description>&lt;pre&gt;Hi,
this morning I played a little to try some of the things that the
Traditori magazine article told. I noticed that the tutorial doesn't
talk about some key features like the terminology handling, the spell
checking or the accelerators (the accelerators in the translations,
not Virtaal ones). Maybe this omissions are due to me having a
relatively old version of Virtaal (0.7.0), but if the development
version tutorial has this flaws I suggest you to include some new
entries in the tutorial to address this particular issues.

Bye

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Leandro Regueiro</dc:creator>
    <dc:date>2012-05-10T16:08:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2636">
    <title>Uploaded toolkit 1.9.0 on Pypi</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2636</link>
    <description>&lt;pre&gt;Hi,

I just uploaded the 1.9.0 version of the Translate Toolkit to Pypi:
http://pypi.python.org/pypi/Translate%20Toolkit/1.9.0

I had to struggle to upload it, until i changed "translate-toolkit" to
"Translate Toolkit" in setup.py in standardsetup("Translate Toolkit",
translateversion).
But then I had to delete and reupload the tar.gz with
"translate-toolkit" in the file name. I guess the problem is that the
package name should be translate-toolkit in the first place on Pypi,
Translate Toolkit being the pretty (display) name.
Should I open a ticket on Pypi bug tracker for that?

Claude
&lt;/pre&gt;</description>
    <dc:creator>Claude Paroz</dc:creator>
    <dc:date>2012-05-08T20:44:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2630">
    <title>Korean input problem in Virtaal</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2630</link>
    <description>&lt;pre&gt;Hi, all.
I found a problem of puting korean in Virtaal.
Watch this video. It would be easier to understand the problem.
http://youtu.be/S-edmYJJK_I

The original text is "Go to %s page"
and Translation is "%s 페이지로 이동"
However when I typed "페이지", it remained only "페지". "이" was missed.
"이" consists of "ㅇ"+"ㅣ", so two letters missed.

and it happened to "이동". It was supposed be "이동", but there is only "이ㅇ".
Also two letters was missed. "ㄷ" and "ㅗ"

please check this out.
Thanks.

&lt;/pre&gt;</description>
    <dc:creator>Jihui Choi</dc:creator>
    <dc:date>2012-04-27T20:32:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2629">
    <title>Batch version control operations in Pootle</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2629</link>
    <description>&lt;pre&gt;Hi everybody

People have sometimes asked for the possibility to do things like
project-wide updates or commits to version control. Stuart Prescott
developed two manage.py commands that can be used to achieve this, and I
committed it in git with a few changes.

This was the bug report:

http://bugs.locamotion.org/show_bug.cgi?id=1491

The original versions that he posted should work fine in Pootle 2.1
(maybe even 2.0!) if copied into
    local_apps/pootle_app/management/commands

The committed version needed a change to Pootle, so the versions in git
won't work as-is with released versions of Pootle, but do mostly the
same thing.

It would be great if interested people can try it out or give their
feedback. Hopefully we see this in Pootle 2.2!

Keep well
Friedel



&lt;/pre&gt;</description>
    <dc:creator>F Wolff</dc:creator>
    <dc:date>2012-04-18T10:04:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2627">
    <title>Copying extracted comments with po2csv</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2627</link>
    <description>&lt;pre&gt;Hello All,

First I hope that I'm sending these questions to the right place, and if I'm not I apologize.

Second, a bit of background.  I'm working on an embedded project that uses a PIC32 micro and the po2c system to produce localization for our GUI.  The system that I'm working on has a small GUI (480x272) and some rather severe constraints on the length and formatting of messages.  I have added Translator comments to all of the strings that need to be translated.

The people that we are using to do our translations don't seem to be able to use the tools that support .po files so I need to convert to .csv files for them, but I need to keep the extracted comments to tell the translator what the constraints are for each message.

I'm not a Python programmer so I may be a bit confused about the workings of the Translate Toolkit.  In doing a quick browse of the code used in the po2csv &amp;amp; csv2po converters I see that both the po &amp;amp; csv storage utilities support the extracted comments but the po2csv converter doesn't copy them.  I'm wondering what the issues are in transferring the extracted comments to the csv file from the po file?

Thanks in advance for any clarifications anyone can provide,

Greg Wilson-Lindberg
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Translate-devel mailing list
Translate-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/translate-devel
&lt;/pre&gt;</description>
    <dc:creator>Greg Wilson-Lindberg</dc:creator>
    <dc:date>2012-04-09T17:49:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2622">
    <title>API docs updated</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2622</link>
    <description>&lt;pre&gt;Hello,

The API docs for the Translate Toolkit have received a big update.

We have converted the source docstrings from epytext to
reStructuredText, thus moving off the unmaintained Epydoc[1] to the
widely used Sphinx[2].

The new API docs are available online at ReadTheDocs:
http://readthedocs.org/docs/translate-toolkit/en/latest/api/

The docs are rebuilt after each commit so this means they will always
be up-to-date.

For now we have only moved the API docs but the general idea is to
move everything there.

As always, feedback and patches are more than welcome.


[1] http://epydoc.sourceforge.net/
[2] http://sphinx.pocoo.org/

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
&lt;/pre&gt;</description>
    <dc:creator>Julen Ruiz Aizpuru</dc:creator>
    <dc:date>2012-04-03T23:15:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2615">
    <title>Modifying web2py2po</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2615</link>
    <description>&lt;pre&gt;Hi,

I am working on a project at sahana-eden[1] which uses
translate-toolkit for it's translation process. Currently the py file
generated by the system contains only the source string and target
string. I am to modify the system so that the py file contains more
info such as file name, line number, source string, traget string,
comments for translator etc. With all those info in the py file,
web2py2po won't be able to generate the po file from that. So is it
possible to define a format and get it converted to a po file?

[1] http://eden.sahanafoundation.org/

&lt;/pre&gt;</description>
    <dc:creator>Kalpa Welivitigoda</dc:creator>
    <dc:date>2012-03-22T06:28:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2610">
    <title>Language Identification</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2610</link>
    <description>&lt;pre&gt;Following up on:

http://bloc.eurion.net/archives/2010/language-identification-and-free-software/

"""
F Wolff says:
September 27, 2010 at 10:32
We already implemented our own Python code based on the n-gram
technique in the Translate Toolkit, which is currently used by Virtaal
to help users do language selection. You can see the code here:
http://translate.svn.sourceforge.net/viewvc/translate/src/trunk/translate/lang/ngram.py
http://translate.svn.sourceforge.net/viewvc/translate/src/trunk/translate/lang/identify.py

It is based on a toy Python implementation we found at the time.

Please work with us to make the best Python language detection
available. Our code works well, but the models aren’t great, and there
are some languages it struggles to identify at the moment. We tried to
remove some of the incorrect models from our copy to try to improve
the quality. Let me know if you want to discuss some possibilities for
reuse/factoring out.

"""

I would like to factor the language detection out into a separate package.

Background: language detection is useful in many use cases. The existing
packages on Pypi are not up to par with your implementation.
I need e.g. to detect the language of a document uploaded to a CMS
(editors just do not put in the metadata)

Proposal:
1) implement language detection as is into an independent package which can
be installed from pypi with easy_install or pip

2) add Bigram language detection: this is useful as many languages can be
a) identified on Bigrams alone or b) to get a narrowed down choice of languages
to be processed by trigrams

e.g. 'bork bork' would be narrowed down to (maybe) some European languages
to determine the language more accurately it does not have to be compared to the
trigrams of say Russian or Chinese.


Please let me know what you think and if you prefer a locations (e.g your svn)


&lt;/pre&gt;</description>
    <dc:creator>Christian Ledermann</dc:creator>
    <dc:date>2012-03-13T14:06:19</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2607">
    <title>Pootle feature request</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2607</link>
    <description>&lt;pre&gt;Hi there,

   I am new to the list. I am primarily a C coder for the WINE project 
however we have recently switched to PO files for our translation needs. 
I administrate a very simple pootle install for a different project and 
was advocating for pootle for WINE's translation needs, however there is 
a snag.

   Wine requires that all changes made be attributed directly to the 
person making the change. Which means that we would need a way for 
pootle to track each translation and be able to attribute it directly to 
the person who made it.  Then either we would need pootle to be able to 
either generate diff patches from the original containing each 
translators changes, or push git commits again attributed to each 
translator.

   I have started looking at the pootle code, however I will freely 
admit my python skills are in their infancy. I was hoping a more 
seasoned pootle developer could give me some insight into if this is 
possible already, planned, or going to be super hard.

thanks!
-aric

------------------------------------------------------------------------------
Virtualization &amp;amp; Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
&lt;/pre&gt;</description>
    <dc:creator>Aric Stewart</dc:creator>
    <dc:date>2012-02-22T14:09:19</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2606">
    <title>New Virtaal 0.7.1 dmg for Mac</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2606</link>
    <description>&lt;pre&gt;
I've built a new Virtaal 0.7.1 package for Mac:
http://sourceforge.net/projects/translate/files/Virtaal/0.7.1/Virtaal-0.7.1-Mac-Beta-2.dmg

This fixes these issues:
* Can't open XML file formats e.g. TMX and XLIFF: we now reference the 
packaged lxml correctly.
* Native dialogs crash on Lion.  Reverted to using GTK dialogs until we 
can work out how to fix this.

&lt;/pre&gt;</description>
    <dc:creator>Dwayne Bailey</dc:creator>
    <dc:date>2012-02-10T17:12:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2604">
    <title>po2prop issue</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2604</link>
    <description>&lt;pre&gt;Hi All,

I've run into an issue with the 'po2prop' tool.  Is this the best place to
report a (possible) bug?

Thanks,
Patrick
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d_______________________________________________
Translate-devel mailing list
Translate-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/translate-devel
&lt;/pre&gt;</description>
    <dc:creator>Patrick Tuckey</dc:creator>
    <dc:date>2012-02-08T01:16:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2603">
    <title>Survey about the usability of Virtaal</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2603</link>
    <description>&lt;pre&gt;
Hallo everybody

A student at the University of Mainz in Germany, Almana Mukabenova, is
doing some research on the usability of Virtaal. She prepared a
questionnaire for the purposes of her master's thesis:

https://www.surveymonkey.com/s/NV9YFJR

I'm very interested to see what comes out of this, and want to encourage
all users of Virtaal (past and present, serious and casual) to take part
if they can.

Keep well
Friedel

&lt;/pre&gt;</description>
    <dc:creator>F Wolff</dc:creator>
    <dc:date>2012-02-02T14:36:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2600">
    <title>Virtaal 0.7.1 on Mac OS X</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2600</link>
    <description>&lt;pre&gt;
I've just uploaded Mac builds for Virtaal 0.7.1

Get it here:
http://sourceforge.net/projects/translate/files/Virtaal/0.7.1/Virtaal-0.7.1-Mac-Beta-1.dmg

Big improvements:
* We are now using CoreText.  Which in laymans terms means that RTL e.g. 
Arabic and CTL e.g. Japanese will render correctly.

Major issues:
* Input methods.  For languages that need their own special input 
methods we can't support them.  So Latin languages = yes, others = most 
likely no.  There are some promising patches that implement an input 
method for Mac in GTK, this would then use native Mac input methods.

Other minor things:
* Still haven't got native spell checking to work
* The translation state widget sometimes gets corrupted
* Native dialogs will sometimes cause Virtaal to crash

&lt;/pre&gt;</description>
    <dc:creator>Dwayne Bailey</dc:creator>
    <dc:date>2012-02-01T13:33:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2597">
    <title>Virtaal 0.7.1 released</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2597</link>
    <description>&lt;pre&gt;
Today the Translate team released version 0.7.1 of Virtaal. Virtaal is
an advanced program with features to help translators increase
translation quality and have fun.

This is a bugfix release, with one new feature (Drag and Drop support)
that came as the simplest way to solve a bug. Please forward this to
people who might be interested. This release is another good step
forward for the project.


Highlights
==========

 - New and updated translations
 - The Windows setup file now has a Galician translation for Innosetup
 - Support for Drag and Drop into the Virtaal window (bug 1955)
 - Improvements to the Moses machine translation plugin
 - Search highlighting sometimes incorrect (bug 1944)
 - Some improvements towards fixing bug 1789 (also search highlighting)
 - Some performance improvements (search and startup time)
 - Reduced memory use in long sessions
 - Support for non-ASCII installation paths
 - Support for non-ASCII usernames (bug 2000) [reported by Zbyněk
Schwarz]


The Windows build also includes some unreleased improvements in the
Toolkit:
 - Better XML tags test (bug 1971) [Seb M]
 - Improvements to the Mozilla quality checks
 - Corrected plural form for Scottish Gaelic [reported by Michael Bauer]



The user manual is an excellent way to learn how Virtaal can help you:
http://translate.sourceforge.net/wiki/virtaal/using_virtaal

Full feature list
http://translate.sourceforge.net/wiki/virtaal/features

Download:
http://sourceforge.net/projects/translate/files/Virtaal/
(Linux users need Translate Toolkit 1.9)

Bugs:
http://bugs.locamotion.org/


Happy translating!
The Translate Team






------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Translate-devel mailing list
Translate-devel&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-devel
&lt;/pre&gt;</description>
    <dc:creator>F Wolff</dc:creator>
    <dc:date>2012-01-10T08:53:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2597">
    <title>Virtaal 0.7.1 released</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2597</link>
    <description>&lt;pre&gt;
Today the Translate team released version 0.7.1 of Virtaal. Virtaal is
an advanced program with features to help translators increase
translation quality and have fun.

This is a bugfix release, with one new feature (Drag and Drop support)
that came as the simplest way to solve a bug. Please forward this to
people who might be interested. This release is another good step
forward for the project.


Highlights
==========

 - New and updated translations
 - The Windows setup file now has a Galician translation for Innosetup
 - Support for Drag and Drop into the Virtaal window (bug 1955)
 - Improvements to the Moses machine translation plugin
 - Search highlighting sometimes incorrect (bug 1944)
 - Some improvements towards fixing bug 1789 (also search highlighting)
 - Some performance improvements (search and startup time)
 - Reduced memory use in long sessions
 - Support for non-ASCII installation paths
 - Support for non-ASCII usernames (bug 2000) [reported by Zbyněk
Schwarz]


The Windows build also includes some unreleased improvements in the
Toolkit:
 - Better XML tags test (bug 1971) [Seb M]
 - Improvements to the Mozilla quality checks
 - Corrected plural form for Scottish Gaelic [reported by Michael Bauer]



The user manual is an excellent way to learn how Virtaal can help you:
http://translate.sourceforge.net/wiki/virtaal/using_virtaal

Full feature list
http://translate.sourceforge.net/wiki/virtaal/features

Download:
http://sourceforge.net/projects/translate/files/Virtaal/
(Linux users need Translate Toolkit 1.9)

Bugs:
http://bugs.locamotion.org/


Happy translating!
The Translate Team






------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Translate-devel mailing list
Translate-devel&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-devel
&lt;/pre&gt;</description>
    <dc:creator>F Wolff</dc:creator>
    <dc:date>2012-01-10T08:53:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2590">
    <title>Bugs on translate-toolkit, virtaal and mailman</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2590</link>
    <description>&lt;pre&gt;Hi, i have problems with translate-toolkit, virtaal and mailman. I
have reported first two bugs but get no attention. May be this mailing
list is more active. Let's, i try to define my problems:

I'm an Archlinux user and a turkish translator. My locale is
tr_TR.UTF8. and that is the source of my problems. I have compiled
virtaal from source without any extra options. Also all dependencies
are installed from official Archlinux repositories and when i checeked
them i see that those dependency packages created without any patches
or special compile time options. So, those packages are safe to use.

ERROR 1: When i tried to install virtaal i hit this bug:
http://bugs.locamotion.org/show_bug.cgi?id=2072 Virtaal simply refused
to install complaining about ASCII. I go further and found that it is
a lxml bug (see: https://bugs.launchpad.net/lxml/+bug/899066 ) Lxml
developers fixed that issue and committed to lxml git. I have compiled
lxml from git and installed,

ERROR 2: Than i again tried to install virtaal and this time virtaal
complained about sqlite3 not found error; although it is installed
properly and python2 interpereter can import it. See:
http://pastebin.com/ydBGGEwL
                Also --nodepcheck option makes it installed but
running virtaal gives same sqlite3 error: http://pastebin.com/YxGNhy88

I digg it, altough i have no coder skills, and i see that both
translate-toolkit ( see:
http://bugs.locamotion.org/show_bug.cgi?id=2073 ) and virtaal tries to
import sqlite3 while it should be _sqlite3. So i changed those lines
and propose a patch: http://pastebin.com/ThnF3q5r for virtaal and
http://pastebin.com/ZgsBMGsD for translate-toolkit

FURTHER ERRORS: It seems that those patches worked and virtaal can run
without a glitch. But i have disappointed the result immediately.
While virtaal can open some of .po files mostly it throws two kind of
errors and refuse to open those po files. (Those files can be
processed via poedit, gtranslator, lokalize and windows version -on
both a windows machine and using wine on linux - of virtaal; so po
files are not problem)
    SECONDARY ERROR A: See: http://pastebin.com/VTfdS52p
(IntegrityError: units.fileid may not be NULL)
    SECONDARY ERROR B: I didnt paste it to pastebin but with a second
post tonigt i' ll give the pastebin link. It simply, throw "Could not
open file. /path/to/pofile/file.po Try opening a different file."
    And this error comes from maincontroller.py line 208. As i can
remember it shows filename="/path/to/pofile/file.po", uri="" .

Well, i really want to use virtaal but those are showstoppers for a
Turkish locale user. Other translation editors are not future rich as
virtaal and not so easy to use as virtaal. Hope those bugs will
solved. If you want further info please contact me.

Also; i think mailman have same Turkish allergy too. I can not
subscribe to list with turkish characters O with dots over it an S
with a dot below it. Please fix this issue too. Thanks

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
&lt;/pre&gt;</description>
    <dc:creator>atilla ontas</dc:creator>
    <dc:date>2011-12-05T09:55:03</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2589">
    <title>Packaging advice</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2589</link>
    <description>&lt;pre&gt;Hi all!

I'm in the process of putting translate-toolkit and virtaal into the
main openSUSE repository (OSS) which means that for 12.2 (the next oS)
and beyond users will not have to handle with repositories, etc.

What I'm asking is to the pro's give a look at the Requires and
BuildRequires of both packages (below) and see if I'm not missing
anything or changing some dependency which is for execution into the
build requires.


# spec file for package translation-toolkit

BuildRequires: python
BuildRequires: python-devel

Requires:      gettext-runtime
Requires:      python-lxml &amp;gt;= 2.1.4
Requires:      python-simplejson
Requires:      python-Levenshtein
Requires:      python-iniparse
Requires:      vobject
Requires:      python-enchant
Suggests:      gaupol

%ifarch %{ix86}
Requires:       python-psyco
%endif

# The following are needed for man page generation
BuildRequires: python-lxml-doc &amp;gt;= 2.1.4

----------------------------
# spec file for virtaal

BuildRequires:  python-devel
BuildRequires:  python-lxml-doc
BuildRequires:  translate-toolkit &amp;gt;= 1.5.3
BuildRequires:  python-curl &amp;gt;= 7.19.0
BuildRequires:  gtk2
BuildRequires:  python-gtk
BuildRequires:  libtranslate0
BuildRequires:  libglade2

Requires:       python-curl &amp;gt;= 7.19.0
Requires:       translate-toolkit &amp;gt;= 1.5.3
Requires:       python-gobject2
Requires:       python-lxml
Requires:       gtkspell
Requires:       python-gnome-extras
Requires:       python-Levenshtein
Requires:       python-psycopg2
Requires:       python-simplejson
Requires:       xdg-utils

# psyco doesn't build on python 2.7
%if 0%{?suse_version} &amp;lt;= 1130
%ifarch %{ix86}
Requires:       python-psyco
%endif
%endif

Regards,

Luiz

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
&lt;/pre&gt;</description>
    <dc:creator>Luiz Fernando Ranghetti</dc:creator>
    <dc:date>2011-11-30T19:43:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.misc.translate.devel/2588">
    <title>Behaviour of pofilter's autocorrect</title>
    <link>http://comments.gmane.org/gmane.comp.misc.translate.devel/2588</link>
    <description>&lt;pre&gt;
Hi everybody

I'm considering making a few somewhat big changes to pofilter's
autocorrect behaviour. Naturally I hope it will be an improvement, but
I'm just wondering if anybody relies on the current behaviour, and of
course, I'm looking for people willing to test whatever new behaviour I
might come up with.

The current issues that I want to address:

- it isn't language aware at all, so it will force the punctuation to be
the same as the source text
- it doesn't handle spacing mistakes in before the final punctuation
- it can only fix one error

Keep well
Friedel



&lt;/pre&gt;</description>
    <dc:creator>F Wolff</dc:creator>
    <dc:date>2011-11-10T11:24:17</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.misc.translate.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.misc.translate.devel</link>
  </textinput>
</rdf:RDF>

