CafeTran Installation
Igor Kmitowski
To facilitate the installation and running the program depending on
the operating system I uploaded two new versions of CafeTran Espresso
for Mac OS X and Windows systems. The Mac OS X version is now packed
as the Mac application CafeTran.app. The Windows version has its own
installer to create a shortcut in the Desktop. The trial versions are
available for download at http://www.cafetran.com/download.html
Cheers,
Igor
--
Igor Kmitowski
Translator and Java developer
CafeTran website: http://www.cafetran.com
CafeTran support: cafetran...@gmail.com
Dominique Pivard
Hi Igor,
> To facilitate the installation and running the program depending on
> the operating system I uploaded two new versions of CafeTran Espresso
> for Mac OS X and Windows systems. The Mac OS X version is now packed
> as the Mac application CafeTran.app. The Windows version has its own
> installer to create a shortcut in the Desktop. The trial versions are
> available for download at http://www.cafetran.com/download.html
Just to confirm the new versions installed fine under both OS X and Windows.
On my Mac, I just moved the app file to the Application folder. I
suppose it's the standard way to deal with applications in OS X,
right, Mac people? It's nice to have a single file that can be clicked
to start the application, as opposed to a folder full of files. The
'About CafeTran' command is still located under the "wrong" menu, but
you perhaps didn't intend to fix that yet? Does it make any difference
whether the Mac version of CafeTran is distributed as a ZIP or as a
DMG (it's a question to Mac users)?
In Windows, I was surprised to see "C:\CafeTran Espresso 2012" was the
folder proposed by default? Why not use "C:\Program files" or
"C:\Program files (x32)", which is the "normal" location for
applications in the Windows world? Anyway, I used "C:\Program files
(x32)", which worked fine, except for the warning that directory
wasn't empty (but it wasn't a problem since CT creates its own
folder).
Cheers,
Dominique
Hans List
On Jan 21, 2012, at 3:35 PM, Dominique Pivard wrote:
>
>
> Just to confirm the new versions installed fine under both OS X and Windows.
>
> On my Mac, I just moved the app file to the Application folder. I
> suppose it's the standard way to deal with applications in OS X,
> right, Mac people?
Yäp!
> It's nice to have a single file that can be clicked
> to start the application, as opposed to a folder full of files.
Hihi, actually it is a folder.
> The
> 'About CafeTran' command is still located under the "wrong" menu, but
> you perhaps didn't intend to fix that yet? Does it make any difference
> whether the Mac version of CafeTran is distributed as a ZIP or as a
> DMG (it's a question to Mac users)?
DMG is more common but ZIP is not a problem IMO.
>
> In Windows, I was surprised to see "C:\CafeTran Espresso 2012" was the
> folder proposed by default? Why not use "C:\Program files" or
> "C:\Program files (x32)", which is the "normal" location for
> applications in the Windows world?
Not per se. E.g. Transit NXT (there he is again with that funny software) should not be installed in c:\prog_etc. in Win Vista (access rights).
BTW: Didn't I tell you that Transit NXT won't accept migration to a new Mac just be moving the Parallels VM to the new Mac?
It was indeed 'Locked' as soon as I started it. Luckily I could get a new license from the Activation server. After the setup routine was completely run again (which almost caused a heart attack). Okay, everything works now. Must ask my friend Igor (hi) for a new license for CT too.
Selcuk Akyuz
Is this a new build, e.g. does it include the latest changes in the
docx filter and additional fields for glossary?
Kind regards,
Selcuk
Igor Kmitowski
>
> On my Mac, I just moved the app file to the Application folder. I
> suppose it's the standard way to deal with applications in OS X,
> right, Mac people? It's nice to have a single file that can be clicked
> to start the application, as opposed to a folder full of files. The
> 'About CafeTran' command is still located under the "wrong" menu, but
> you perhaps didn't intend to fix that yet?
Not yet. I will try to set it in both places for the next major version.
> In Windows, I was surprised to see "C:\CafeTran Espresso 2012" was the
> folder proposed by default? Why not use "C:\Program files" or
> "C:\Program files (x32)", which is the "normal" location for
> applications in the Windows world? Anyway, I used "C:\Program files
> (x32)", which worked fine, except for the warning that directory
> wasn't empty (but it wasn't a problem since CT creates its own
> folder).
There are some writable settings in the CT installation folder, and the
Program files filer may have access restriction to prevent writing there.
So I decided to put it in C:\ by default. However, if there are no folder
administration issues on your system, you can install it in the Program
files folder.
BR
Igor Kmitowski
The build (2012011901) is new with some improvements to the docx filter,
namely, recognition of strikethrough, highlight, caps, small caps
formatting and better handling of a hidden text.
As for the tab delimited glossaries, I also improved displaying of
multiple fields.
I don't want to bother users with so frequent updates. I think once or
twice a year is a good practice. However, if anybody feels that this
update can affect his or her workflow and comfort, please download the
latest trial and contact me to update to the full version.
Cheerio,
Igor
Igor Kmitowski
> Program files filer may have access restriction to prevent writing there.
Igor
> --
> Igor Kmitowski
> Translator and Java developer
> CafeTran website:http://www.cafetran.com
Jean-Christophe Helary
On Jan 21, 2012, at 11:42 PM, Hans List wrote:
>> Does it make any difference
>> whether the Mac version of CafeTran is distributed as a ZIP or as a
>> DMG (it's a question to Mac users)?
>
> DMG is more common but ZIP is not a problem IMO.
There are a number of UI issues with DMG. Some users don't realize that DMGs are only virtual disks that get mounted and unmounted and that if you don't move their contents to a place on the disk then it is not going to be "installed".
That is the reason why OmegaT choose ZIP instead. With ZIP, OSX automatically creates a container folder where all the data is. Wherever it is unpacked, it can be considered "installed".
Jean-Christophe Helary
----------------------------------------
fun: http://mac4translators.blogspot.com
work: http://www.doublet.jp (ja/en > fr)
tweets: http://twitter.com/brandelune
Dominique Pivard
Hi Igor,
> There are some writable settings in the CT installation folder, and the
> Program files filer may have access restriction to prevent writing there. So
> I decided to put it in C:\ by default. However, if there are no folder
> administration issues on your system, you can install it in the Program
> files folder.
Actually, I noticed it's not such a good idea to install CT in
"c:\program files (x86)", even if I have administrator rights and
installation there is possible. This is because CT keeps its resources
folder there as well. After having created a new TM, for instance, I
wasn't able to save it, most likely because Win 7 doesn't grant write
rights to applications, even if the user is logged with administrator
rights. So I will reinstall to c:\programdata, which has no such
issues.
Btw, do I understand correctly that when creating a project TM (by
ticking 'New memory', in the Project manager window), a file is
automatically created and saved on disk (in the same folder as the
project's document). But when creating a new TM later on, via the
Memory > New memory menu, that TM is not automatically saved on disk,
ie. everything remains in RAM; only if/when the user selects Memory >
Save memory (or Save memory as) does the TM actually gets saved on
disk (by default, in the 'memories' folder, under 'resources'), right?
Cheers,
Dominique
Dominique Pivard
Hi Igor,
> I don't want to bother users with so frequent updates. I think once or twice
> a year is a good practice.
Actually, I think that the very small size of CT would make it an
ideal candidate for frequent updates and rapid development. A bit like
what Yves Champollion is doing with Wordfast Classic: he (nowadays)
has public releases that only change once or twice a year, but beta
releases that come out very often (sometimes several releases during
the same week). There's a separate beta list for people who are
interested in using and testing the latest stuff.
But I understand your current licensing scheme (a new .jar not
included in the distribution has to be copied separately) makes
frequent updates very tough. If/when you manage to sell thousands of
CT licenses, it will be very hard to keep things manageable. So you
should consider a licensinhg scheme similar to what other products are
using, ie. once installed and licensed on a given computer, the
installation survives updates.
Cheers,
Dominique
Igor Kmitowski
> Btw, do I understand correctly that when creating a project TM (by
> ticking 'New memory', in the Project manager window), a file is
> automatically created and saved on disk (in the same folder as the
> project's document).
Yes, this memory called ProjectTM.tmx always opens automatically with the
project and can also be used/shared in other projects if you place it in
the same folder as project's .xlf file.
> But when creating a new TM later on, via the
> Memory > New memory menu, that TM is not automatically saved on disk,
> ie. everything remains in RAM; only if/when the user selects Memory >
> Save memory (or Save memory as) does the TM actually gets saved on
> disk (by default, in the 'memories' folder, under 'resources'), right?
Right, but after 10 segments (see Edit | Options | Workflow tab | Autosave
memory) CT will pop-up the Save Memory window to remind you of saving. If
you skip this window without saving, this memory will be only in RAM
(temporal memory).
Igor Kmitowski
> included in the distribution has to be copied separately) makes
> frequent updates very tough. If/when you manage to sell thousands of
> CT licenses, it will be very hard to keep things manageable. So you
> using, ie. once installed and licensed on a given computer, the
> installation survives updates.
Yes, the updating scheme will have to change in future to make it more
comfortable. The modern solution is a License server but I am also
considering moving the activation to another file without the need to
reinstall the whole thing. The last update was a special case because it
featured an installer and different packaging so there was no other way
but to reinstall the program.
Igor
Selcuk Akyuz
Selcuk
Hans List
On Jan 22, 2012, at 1:27 PM, Selcuk Akyuz wrote:
> I am always ready to test beta builds.
>
Hi Selçuk,
Are you already using CT for Turkish > English? What do you think of:
• Prefix matching
When this option is selected, CafeTran will analyze the beginnings of words (here called prefixes) and discard any endings responsible for inflection of words. It is an option which increases significantly the number of hits for highly inflected languages. The length of prefixes is set by a percentage number. The bigger the percent number the longer the prefix of words which the program will analyze. The minimal prefix length option (menu Edit | Options | Memory | Minimal prefix length) lets you set the minimal allowed length of prefixes. The length can also be fixed, when the "fixed" option selected, instead of a set percentage length. It means that all the words will have the minimal prefix length, no matter their actual length.
• Custom prefixes
If the inflection of a word is too high for automatic prefix matching you can enter your terms to the memory determining the prefix of a word manually. This is done by inserting the pipe character | at the end of a prefix in a word. For example, the Polish phrase "piękny dzień" (a beautiful day) has a highly inflected word "dzień" occuring in a number of various cases (dnia, dni, dniom). If you insert the pipe characters at the following positions - "pięk|ny d|zień", CafeTran will also recognize other forms of the phrase (pięknego dnia, pięknych dni etc.). Note that inserting the pipe character at the first word in the phrase - "pięk|ny" is optional since its inflection is quite regular and CafeTran should recognize its prefix automatically.
Is it good for Turkish?
Same question to Dominique, please read Finnish for Turkish here ;).
Hans
Selcuk Akyuz
As I have stated in the other thread, I translate into Turkish only.
But both Prefix Matching and Custom Prefixes should work in Turkish
into other languages.
At the moment I am just testing the filters, I did not use CT in real
projects.
Selcuk