bitext2tmx-devel — A list for the developers of bitext2tmx

Re: [Bitext2tmx-devel] b2t : resizng windows + wish to help

[Raymond M. <la...@gm...>]

Hello Senor Mojo:

On March 21, 2010 06:24:32 am Mikel L. Forcada wrote:
> 
> thanks for your message and for your offer to help. I am currently not
> too active in bitext2tmx development, but I have forwarded your message
> to the bitext2tmx-devel list. I will get back to you as soon as I hear
> from them.
> 
> All the best,
> 
> Mikel L. Forcada
> 
>  En/na Senor Mojo ha escrit:
> > Message body follows:
> > 
> > Hi,
> > 
> > I posted a thread in regards to my being unable to resize windows. I
> > use release 1.0M0 on Mac Os 10.4.11.
> > I see the double-sided arrows when putting my cursor in the fringe, but i
> > cannot stretch the windows.
> > On another topic, I am French and English copy writer and translator
> > and I would like to know if there is a way I can contribute, talent and
> > time wise.

The functionality to re-size the window is not available in that version.
There is a newer version of the program in the Git repository that you would 
have check out and compile using Java. It can resize, if I remember correctly.

Apart from that, I personally have not had much time to work on B2T
development in a long time. There are many improvements that can be add to the 
program. You certainly can contribute to the program, but depending upon what 
you want to do and time available we will just have to see what we can do.

There are already some English/French resources for the program (localization, 
webpages). As usual with a project there is always a need for good 
documentation and updates to localizations and webpages. Is any of that of 
interest (or something to do with programming perhaps)?

Any contributions are welcome. Let us know.

Thanks.

Raymond

Re: [Bitext2tmx-devel] b2t : resizng windows + wish to help

[Mikel L. F. <ml...@dl...>]

Dear Senor Mojo:

thanks for your message and for your offer to help. I am currently not 
too active in bitext2tmx development, but I have forwarded your message 
to the bitext2tmx-devel list. I will get back to you as soon as I hear 
from them.

All the best,

Mikel L. Forcada


 En/na Senor Mojo ha escrit:
> Message body follows:
>
> Hi,
>
> I posted a thread in regards to my being unable to resize windows. I 
> use release 1.0M0 on Mac Os 10.4.11.
> I see the double-sided arrows when putting my cursor in the fringe, but i 
> cannot stretch the windows. 
> On another topic, I am French and English copy writer and translator 
> and I would like to know if there is a way I can contribute, talent and 
> time wise.
>
> Thank you
> Senor Mojo
>
> --
> This message has been sent to you, a registered SourceForge.net user,
> by another site user, through the SourceForge.net site.  This message
> has been delivered to your SourceForge.net mail alias.  You may reply
> to this message using the "Reply" feature of your email client, or
> using the messaging facility of SourceForge.net at:
> https://sourceforge.net/sendmessage.php?touser=2849699
>   

[Bitext2tmx-devel] Git commit

[<la...@gm...>]

Hi all,

Okay, the first commit to Git has been done. I have also created an
"experimental" branch. Please pull and push to that branch, not "master".
Aside from the initial commit that needed to be done on the master branch, we 
will keep the master for stable tagged versions only.

Just make sure to pull/fetch from "experimental" and then all pushes will go
directly back to that branch. The experimental stuff will later be merged into
the master for tagged release versions. Of course, make as many branches
as desired in your local git repository and merge them into your local 
experimental version before pushing the changes to the SourceForge remote
repository.

As for the code, there are definitely more changes needed on the GUI side with
the new docking desktop, plus some other bugs I noticed along the way. Lots
to do, so if you see any bugs please file notes about them on the project.

Comments, ideas?

Cheers,

Raymond

[Bitext2tmx-devel] Git SCM and B2T 1.0.M1 development

[raymond <la...@gm...>]

Hi all,

I am starting to cleanup/order the code/file/directories to push it onto the 
SF bitext2tmx Git repository. So just providing some preliminary information
about what I am thinking of doing in this regard so we can discuss things and
move forward to version 1.0.M1.

Firstly, pushing all the code to Git is very easy and the commands are
straightforward as far as I can see. If you need information about Git, SF
has its own page at http://sourceforge.net/apps/trac/sourceforge/wiki/Git
with regard to how to use it on SF. And the official Git documentation is at 
http://git-scm.com/documentation.

A primary issue is how work is to be performed once the master branch has
been put up. In this regard, I would like to create separate branches for the
actual work (e.g., at least a branch named "experimental"). All the unstable
changes and experimentation can be done on this "experimental" branch
while retaining the master branch for stable versions/releases after
sufficient testing is done. Thus, I am asking that developers checkout/checkin
code from the experimental branch and not the master one. There is also
a way to control who commits to specific branches I believe. This might be
an option to use. There are only two people going to be doing any work on
B2T as far as I know, so it may not be an issue as long as we keep each other
informed as work progresses.

Anyway, if you have any other ideas about this let us all know so we can
choose the best way going forward.

Apart from that, I am looking over the current code and I have to cleanup and
make some rearrangements. I am trying to simplify the /src folder hierarchy
and have decided to move some resources outside of this path. The program
icons used by the docking desktop and other components is outside now so that
these can easily be changed without recompiling the application, it is the
same as the localizations in this regard then. And, of course, the docking
desktop is completely experimental in this version (although I have experience
using the library in OmegaT+), so there might need to be some rearrangement
or redesign of certain components. You will have to run the application when 
it is available, see what you think and let us all know.

Anyway, I should have the first commit to the repository up in the next few
days. Then we can start to integrate the newly ported code from TagAligner
by Miquel into it. Version 1.0.M1 will definitely have some significant
improvements all around.

Apart from that, B2T sorely needs better documentation, in all languages
supported. Not to mention improvements to the webpages. Help with this,
when people have time, would be a real plus for users interested in B2T.

Your thoughts or comments...

Cheers,

Raymond

Re: [Bitext2tmx-devel] bitext2tmx 1.0.M1

[Mikel L. F. <ml...@dl...>]

Raymond:
>
> I see he is now on the project as a member. 

Sure, I made him.

> Someone should have posted 
> about this on the mailing list so we can avoid wasted effort and know what
> is going on. 

I could have, that's true. I apologize. Fortunately, not much effort has been 
lost.

> Anyway, I don't see that anything has been committed to the 
> trunk. It does not matter because I already fixed the loading of TMX and
> the dialog for M1. His effort is wasted if he did do something without
> making it known.

You have already made your point, Raymond. Things are far from being optimal 
when people are so busy, that's all. We'll try to do it better next time.

> > I hope what Miquel did doesn't break this plan. If not, we can always
> > merge.
>
> Nothing to merge, as far as I can tell.

Good.

> I am just learning git myself, but I would definitely give Linus Torvalds
> the benefit of the doubt for developing it given that RCS, CVS, SVN, and so
> forth were readily available when he did it. We'll see.

He's a referent. We can give it a try as I said.

Best

Mikel

Re: [Bitext2tmx-devel] bitext2tmx 1.0.M1

[Raymond M. <la...@gm...>]

Hi,

On 24 March 2009 08:18:05 Miquel Esplà wrote:
> > >
> > > In connection with this: my student Miquel Esplhas been commiting
> > changes to the trunk (just to change the dialog that allowed to load and continue
> > > aligning a TMX file).
> >
> > I see he is now on the project as a member. Someone should have posted
> > about this on the mailing list so we can avoid wasted effort and know what is going
> > on. Anyway, I don't see that anything has been committed to the trunk. It does not
> > matter because I already fixed the loading of TMX and the dialog for M1. His effort is
> > wasted if he did do something without making it known.
> 
> It's true that I would have to send a mail asking about it, I'm sorry. In
> any case, I have the code (it's not commited to the trunk, but I can do it
> when you whant). I've only writed it because I was looking for that option
> in the code placed in CVS and I didn't find it. If you have fixed it, all
> correct, I will delete my code. If you whant the code, I can commit it.

You can send it to me rather than putting it in CVS. Maybe there is something
to be used even though I fixed it, AFAIK. I would like to avoid anymore work
with CVS on the project. Once M1 is ready a fresh commit to git (or SVN) will
happen.

I see you are also involved in bitextor and tag-aligner. I am thinking of porting
the tag-aligner code to java for use in B2T. There are still lots of issues surrounding
this in terms of testing it for expected results. It is definitely better than what is
used for alignment in B2T now. Need to create document filters for various inputs
that B2T currently does not support (will be putting Java .properties support in soon).
Will be taking a serious look at filters for HTML/XHTML (tag-aligner) and OpenDocument
format at least.

If you have an ideas just let us all know so we can co-ordinate our efforts.

Regards,

Raymond

Re: [Bitext2tmx-devel] bitext2tmx 1.0.M1

[Miquel E. <miq...@gm...>]

Hi,

2009/3/24 Raymond Martin <la...@gm...>

> Hi,
>
> On 24 March 2009 06:53:05 you wrote:
> >
> > > A bit of code cleanup and optimization is also being done, but real
> changes
> > > (e.g., alignment algorithm upgrade) will have to wait for M2 or later.
> >
> > In connection with this: my student Miquel Esplà  has been commiting
> changes
> > to the trunk (just to change the dialog that allowed to load and continue
> > aligning a TMX file).
>
> I see he is now on the project as a member. Someone should have posted
> about this
> on the mailing list so we can avoid wasted effort and know what is going
> on. Anyway,
> I don't see that anything has been committed to the trunk. It does not
> matter because
> I already fixed the loading of TMX and the dialog for M1. His effort is
> wasted if he
> did do something without making it known.


It's true that I would have to send a mail asking about it, I'm sorry. In
any case, I have the code (it's not commited to the trunk, but I can do it
when you whant). I've only writed it because I was looking for that option
in the code placed in CVS and I didn't find it. If you have fixed it, all
correct, I will delete my code. If you whant the code, I can commit it.


>
>
> >
> > > Update versions of M1 should also be expected after it is released
> because
> > > there are numbers of things to take care of that will take too long to
> get
> > > together all at once. It has been long enough waiting for M1 so the
> best
> > > thing to do is just get a working version out as soon as is practical
> and
> > > then fix the various missing/broken pieces (not too many I hope).
> >
> > I hope what Miquel did doesn't break this plan. If not, we can always
> merge.
>
> Nothing to merge, as far as I can tell.
>
> > > Other things of concern for bitext2tmx:
> > >
> > > I never got around to putting the code into SVN. Alas, now SourceForge
> has
> > > git. I am just starting to look at it and it seems good. So the
> question is
> > > whether to switch to git for B2T or not. Now would be the best time
> since
> > > there is nothing in SVN.
> >
> > I would have to learn git (older people have a bit of trouble with
> learning
> > new things) but we can give it a try. It would be nice if you could give
> us
> > some tips on using it when you do the migration, if you plan to do that.
>
> I am just learning git myself, but I would definitely give Linus Torvalds
> the
> benefit of the doubt for developing it given that RCS, CVS, SVN, and so
> forth
> were readily available when he did it. We'll see.
>
> >
> > > Another thing is that the webpages (and documentation) need updating
> and
> > > more content. I will write some more content, but a problem exists in
> > > getting it translated. On OmegaT+ webpages I am using Google translate
> > > functionality (for what it is worth) to automatically translate and
> present
> > > the page to the user. Not sure you guys will want that since some of
> you
> > > work on Apertium. I will have to look again at the Apertium site, but I
> > > don't think the functionality (in javascript) exists to do what Google
> > > translate does (yet). What do you think?
> >
> > We have some webservices. We also have some plugins for things like
> Wordpress,
> > etc. It should not be a problem. Do you want me to ask? Maybe you can ask
> > yourself in ape...@li....
>
> Let me look into it first. I already hacked some code a few months ago to
> actually
> use apertium to translate from a Java application. Now I need something in
> Javascript
> to make this work with a wepage in place.
>
> >
> > I'd vote for having a wiki to keep documentation updated, and not
> worrying
> > much about being completely multilingual
>
> That would be fine with me, as long as I don't have to administer it. Too
> many
> other development activities to focus on. This is one reason I like the
> Google
> thing, expediency. You just put it in any webpage and it works (sort of).
> The main
> point to me is not necessaily to have a perfect translation, but to have at
> least
> something that a native reader can at least skim and the language centers
> in their
> brain can kind of fill in the gaps--maybe that will be enough to get some
> people to
> contribute a real translation :)
>
> Lots more to do.
>
> Cheers,
>
> Raymond
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Bitext2tmx-devel mailing list
> Bit...@li...
> https://lists.sourceforge.net/lists/listinfo/bitext2tmx-devel
>
>
Miquel Esplà.

Re: [Bitext2tmx-devel] bitext2tmx 1.0.M1

[Raymond M. <la...@gm...>]

Hi,

On 24 March 2009 06:53:05 you wrote:
> 
> > A bit of code cleanup and optimization is also being done, but real changes
> > (e.g., alignment algorithm upgrade) will have to wait for M2 or later.
> 
> In connection with this: my student Miquel Esplhas been commiting changes 
> to the trunk (just to change the dialog that allowed to load and continue 
> aligning a TMX file).

I see he is now on the project as a member. Someone should have posted about this
on the mailing list so we can avoid wasted effort and know what is going on. Anyway,
I don't see that anything has been committed to the trunk. It does not matter because
I already fixed the loading of TMX and the dialog for M1. His effort is wasted if he
did do something without making it known.

> 
> > Update versions of M1 should also be expected after it is released because
> > there are numbers of things to take care of that will take too long to get
> > together all at once. It has been long enough waiting for M1 so the best
> > thing to do is just get a working version out as soon as is practical and
> > then fix the various missing/broken pieces (not too many I hope). 
> 
> I hope what Miquel did doesn't break this plan. If not, we can always merge.

Nothing to merge, as far as I can tell.

> > Other things of concern for bitext2tmx:
> >
> > I never got around to putting the code into SVN. Alas, now SourceForge has
> > git. I am just starting to look at it and it seems good. So the question is
> > whether to switch to git for B2T or not. Now would be the best time since
> > there is nothing in SVN.
> 
> I would have to learn git (older people have a bit of trouble with learning 
> new things) but we can give it a try. It would be nice if you could give us 
> some tips on using it when you do the migration, if you plan to do that.

I am just learning git myself, but I would definitely give Linus Torvalds the
benefit of the doubt for developing it given that RCS, CVS, SVN, and so forth
were readily available when he did it. We'll see.

> 
> > Another thing is that the webpages (and documentation) need updating and
> > more content. I will write some more content, but a problem exists in
> > getting it translated. On OmegaT+ webpages I am using Google translate
> > functionality (for what it is worth) to automatically translate and present
> > the page to the user. Not sure you guys will want that since some of you
> > work on Apertium. I will have to look again at the Apertium site, but I
> > don't think the functionality (in javascript) exists to do what Google
> > translate does (yet). What do you think?
> 
> We have some webservices. We also have some plugins for things like Wordpress, 
> etc. It should not be a problem. Do you want me to ask? Maybe you can ask 
> yourself in ape...@li....

Let me look into it first. I already hacked some code a few months ago to actually
use apertium to translate from a Java application. Now I need something in Javascript
to make this work with a wepage in place.

> 
> I'd vote for having a wiki to keep documentation updated, and not worrying 
> much about being completely multilingual

That would be fine with me, as long as I don't have to administer it. Too many
other development activities to focus on. This is one reason I like the Google
thing, expediency. You just put it in any webpage and it works (sort of). The main
point to me is not necessaily to have a perfect translation, but to have at least
something that a native reader can at least skim and the language centers in their
brain can kind of fill in the gaps--maybe that will be enough to get some people to
contribute a real translation :)

Lots more to do.

Cheers,

Raymond

Re: [Bitext2tmx-devel] bitext2tmx 1.0.M1

[Mikel L. F. <ml...@dl...>]

On Monday 23 March 2009 17:02:09 Raymond Martin wrote:
> Hi all,
>
> I have been working on the M1 version of B2T in the past few weeks.
>
> Things are coming along and I have change it over to using the same docking
> desktop library as OmegaT+. Most the changes I have made, or will, for M1
> will be of a cosmetic nature, fixing the overall appearance/presentation.

Good.

> A bit of code cleanup and optimization is also being done, but real changes
> (e.g., alignment algorithm upgrade) will have to wait for M2 or later.

In connection with this: my student Miquel Esplà  has been commiting changes 
to the trunk (just to change the dialog that allowed to load and continue 
aligning a TMX file).

> Update versions of M1 should also be expected after it is released because
> there are numbers of things to take care of that will take too long to get
> together all at once. It has been long enough waiting for M1 so the best
> thing to do is just get a working version out as soon as is practical and
> then fix the various missing/broken pieces (not too many I hope). 

I hope what Miquel did doesn't break this plan. If not, we can always merge.

> Once M2
> comes around there will then be less need for updates (barring serious bugs
> after release).
>
> If anyone wants a pre-release version I can send it to them. Let me know.

Let's wait.

> Other things of concern for bitext2tmx:
>
> I never got around to putting the code into SVN. Alas, now SourceForge has
> git. I am just starting to look at it and it seems good. So the question is
> whether to switch to git for B2T or not. Now would be the best time since
> there is nothing in SVN.

I would have to learn git (older people have a bit of trouble with learning 
new things) but we can give it a try. It would be nice if you could give us 
some tips on using it when you do the migration, if you plan to do that.

> Another thing is that the webpages (and documentation) need updating and
> more content. I will write some more content, but a problem exists in
> getting it translated. On OmegaT+ webpages I am using Google translate
> functionality (for what it is worth) to automatically translate and present
> the page to the user. Not sure you guys will want that since some of you
> work on Apertium. I will have to look again at the Apertium site, but I
> don't think the functionality (in javascript) exists to do what Google
> translate does (yet). What do you think?

We have some webservices. We also have some plugins for things like Wordpress, 
etc. It should not be a problem. Do you want me to ask? Maybe you can ask 
yourself in ape...@li... .

I'd vote for having a wiki to keep documentation updated, and not worrying 
much about being completely multilingual

>
> Your thoughts.


What do you think?

Mikel
-- 
Mikel L. Forcada <ml...@dl...>
http://www.dlsi.ua.es/~mlf/

[Bitext2tmx-devel] bitext2tmx 1.0.M1

[Raymond M. <la...@gm...>]

Hi all,

I have been working on the M1 version of B2T in the past few weeks.

Things are coming along and I have change it over to using the same docking
desktop library as OmegaT+. Most the changes I have made, or will, for M1
will be of a cosmetic nature, fixing the overall appearance/presentation.

A bit of code cleanup and optimization is also being done, but real changes
(e.g., alignment algorithm upgrade) will have to wait for M2 or later.

Update versions of M1 should also be expected after it is released because
there are numbers of things to take care of that will take too long to get
together all at once. It has been long enough waiting for M1 so the best thing
to do is just get a working version out as soon as is practical and then fix the
various missing/broken pieces (not too many I hope). Once M2 comes around
there will then be less need for updates (barring serious bugs after release).

If anyone wants a pre-release version I can send it to them. Let me know.

Other things of concern for bitext2tmx:

I never got around to putting the code into SVN. Alas, now SourceForge has git.
I am just starting to look at it and it seems good. So the question is whether to
switch to git for B2T or not. Now would be the best time since there is nothing in SVN.

Another thing is that the webpages (and documentation) need updating and more content.
I will write some more content, but a problem exists in getting it translated. On OmegaT+
webpages I am using Google translate functionality (for what it is worth) to automatically
translate and present the page to the user. Not sure you guys will want that since some
of you work on Apertium. I will have to look again at the Apertium site, but I don't think
the functionality (in javascript) exists to do what Google translate does (yet). What do
you think?

Your thoughts.

Regards,

Raymond

[Bitext2tmx-devel] New bitext2tmx members

[Raymond M. <la...@gm...>]

Hi all,

A couple of new members have been added to the bitext2tmx project:
 - Valerie Martineau - French translation
 - Yannis Evangelou - Greek Translation

Both have been added under the role of Translator (I18N/L10N) with minimal
project access to begin with.

Valerie has already helped with some French translations and will be able to
help with the future versions. Yannis is a new contributor and we will have
to see if it works out.

If you receive this message via the SourceForge redirection to your mail
could somebody on the list please drop me a note (directly) saying that you
have seen it. I made a few posts recently through the SF lists and I do not see
them coming back or being archived. Something might be wrong since SF is
in transition to their new location in Chicago.

Thanks.

Raymond

P.S. bitext2tmx 1.0.M1 has been on hold for quite a while. I am busy preparing
OmegaT+ 1.0.M2. After that is out I can redirect some effort to B2T.

Re: [Bitext2tmx-devel] bitext2tmx

[Raymond M. <la...@gm...>]

Hi Yannis,

I have added you as project member to the SourceForge bitext2tmx project.
Your role is currently set as "Translator (I18N/L10N) and you have access to
the web space and CVS/SVN(to be put in place to replace CVS) repositories.

You can add a Greek version of the web page or get/put code/data, but please
let us know what you are doing or are going to do so we can avoid problems.
To this end, I suggest you join the bitext2tmx developers mailing list and make
announcements of any changes you are making.

Thanks and welcome to the project.

Regards,

Raymond

Re: [Bitext2tmx-devel] Fwd: bitext2tmx

[Raymond M. <bio...@ya...>]

Hi Andy,

> Thank you for your excellent effort with bitext2tmx!
> 
> However: I have a problem:
> 
> 
> When trying to open two large files i get the error
> "insufficient memory to continue processing segments"
> 
> Seems to be a limit around 4700 segments or so.
> 
> Can aything be done about that, or do I need to just work with smaller
> files and then join the tmx-s with omegaT?

Admittedly, some work needs to be done to deal with large input files.

For now, the first thing you can try is to increase the memory to the application
at startup. To do this you have to start the application from the command line
and give some options to Java.

What you need to understand is that when you run bitext2tmx(B2T), or any other Java
application, it usually starts with a set amount of memory that it can use. Once that
runs out, then the application cannot do anything more. In the case of B2T, it is just
using the default memory values. Depending upon your operating system, this is
probably about 32 or 64MB. So you need to put it up to 128MB (256MB) or more.

From the command line, for 128MB maximum memory, enter:

java -Xmx128M -jar bitext2tmx-<version>.jar

where <version> depends on which release of B2T you are using. The -Xmx
argument is the memory option, with its value here at 128MB.

If this works for you, and you want to keep using more memory each time you
use B2T, just put that command in the shell script(batch file) that came with
B2T (bitext2tmx.sh, bitext2tmx.bat) and you won't have to enter it every time.
Just start B2T with the shell script instead (this also works by mouse clicking under
certain systems).

Other than that, you will have to break up your input into chunks. Note that increasing
the memory should just move the upper limit of the number of segments up in step with
the amount of memory. Thus, doubling the memory will roughly correspond to B2T being
able to handle twice as many segments before it vomits on more input.

As for connecting the TMXs afterward in OmegaT(OmegaT+), those applications really
do not do that for you, unless you go through one segment at a time to have all the
segments added to the project TMX. Maybe you know that. If you end up with multiple
TMX, instead of a single one, as an external TMX to use in those applications. you can
easily edit them by hand to create a big one. Just put all the <tuv> segments from one
TMX into the other at the end, but before the last two tags (</body></tmx>).

Note that even OmegaT(OmegaT+) has problems currently with a large number of input
segments. It is not as apparent as in B2T, due to different code, but there is an upper limit
around 10000 segments that really slows down the loading of a project, and requires more 
memory(~256MB). Thus these applications will not scale to projects with 25k-50k segments
without severe memory usage (1GB) by the program itself. You just have to create smaller
projects, with less files in that case.

I hope that helps, but I can't say that I have tested it myself. Let me know if the problem
persists even with more memory.

You can join the Yahoo bitext2tmx users group if you want to discuss B2T issues - 
http://groups.yahoo.com/group/bitext2tmx

Regards,

Raymond Martin

[Bitext2tmx-devel] Fwd: bitext2tmx

[Mikel L. F. <ml...@dl...>]

Hi there,
I got this message grom Andreas Jonson, but I don't know how to help.
Raymond, Sergio, can you please? Andreas is not on the list; please
make sure you CC: him.

Thanks a lot

Mikel

---------- Forwarded message ----------
From: Andreas Jonson <And...@te...>
Date: 18/04/2008 08:42
Subject: bitext2tmx
To: ml...@ua...




Hello,

Thank you for your excellent effort with bitext2tmx!

However: I have a problem:


When trying to open two large files i get the error
"insufficient memory to continue processing segments"

Seems to be a limit around 4700 segments or so.

Can aything be done about that, or do I need to just work with smaller
files and then join the tmx-s with omegaT?


Sincerely
/Andy

-- 
Mikel L. Forcada                    E-mail: ml...@dl...
Departament de Llenguatges          Phone: +34-96-590-9776
i Sistemes Informàtics                also +34-96-590-3772.
UNIVERSITAT D'ALACANT               Fax:   +34-96-590-9326, -3464
E-03071 ALACANT, Spain.

URL: http://www.dlsi.ua.es/~mlf

[Bitext2tmx-devel] RPM for bitext2tmx 1.0M0 (build 080229) available now

[Raymond M. <la...@gm...>]

Hi,

Just made a preliminary RPM for B2T.

Sorry, no desktop/menu entries for easy launch yet. You can just make one yourself
and point it at 'bitext2tmx' which should work from anywhere (as long as /usr/local/bin
is your path). Of course, bitext2tmx should launch from any console too.

Cheers,

Raymond

bitext2tmx: bitext aligner/converter to TMX - http://bitext2tmx.sourceforge.net

[Bitext2tmx-devel] bitext2tmx 1.0M0 (build 080229) released

[Raymond M. <la...@gm...>]

Hi,

bitext2tmx 1.0M0 (build 080229) has been released.

Replaces build 080218, which had a license violation in an included library
(MRJAdapter). Library has been replaced with GPL code I wrote.

Also, there were some extra files/libraries included that were not used and have
now been removed.

Code has been committed to CVS and packages released (bz2, gz, and 7z
currently; OS X dmg & RPM still to come).

In addition, Subversion has been enabled and I will get the code/libraries
into that in the near future.

Cheers,

Raymond

[Bitext2tmx-devel] bitext2tmx 1.0M0 temporarily removed

[Raymond M. <la...@gm...>]

Hello,

I have temporarily removed bitext2tmx 1.0M0 packages from 
distribution.

There is a GPL violation in one of the included libraries that has 
caused me to do so. This has been done as a precaution to protect 
user's right and freedoms when expecting to be able to use the 
application under the GPL free software license.

I am currently in the process of righting code to replace the 
offending portions. The code I am writing functions to a degree, but 
needs a little further testing. Hopefully, I will be able to have 
new packages up in the near future (later today is likely).

In the interim, to protect users interests, please do not use the 
1.0M0 version, or distribute it. A proper replacement is coming.

Also note, users of OmegaT+ and OmegaT are also using software that 
violates the GPL and possibly other free software licenses. Please 
refrain from using those software until the situation has been 
remedied. In the case of OmegaT+, the same code I am writing for 
bitext2tmx is to be in there also, that will be fixed around the 
same time as B2T.

As for OmegaT, they have been notified of the situation. Thus, far 
they have not taken the appropriate actions to remedy the situation 
for their users and there is no sign that they intend to take the 
proper steps as far as I know.

Regards,

Raymond

Re: [Bitext2tmx-devel] 1.0M0 CVS commit

[Mikel L. F. Z. <ml...@dl...>]

Raymond,

> > I vote in favour of moving to subversion. Perhaps you can move the stuff
> > just before the commits that generated the empty directories, and do the
> > commit later. Does that sound OK?
> 
> Not sure I understand.

Don't worry.
> I have already put the code in. So we can start in subversion fresh with 1.0M0,
> if that is what you mean.

No, but that's close enough. Let's work on that.

> As for CVS, are you saying that directories can be moved? I'm not sure if
> you can do that, haven't done it myself. I'll look at the documentation to
> see if it is possible.

Not sure myself either. I would also have to look at the docs.

Mikel


> 
> Later.
> 
> Raymond

Re: [Bitext2tmx-devel] 1.0M0 CVS commit

[Raymond M. <la...@gm...>]

Hi Mikel,

On 25 February 2008 10:17:31 you wrote:
> I vote in favour of moving to subversion. Perhaps you can move the stuff
> just before the commits that generated the empty directories, and do the
> commit later. Does that sound OK?

Not sure I understand.

I have already put the code in. So we can start in subversion fresh with 1.0M0,
if that is what you mean.

As for CVS, are you saying that directories can be moved? I'm not sure if
you can do that, haven't done it myself. I'll look at the documentation to
see if it is possible.

Later.

Raymond

Re: [Bitext2tmx-devel] 1.0M0 CVS commit

[Mikel L. F. Z. <ml...@dl...>]

I vote in favour of moving to subversion. Perhaps you can move the stuff
just before the commits that generated the empty directories, and do the
commit later. Does that sound OK?

Mikel

El dl 25 de 02 del 2008 a les 06:51 -0500, en/na Raymond Martin va
escriure:
> Hi,
> 
> I have finally committed the 1.0M0 code to CVS.
> 
> Unfortunately, I made a little mess in the process. Haven't used CVS in a while.
> I cleaned it up, but CVS won't let me delete directories. My apologies for that.
> 
> Just make sure to use the -P option when doing a checkout or update, to avoid getting
> any empty directories.
> 
> Can we please consider moving to Subversion so that we may have better functionality.
> I would like to do this before the final 1.0 version.
> 
> There is an online version of the O'reilly Subversion book over here -> http://svnbook.red-bean.com
> in case anyone needs a good reference.
> 
> Please let me know if there are any problems. I will fix them as soon as possible.
> Sorry again for the mess.
> 
> Regards,
> 
> Raymond
> 
> P.S. I have tagged the errors with "Removed due to error - duplicate".
> Things that were removed to make way for new versions are tagged
> as "Removed for 1.0M0". You won't see these comments unless you look
> at the dead files. Clear enough, I hope.
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Bitext2tmx-devel mailing list
> Bit...@li...
> https://lists.sourceforge.net/lists/listinfo/bitext2tmx-devel

[Bitext2tmx-devel] 1.0M0 screenshots added

[Raymond M. <la...@gm...>]

Hi,

I have added a few screenshots to the project.

One with it at work on two text files, another with it working on a TMX, and
a last one with it just blank, nothing open.

Cheers,

Raymond

[Bitext2tmx-devel] 1.0M0 CVS commit

[Raymond M. <la...@gm...>]

Hi,

I have finally committed the 1.0M0 code to CVS.

Unfortunately, I made a little mess in the process. Haven't used CVS in a while.
I cleaned it up, but CVS won't let me delete directories. My apologies for that.

Just make sure to use the -P option when doing a checkout or update, to avoid getting
any empty directories.

Can we please consider moving to Subversion so that we may have better functionality.
I would like to do this before the final 1.0 version.

There is an online version of the O'reilly Subversion book over here -> http://svnbook.red-bean.com
in case anyone needs a good reference.

Please let me know if there are any problems. I will fix them as soon as possible.
Sorry again for the mess.

Regards,

Raymond

P.S. I have tagged the errors with "Removed due to error - duplicate".
Things that were removed to make way for new versions are tagged
as "Removed for 1.0M0". You won't see these comments unless you look
at the dead files. Clear enough, I hope.

[Bitext2tmx-devel] B2T 1.0M0 CVS commit

[Raymond M. <la...@gm...>]

Hi,

I was about to commit the 1.0M0 code to CVS.

Looking at it I noticed that there is some code in another branch (newaligner) that I missed
for inclusion into M0. Guess I will have to make another release with that included
before I can get back to M1 development.

Right now I am wondering whether to create a new branch for 1.0 or each of M0, M1, ..
Or just put the code straight into the HEAD.

If there aren't any preferences I will put this latest version into HEAD, since the
1.0 will become the official version eventually. Just note that I have changed some
things around (the B2T jar has a build number as part of its file name (until official
1.0 is released), Ant build file is changed, not to mention some code).

I'll hold off committing until tomorrow. Let me know if there are any problems
with my approach for any of you.

Thanks.

Raymond

Re: [Bitext2tmx-devel] bitext2tmx experimental release on OmegaT+

[Raymond M. <bio...@ya...>]

Hi Mikel,

> > 
> > Seems we are still up in the air with this then. I believe that the work I am going 
> > to do will have more significant changes than perhaps the project will be willing 
> > to merge into the official version. 
> 
> Raymond, you are the only one working on it now. Let's make your version
> the official one. Whoeever wants to trace changes can use the "time
> machine" built into CVS.

Sounds great and definitely makes my work easier.

> I think your versions could be called bitext2tmx-1.0-RC1, -RC2, etc. (no
> -exp) so that they are considered precursors of the official version.
> Using the -RCn flag visualizes progress.

Okay, that is better and more clear for users.

> > I could go with 0.99 as you suggest. That might be what I do if my version could 
> > eventually become the official one. Then there would be no need for a 1.0-exp,
> > the 1.0 version would be enough. Depending on what others want to do, I may have 
> > to consider giving my version a different name at some point. Things are still a 
> > little mixed up. Hopefully everybody else can weigh in on these possibilities 
> > before I make a final decision.
> 
> Do you feel comfortable with bitext2tmx-1.0-RC1, etc.? Then go for it.

Alright, I will do something along that line.

> > Others can always pick and choose what
> > they want from my version and put that in the current official version.
> 
> Or make experimental versions out of your version if it is the official
> one.

Exactly.

Is anybody else going to give some feedback on this matter?
I'll wait for more comments if that is the case.

Not sure about the time frame for getting something ready. I can pretty much start
working on it right away.

More later...

Raymond

Re: [Bitext2tmx-devel] bitext2tmx experimental release on OmegaT+

[Mikel F. Z. <ml...@dl...>]

Hi Raymond,

> She had made it possible to reload work from a TMX. That will be there.

Excellent.

> 
> Seems we are still up in the air with this then. I believe that the work I am going 
> to do will have more significant changes than perhaps the project will be willing 
> to merge into the official version. 

Raymond, you are the only one working on it now. Let's make your version
the official one. Whoeever wants to trace changes can use the "time
machine" built into CVS.

> One reason I wanted to settle on exactly what
> version number to use.
> 
> I was thinking of bitext2tmx-1.0-exp as the final version, after going through
> preliminary release candidates, e.g. bitext2tmx-1.0-RC1-exp, and so forth.
> The idea is to differentiate it from bitext2tmx proper because it won't be the
> official version. 

Or it will.

> A question here is whether it could ever become the official
> version. Is there any more work going to be done by others? 

As I have said above, not much. 

> If not, would
> others just like to keep the official version as is or could my version take its
> place (after it is shown to be of good quality)?


I think your versions could be called bitext2tmx-1.0-RC1, -RC2, etc. (no
-exp) so that they are considered precursors of the official version.
Using the -RCn flag visualizes progress.

> I could go with 0.99 as you suggest. That might be what I do if my version could 
> eventually become the official one. Then there would be no need for a 1.0-exp,
> the 1.0 version would be enough. Depending on what others want to do, I may have 
> to consider giving my version a different name at some point. Things are still a 
> little mixed up. Hopefully everybody else can weigh in on these possibilities 
> before I make a final decision.

Do you feel comfortable with bitext2tmx-1.0-RC1, etc.? Then go for it.

> Just note that whatever work I do on a version, I cannot go to the effort to merge
> my changes back into the official version. There are just too many things that I 
> am going to change. It would basically just be a mess and a nightmare to try and 
> make it work. It would be easier to take my version and put other changes into 
> it and make that the official version. 

I agree.

> Others can always pick and choose what
> they want from my version and put that in the current official version.

Or make experimental versions out of your version if it is the official
one.

> Whatever the case, bitext2tmx will be moving forward in one way or another.

That is good!

Thanks

Mikel