Hello everyone

For those who know how to run an SWF file in their browser, and who have
14 minutes to spare, have a look at this preliminary little
demonstration of Aligner and Bligner.  There is no sound.  The final
version will probably come with written comments that stop the action so
that the viewer can read the comment and then click to continue.

http://wikisend.com/download/931856/bligner.swf (12 MB)

Samuel

On Wed, Nov 3, 2010 at 01:42, Samuel Murray (Ugchelen) <leuce@...
> wrote:

>
>
> Hello everyone
>
> For those who know how to run an SWF file in their browser, and who have
>

FYI, it's as easy as downloading the file, then choosing "File->open file
(Ctl-O)" in a web browser.



> 14 minutes to spare, have a look at this preliminary little
> demonstration of Aligner and Bligner. There is no sound. The final
> version will probably come with written comments that stop the action so
> that the viewer can read the comment and then click to continue.
>
> http://wikisend.com/download/931856/bligner.swf (12 MB)
>
> Samuel
>
>



--
Not good enough for Republicans. Peter Diamond, a 70-year-old economist at
MIT, just won the Nobel Prize in Economics. Peter Diamond, the very same
70-year-old economist at MIT, was appointed to the Federal Reserve in April
by President Obama but has had his confirmation blocked by Senate
Republicans who doubt his economic qualifications for the job. Strange place
that United States.
  - 20101012, Richard Farmer, crikey.com.au


[Non-text portions of this message have been removed]

On 11/2/2010 7:42 AM, Samuel Murray (Ugchelen) wrote:
> Hello everyone
>
> For those who know how to run an SWF file in their browser, and who have
> 14 minutes to spare, have a look at this preliminary little
> demonstration of Aligner and Bligner.  There is no sound.  The final
> version will probably come with written comments that stop the action so
> that the viewer can read the comment and then click to continue.
>
> http://wikisend.com/download/931856/bligner.swf (12 MB)
>
> Samuel
>
Very informative for myself. Thank you.

If you're the one making up this tutorial, it would be nice
if the comments going with
the tutorial could be open for translation by interested
users ;-)

--
Fight Spam - report it with wxSR
http://www.columbinehoney.net/wxSR.shtml



[Non-text portions of this message have been removed]

Hi Didier,

Thanks for your help. It was indeed one of the files in my TM folder - I was
experimenting with Wordfast to produce an unclean document for a client and had
used the file in question with Wordfast so perhaps that was the problem.

Thanks again.
Kind regards,
Rachel


--- In OmegaT@yahoogroups.com, "Didier Briel" <d.briel@...> wrote:
>
> -----Original Message-----
> >From: OmegaT@yahoogroups.com [mailto:OmegaT@yahoogroups.com]On Behalf Of
> rachelempringham
> >Sent: Wednesday, October 20, 2010 10:03 PM
> >To: OmegaT@yahoogroups.com
> >Subject: [OmT] Fatal Errors
>
> >I am having problems with OmegaT and Open Office.
> >
> >Creating a project seems to work fine if there is no TM involved. But when
> loading the TMX files, I get an error message:
> >Fatal error on line 731, column 568 while parsing org.xml.sax.SAParse
> Exception: Attribute name 'la' associated with an element type 'tuv' must be
> followed by the '=' character.
>
> This TMX has been corrupted (or was never right in the first place). Where
> did you get it?
>
> >I tried testing with a different document and a different set of TMs, and I
> got:
> >Fatal error on line 209, column 1 while parsing:
> org.xml.sax.SAParseException: Content is not allowed in trailing section.
>
> Again, one (at least) of the TMXs seems to be damaged.
>
> >This all seems to have been triggered by a particular document. I am also
> having problems with Open Office (whenever I try to open the document in
> question I get the document recovery message with "the next time Open Office
> is opened the following files will be recovered", but there are no files in
> the list as I haven't been working on anything and when I close the message
> nothing happens).
>
> This document might have been damaged by translating it while damaging its
> tags in OmegaT.
>
> You should concentrate on one thing at a time.
>
> What are you trying to do exactly?
>
> If you are trying to translate a document:
> - Create an empty project.
> - Put the source document in /source.
> - Load the project.
>
> If that still works:
> - Put *one* of the TMX in the /tm project. If it still works, continue
> putting other TMXs one by one until you get the Fatal error message.
> At that step, you know which one is wrong.
>
> Report here your progress.
>
> Didier
>

Error: org.omegat.filters2.TranslationException: Unexpected char < (1)!

Hello, this occurred on an ODT file, it is not said the fault is of ODT format.
I held this old project for my personal CV-s and translated 1 odt and 1 ods file
before, adding today another odt document.

Yes, meanwhile I enriched the segmentation rules, but this should not block the
opening of the project. And of course, I use one of the most recent OmT (beta
2201)

It seems that this character "<" derives from a EN<>SR, i.e. this is a language
pair in my CV, and seems as a tag. I've changed now the above, into EN<space>SR,
and into EN-SR, happens the same error. Also, I deleted the today's file, and
continues happen. But this ">" might be some internal invisible character in OOo
file scheme...?

Any clarification and help are welcome, tvm. Dragomir

-----Original Message-----
>From: OmegaT@yahoogroups.com [mailto:OmegaT@yahoogroups.com]On Behalf Of
dragomir_k
>Sent: Friday, November 05, 2010 12:14 PM
>To: OmegaT@yahoogroups.com
>Subject: [OmT] error reading a ODT file
>
>Error: org.omegat.filters2.TranslationException: Unexpected char < (1)!

>Hello, this occurred on an ODT file,

Is that the only document in source?

>it is not said the fault is of ODT format. I held this old project for my
personal CV-s and translated 1 odt and 1 ods file before, adding today
another odt document.

>It seems that this character "<" derives from a EN<>SR,

It is *very* unlikely.

>i.e. this is a language pair in my CV, and seems as a tag. I've changed now
the above, into EN<space>SR, and into EN-SR, happens the same error. Also, I
deleted the today's file,

So it isn't related to "today's file", it seems.

>and continues happen. But this ">" might be some internal invisible
character in OOo file scheme...?

- Create a new project.
- Put only one of your source documents in /source.
- Load the project.
- Does it happen?
- If yes, send me the document.
- If not, add the other documents one by one. If the issue happens for one
of the document, send it to me.

If, from the above, you didn't find the issue:
Zip the entire project, and send it to me.

Didier

OmegaT is breaking segments on manual newlines, while I want to not
segment on newlines but only on paragraph marks.  I can't figure out
which is the segmentation rule character for a manual newline, to set an
exception.  Thanks for help.

On 5 nov. 10, at 22:42, John Fossey wrote:

> OmegaT is breaking segments on manual newlines, while I want to not
> segment on newlines but only on paragraph marks.  I can't figure out
> which is the segmentation rule character for a manual newline, to set an
> exception.  Thanks for help.


Options > File Filters > Text files > [Options] > Empty lines.


Jean-Christophe Helary
----------------------------------------
fun: http://mac4translators.blogspot.com
work: http://www.doublet.jp (ja/en > fr)
tweets: http://twitter.com/brandelune

-----Original Message-----
>From: OmegaT@yahoogroups.com [mailto:OmegaT@yahoogroups.com]On Behalf Of
Jean-Christophe Helary
>Sent: Friday, November 05, 2010 2:47 PM
>To: OmegaT@yahoogroups.com
>Subject: Re: [OmT] Stopping segmentation on manual newline
>
>
>On 5 nov. 10, at 22:42, John Fossey wrote:
>
>> OmegaT is breaking segments on manual newlines, while I want to not
>> segment on newlines but only on paragraph marks.  I can't figure out
>> which is the segmentation rule character for a manual newline, to set an
>> exception.  Thanks for help.
>
>
>Options > File Filters > Text files > [Options] > Empty lines.

*If* it's a text file.

Didier

On 5 nov. 10, at 22:52, Didier Briel wrote:

> -----Original Message-----
>> From: OmegaT@yahoogroups.com [mailto:OmegaT@yahoogroups.com]On Behalf Of
> Jean-Christophe Helary
>> Sent: Friday, November 05, 2010 2:47 PM
>> To: OmegaT@yahoogroups.com
>> Subject: Re: [OmT] Stopping segmentation on manual newline
>>
>>
>> On 5 nov. 10, at 22:42, John Fossey wrote:
>>
>>> OmegaT is breaking segments on manual newlines, while I want to not
>>> segment on newlines but only on paragraph marks.  I can't figure out
>>> which is the segmentation rule character for a manual newline, to set an
>>> exception.  Thanks for help.
>>
>>
>> Options > File Filters > Text files > [Options] > Empty lines.
>
> *If* it's a text file.

Correct.

What it the format of your document ?


Jean-Christophe Helary
----------------------------------------
fun: http://mac4translators.blogspot.com
work: http://www.doublet.jp (ja/en > fr)
tweets: http://twitter.com/brandelune

No, its an .odp Impress presentation.

Blocks of text need to be translated together and the line end is a
manual (soft) line break.  Separate blocks are ended with a paragraph
mark (hard line break). Each block needs to be translated as one.

-----Original Message-----
  >From: OmegaT@yahoogroups.com
<http://tech.groups.yahoo.com/group/OmegaT/post?postID=YnZBHSoV9UZSZ-zPKYPQ5NRDG\
E7VTA2OcvlJLBSFKvdMzLmz3qewdu2A-aXpSFLjNAkgdUcVzTFyac59mERx>
[mailto:OmegaT@yahoogroups.com
<http://tech.groups.yahoo.com/group/OmegaT/post?postID=YnZBHSoV9UZSZ-zPKYPQ5NRDG\
E7VTA2OcvlJLBSFKvdMzLmz3qewdu2A-aXpSFLjNAkgdUcVzTFyac59mERx>]On
Behalf Of
Jean-Christophe Helary
  >Sent: Friday, November 05, 2010 2:47 PM
  >To: OmegaT@yahoogroups.com
<http://tech.groups.yahoo.com/group/OmegaT/post?postID=YnZBHSoV9UZSZ-zPKYPQ5NRDG\
E7VTA2OcvlJLBSFKvdMzLmz3qewdu2A-aXpSFLjNAkgdUcVzTFyac59mERx>
  >Subject: Re: [OmT] Stopping segmentation on manual newline
  >
  >
  >On 5 nov. 10, at 22:42, John Fossey wrote:
  >
  >> OmegaT is breaking segments on manual newlines, while I want to not
  >> segment on newlines but only on paragraph marks. I can't figure out
  >> which is the segmentation rule character for a manual newline, to set an
  >> exception. Thanks for help.
  >
  >
  >Options > File Filters > Text files > [Options] > Empty lines.

*If* it's a text file.

Didier


[Non-text portions of this message have been removed]

Check that the HTML+XHTML filter isn't causing this. It contains the
following rule:

<br\d+/?>

If you want to break on soft returns, check the Break/Exception box. If
you don't, uncheck it. It's intended for HTML/XHTML, but affects other
file formats as well.

Marc



John Fossey wrote:
> No, its an .odp Impress presentation.
>
> Blocks of text need to be translated together and the line end is a
> manual (soft) line break.  Separate blocks are ended with a paragraph
> mark (hard line break). Each block needs to be translated as one.
>
> -----Original Message-----
>  >From: OmegaT@yahoogroups.com
>
<http://tech.groups.yahoo.com/group/OmegaT/post?postID=YnZBHSoV9UZSZ-zPKYPQ5NRDG\
E7VTA2OcvlJLBSFKvdMzLmz3qewdu2A-aXpSFLjNAkgdUcVzTFyac59mERx>
> [mailto:OmegaT@yahoogroups.com
>
<http://tech.groups.yahoo.com/group/OmegaT/post?postID=YnZBHSoV9UZSZ-zPKYPQ5NRDG\
E7VTA2OcvlJLBSFKvdMzLmz3qewdu2A-aXpSFLjNAkgdUcVzTFyac59mERx>]On
> Behalf Of
> Jean-Christophe Helary
>  >Sent: Friday, November 05, 2010 2:47 PM
>  >To: OmegaT@yahoogroups.com
>
<http://tech.groups.yahoo.com/group/OmegaT/post?postID=YnZBHSoV9UZSZ-zPKYPQ5NRDG\
E7VTA2OcvlJLBSFKvdMzLmz3qewdu2A-aXpSFLjNAkgdUcVzTFyac59mERx>
>  >Subject: Re: [OmT] Stopping segmentation on manual newline
>  >
>  >
>  >On 5 nov. 10, at 22:42, John Fossey wrote:
>  >
>  >> OmegaT is breaking segments on manual newlines, while I want to not
>  >> segment on newlines but only on paragraph marks. I can't figure out
>  >> which is the segmentation rule character for a manual newline, to set an
>  >> exception. Thanks for help.
>  >
>  >
>  >Options > File Filters > Text files > [Options] > Empty lines.
>
> *If* it's a text file.
>
> Didier
>
>
>

That was it - perfect now.

Thanks.

--------------- Message d'origine --------------
Re: [OmT] Stopping segmentation on manual newline

Check that the HTML+XHTML filter isn't causing this. It contains the
following rule:

<br\d+/?>

If you want to break on soft returns, check the Break/Exception box. If
you don't, uncheck it. It's intended for HTML/XHTML, but affects other
file formats as well.

Marc



John Fossey wrote:
  > No, its an .odp Impress presentation.
  >
  > Blocks of text need to be translated together and the line end is a
  > manual (soft) line break. Separate blocks are ended with a paragraph
  > mark (hard line break). Each block needs to be translated as one.
  >
  > -----Original Message-----
  > >From: OmegaT@yahoogroups.com
<http://tech.groups.yahoo.com/group/OmegaT/post?postID=kJCZW7jZQEGImg7LDXklFi24v\
TG5tiwnPz2zcEI-yL1H_4OfoWeovrpY1NPdZjNFE9I7vLc640mk9JYV>
  >
<http://tech.groups.yahoo.com/group/OmegaT/post?postID=YnZBHSoV9UZSZ-zPKYPQ5NRDG\
\
E7VTA2OcvlJLBSFKvdMzLmz3qewdu2A-aXpSFLjNAkgdUcVzTFyac59mERx
<http://tech.groups.yahoo.com/group/OmegaT/post?postID=YnZBHSoV9UZSZ-zPKYPQ5NRDG\
E7VTA2OcvlJLBSFKvdMzLmz3qewdu2A-aXpSFLjNAkgdUcVzTFyac59mERx>>
  > [mailto:OmegaT@yahoogroups.com
<http://tech.groups.yahoo.com/group/OmegaT/post?postID=kJCZW7jZQEGImg7LDXklFi24v\
TG5tiwnPz2zcEI-yL1H_4OfoWeovrpY1NPdZjNFE9I7vLc640mk9JYV>
  >
<http://tech.groups.yahoo.com/group/OmegaT/post?postID=YnZBHSoV9UZSZ-zPKYPQ5NRDG\
\
E7VTA2OcvlJLBSFKvdMzLmz3qewdu2A-aXpSFLjNAkgdUcVzTFyac59mERx
<http://tech.groups.yahoo.com/group/OmegaT/post?postID=YnZBHSoV9UZSZ-zPKYPQ5NRDG\
E7VTA2OcvlJLBSFKvdMzLmz3qewdu2A-aXpSFLjNAkgdUcVzTFyac59mERx>>]On
  > Behalf Of
  > Jean-Christophe Helary
  > >Sent: Friday, November 05, 2010 2:47 PM
  > >To: OmegaT@yahoogroups.com
<http://tech.groups.yahoo.com/group/OmegaT/post?postID=kJCZW7jZQEGImg7LDXklFi24v\
TG5tiwnPz2zcEI-yL1H_4OfoWeovrpY1NPdZjNFE9I7vLc640mk9JYV>
  >
<http://tech.groups.yahoo.com/group/OmegaT/post?postID=YnZBHSoV9UZSZ-zPKYPQ5NRDG\
\
E7VTA2OcvlJLBSFKvdMzLmz3qewdu2A-aXpSFLjNAkgdUcVzTFyac59mERx
<http://tech.groups.yahoo.com/group/OmegaT/post?postID=YnZBHSoV9UZSZ-zPKYPQ5NRDG\
E7VTA2OcvlJLBSFKvdMzLmz3qewdu2A-aXpSFLjNAkgdUcVzTFyac59mERx>>
  > >Subject: Re: [OmT] Stopping segmentation on manual newline
  > >
  > >
  > >On 5 nov. 10, at 22:42, John Fossey wrote:
  > >
  > >> OmegaT is breaking segments on manual newlines, while I want to not
  > >> segment on newlines but only on paragraph marks. I can't figure out
  > >> which is the segmentation rule character for a manual newline, to
set an
  > >> exception. Thanks for help.
  > >
  > >
  > >Options > File Filters > Text files > [Options] > Empty lines.
  >
  > *If* it's a text file.
  >
  > Didier
  >
  >
  >


[Non-text portions of this message have been removed]

Hello Didier,

I've just created a new project with one file, opened OK, added another one,
opened normally once again, added the 3rd, an OOo calc, all regular.
Then, of course, I used the previous TM level1.1, renamed it into
project_save.tmx to pretranslate at least the old part.

Today I hold several OOo big files opened, not being part of any OmT project,
and had to quickly access to this project. I would say that OOo shew some signs
of weakness. It occurs to me lately that I can't copy-paste bigger packs of
data, but just parts of them. Also, copy-paste from Windows notepad into OOo
became very buggy. All this on Win7-64bit. All well beaten. :)

Thank you v.m. for a straightforward instructions.

Dragomir

--- In OmegaT@yahoogroups.com, "Didier Briel" <d.briel@...> wrote:

> - Create a new project.
> - Put only one of your source documents in /source.
> - Load the project.
> - Does it happen?
> - If yes, send me the document.
> - If not, add the other documents one by one. If the issue happens for one
> of the document, send it to me.
>
> If, from the above, you didn't find the issue:
> Zip the entire project, and send it to me.
>
> Didier
>

I'd like to forward this mail from the okapitools list that contains a brief
introduction to ITS, the format that describes the translatable parts of an XML
document.

By using ITS, you can create specific filters for your XML files and process
them in Rainbow so as to be able to translate them in OmegaT.

> From: "yves_savourel"
> Date: 6 novembre 2010 22:07:09 UTC+09:00
> To: okapitools@yahoogroups.com
> Subject: [okapitools] Re: XML file: Translatable "alt=" attribute within the
IMG link.
> Reply-To: okapitools@yahoogroups.com
>
> FYI: I've added a step-by-step example on how to create a custom configuration
for the XML Filter in the wiki.
>
>
http://www.opentag.com/okapi/wiki/index.php?title=How_to_Create_a_Custom_Configu\
ration_for_the_XML_Filter
>
> Hopefully this should be a good starting point to understand some of the
aspects of ITS.


Jean-Christophe Helary
----------------------------------------
fun: http://mac4translators.blogspot.com
work: http://www.doublet.jp (ja/en > fr)
tweets: http://twitter.com/brandelune

Hello,

so I translated my first document with omegat today and after clicking on create
translated document and going to the target folder to open the doc this error
message came up (I'm translating from Italian here)
File Error in the Format, in the sub-document content.xml in 2,13996 (line,
column)
I'm desperate please help.

Also I need to translate a series of sentences in an excel format: how can I do
that? I mean I have to come up with a document that keeps the excel format (one
column source text and one column translation)

Thank you,

Laura

-----Original Message-----
>From: OmegaT@yahoogroups.com [mailto:OmegaT@yahoogroups.com]On Behalf Of
pitecusa
>Sent: Sunday, November 07, 2010 4:17 AM
>To: OmegaT@yahoogroups.com
>Subject: [OmT] need for help: two MAJOR issues!

>so I translated my first document with omegat today and after clicking on
create translated document and going to the target folder to open the doc
this error message came up (I'm translating from Italian here)
>File Error in the Format, in the sub-document content.xml in 2,13996 (line,
column)

Tools > Validate Tags (Ctrl+T).

Then correct any tag mentioned as faulty.

See the manual (F1):
Working with formatted texts

>Also I need to translate a series of sentences in an excel format: how can
I do that? I mean I have to come up with a document that keeps the excel
format (one column source text and one column translation)

Save a copy of the original.
Translate the original.
In Excel, copy the translated column from the copy to the translation column
of the original document.

Didier Briel

2010/11/7, Didier Briel <d.briel@...>:
> -----Original Message-----
>>From: OmegaT@yahoogroups.com [mailto:OmegaT@yahoogroups.com]On Behalf Of
> pitecusa
>>Sent: Sunday, November 07, 2010 4:17 AM
>>To: OmegaT@yahoogroups.com
>>Subject: [OmT] need for help: two MAJOR issues!
>
>>so I translated my first document with omegat today and after clicking on
> create translated document and going to the target folder to open the doc
> this error message came up (I'm translating from Italian here)
>>File Error in the Format, in the sub-document content.xml in 2,13996 (line,
> column)
>
> Tools > Validate Tags (Ctrl+T).
>
> Then correct any tag mentioned as faulty.
>
> See the manual (F1):
> Working with formatted texts
>
>>Also I need to translate a series of sentences in an excel format: how can
> I do that? I mean I have to come up with a document that keeps the excel
> format (one column source text and one column translation)
>
> Save a copy of the original.
> Translate the original.
> In Excel, copy the translated column from the copy to the translation column
> of the original document.
>
> Didier Briel
>
>


--
Best regards,
Amike,

Dmitri Gabinski

С уважением,

Дмитрий Габинский

Dear All,


OmegaT beta version 2.2.0 update 3 has been released.

This version is a maintenance release.

The handling of Google Translate results has been improved: spaces
introduced by GT around tags are now removed.

Hunspell has been updated to 1.2.12

The Polish and Brazilian Portuguese localisations have been updated.

You can download the new version following the directions from
http://www.omegat.org/en/downloads.html
for Latest versions.

Best regards,

Didier Briel

And my translation of UI to Russian is still missing...

2010/11/7 Didier Briel <d.briel@...>

>
>
> Dear All,
>
> OmegaT beta version 2.2.0 update 3 has been released.
>
> This version is a maintenance release.
>
> The handling of Google Translate results has been improved: spaces
> introduced by GT around tags are now removed.
>
> Hunspell has been updated to 1.2.12
>
> The Polish and Brazilian Portuguese localisations have been updated.
>
> You can download the new version following the directions from
> http://www.omegat.org/en/downloads.html
> for Latest versions.
>
> Best regards,
>
> Didier Briel
>
>
>



--
Freelance Translator
Kyiv, Ukraine


[Non-text portions of this message have been removed]

-----Original Message-----
>From: OmegaT@yahoogroups.com [mailto:OmegaT@yahoogroups.com]On Behalf Of Pavel
Maryanov
>Sent: Sunday, November 07, 2010 3:13 PM
>To: OmegaT@yahoogroups.com
>Subject: Re: [OmT] OmegaT beta version 2.2.0 update 3 released
>
>And my translation of UI to Russian is still missing...

Sorry about that.

I'll check with Jean-Christophe, who is the localisation manager.

Didier

> And my translation of UI to Russian is still missing...


It seems it was sent to the l10n mailing list rather than directly to
the localization co-ordinator.

I see that it is still at
http://jack.kiev.ua/filez/OmegaT_2.2.0_01_L10N_Minimal-ru.zip. I am sure
that it will be taken care of.

Marc



Pavel Maryanov wrote:
> And my translation of UI to Russian is still missing...
>
> 2010/11/7 Didier Briel <d.briel@...>
>
>
>> Dear All,
>>
>> OmegaT beta version 2.2.0 update 3 has been released.
>>
>> This version is a maintenance release.
>>
>> The handling of Google Translate results has been improved: spaces
>> introduced by GT around tags are now removed.
>>
>> Hunspell has been updated to 1.2.12
>>
>> The Polish and Brazilian Portuguese localisations have been updated.
>>
>> You can download the new version following the directions from
>> http://www.omegat.org/en/downloads.html
>> for Latest versions.
>>
>> Best regards,
>>
>> Didier Briel
>>
>>
>>
>>
>
>
>
>

-----Original Message-----
>From: OmegaT@yahoogroups.com [mailto:OmegaT@yahoogroups.com]On Behalf Of Marc
Prior
>Sent: Sunday, November 07, 2010 3:22 PM
>To: OmegaT@yahoogroups.com
>Subject: [OmT] OmegaT beta version 2.2.0 update 3 released
>
>> And my translation of UI to Russian is still missing...
>
>
>It seems it was sent to the l10n mailing list rather than directly to
>the localization co-ordinator.
>
>I see that it is still at
>http://jack.kiev.ua/filez/OmegaT_2.2.0_01_L10N_Minimal-ru.zip. I am sure
>that it will be taken care of.

Got it.

It will appear in next release.

Didier

Didier,

thank you so much for your help with the corrupted document. I will also used
the advice you gave me concerning the excel spreadsheet.

One more question: if my original doc is excel (.xls) what format would you
recommend to save it as?

Thanks again. You really saved my day!

Laura

--- In OmegaT@yahoogroups.com, "pitecusa" <pitecusa@...> wrote:
>
> Hello,
>
> so I translated my first document with omegat today and after clicking on
create translated document and going to the target folder to open the doc this
error message came up (I'm translating from Italian here)
> File Error in the Format, in the sub-document content.xml in 2,13996 (line,
column)
> I'm desperate please help.
>
> Also I need to translate a series of sentences in an excel format: how can I
do that? I mean I have to come up with a document that keeps the excel format
(one column source text and one column translation)
>
> Thank you,
>
> Laura
>

-----Original Message-----
>From: OmegaT@yahoogroups.com [mailto:OmegaT@yahoogroups.com]On Behalf Of
pitecusa
>Sent: Sunday, November 07, 2010 6:07 PM
>To: OmegaT@yahoogroups.com
>Subject: [OmT] Re: need for help: two MAJOR issues!

>One more question: if my original doc is excel (.xls) what format would you
recommend to save it as?

You can either convert it to .ods with OpenOffice.org, or you can convert it
to .xlsx with a recent version of MS Office or a free patch from Microsoft
(http://office.microsoft.com/en-us/support/microsoft-office-compatibility-pa
ck-for-word-excel-and-powerpoint-2007-file-formats-HA010168676.aspx).

For more general information, reading the compatibility howto is
recommended:
http://www.omegat.org/en/howtos/compatibility.html


Didier

--- In OmegaT@yahoogroups.com, "Didier Briel" <d.briel@...> wrote:
>
> Dear All,
>
>
> OmegaT beta version 2.2.0 update 3 has been released.
>
> This version is a maintenance release.
>

The OmegaT main page in SourceForge still shows OmegaT 2.0.5 update 4 as the
default version to download.
http://sourceforge.net/projects/omegat/

Is there any plan to release a, let's say, "stable" version, or will OmegaT keep
something similar to a rolling release schedule?

Just to know when could be the best time to update my Basque localization.

Regards.
Asier.

-----Original Message-----
>From: OmegaT@yahoogroups.com [mailto:OmegaT@yahoogroups.com]On Behalf Of
Asier
>Sent: Sunday, November 07, 2010 10:17 PM
>To: OmegaT@yahoogroups.com
>Subject: [OmT] Re: OmegaT beta version 2.2.0 update 3 released

>> OmegaT beta version 2.2.0 update 3 has been released.
>>
>> This version is a maintenance release.
>>
>
>The OmegaT main page in SourceForge still shows OmegaT 2.0.5 update 4 as
the default version to download.
>http://sourceforge.net/projects/omegat/
>
>Is there any plan to release a, let's say, "stable" version,

2.0.5 update 4 *is* the stable version, currently.

>or will OmegaT keep something similar to a rolling release schedule?

I'm not sure I understand the question.

Stable is "stable", and Latest is "latest", as explained on the download
page:
http://www.omegat.org/en/downloads.html

There are always (potentially) updates to both (even if 2.0.5 is stopped
currently).

At some point, 2.2 (or later) will become the new stable.

>Just to know when could be the best time to update my Basque localization.

It's up to you but, IMHO, the best time is "now", i.e., whenever you have
the time to do so.

Didier

--- In OmegaT@yahoogroups.com, "Didier Briel" <d.briel@...> wrote:
>
> At some point, 2.2 (or later) will become the new stable.
>
> >Just to know when could be the best time to update my Basque localization.
>
> It's up to you but, IMHO, the best time is "now", i.e., whenever you have
> the time to do so.
>

Thanks Didier.

Asier.

Hi to all ;)

I've just discovered something appearing like a bug with OmegaT,
My config is: Laptop MSI MS 1734 (CR700 series)
Ubuntu 10.04 up to date with  ubuntu recommended Nvidia driver version 260.19.06
for the graphic card.


OmegaT start log:
vince@LinuxBox:~$ java -jar OmegaT/OmegaT.jar
37260: Info: ===================================================================
37260: Info: OmegaT-2.2.0_3 (Tue Nov 09 09:46:32 CET 2010)  Locale fr_FR
37260: Info: Java : Sun Microsystems Inc. ver. 1.6.0_20, ex�cut� � partir de 
��/usr/lib/jvm/java-6-openjdk/jre�� (LOG_STARTUP_INFO)
37260: Info: Docking Framework version: 2.1.4

The problem occurs only when i click on Options --> Segmentation

Then it kind of freeze for 30 seconds (omegaT screen is empty) before opening
the segmentation window, while my desktop screen is reduced (at least 1/3),
there's some big black bands (des bandes noires) on left, right and bottom and i
can only see and use programs on the reduced desktop screen size, i need to
re-login (restart X session) to go back to normal.
One strange thing is that when the usable screen is reduced, the gnome
desktop-bar (at the top and bottom) appears and react normally, as well as Docky
which i use too, those elements are not modified by the 'bug'. I was wondering
if this problem can be linked with the Nvidia driver and kernel modules, or
Java, or both ?.

It was the same with the prior OmegaT version (i have updated yesterday).

Am i the only one experimenting this when opening Segmentation ?

Bonne journ�e !
Vincent

-----Original Message-----
>From: OmegaT@yahoogroups.com [mailto:OmegaT@yahoogroups.com]On Behalf Of
vincelyfr
>Sent: Tuesday, November 09, 2010 11:12 AM
>To: OmegaT@yahoogroups.com
>Subject: [OmT] Desktop screen size reduced when clicking on segmentation

>I've just discovered something appearing like a bug with OmegaT,
>My config is: Laptop MSI MS 1734 (CR700 series)
>Ubuntu 10.04 up to date with  ubuntu recommended Nvidia driver version
260.19.06 for the graphic card.
>
>
>OmegaT start log:
>vince@LinuxBox:~$ java -jar OmegaT/OmegaT.jar
>37260: Info:
===================================================================
>37260: Info: OmegaT-2.2.0_3 (Tue Nov 09 09:46:32 CET 2010)  Locale fr_FR
>37260: Info: Java : Sun Microsystems Inc. ver. 1.6.0_20, ex�cut� � partir
de  " /usr/lib/jvm/java-6-openjdk/jre " (LOG_STARTUP_INFO)

Have you tried with Sun/Oracle's Java?

If you don't have it, you can try with the "Java included" Linux version of
OmegaT.

Didier