Well, I'm not a tech ...
Well for a non-tech user, you seem pretty tech-savvy to me, with excellent insights and ideas for making CT better :-) I had already checked out your CafeTran-related posts in Japanese (using machine translate) and I will definitely explorer it more in the future. I can definitely be a penny donator and give my to cents !
I started using Macs in 1987, had to switch to Windows when I started translating in 1994. [...] So I switched to CT because of the Mac, not the other way around.
Since CafeTran can be used on Windows, Mac and GNU/Linux, I did not mean it as an argument exclusively in favor of a Mac, but it makes it more possible and enjoyable to be a translator on Mac or GNU/Linux, and to helps to make the switch.
And anyway, you could not have switched to Mac because of CT since CT wasn't around when you started using Macs!
DRM vs privacy
DRM is an extremely flawed way to tackle the "intellectual rights" problem in many many ways. It gives control to Amazon or Apple to delete things off your device, so you cannot say that you are the one in full control of your data. And it is not a wonder many publishers that were using DRM start to offer DRM-free ebooks etc. Lulu.com for example. Even Apple stopped selling its music with DRM protection (5 computers authorization limit), before reimplementing it in another way through Apple Music subscriptions.
Check out https://fsfe.org/activities/drm/drm.en.html or http://drm.info/ but I don't want to get into a pro/against DRM discussion. There is no such thing as good DRM and if there is, I don;t want to hear about it. Not for my data and on my computer anyway. And saying that you have choose to also have an iPad etc. to get around the DRM problem when using mobile devices confirms the argument about Apple offering tight digital handcuffs.
I'm pretty much in control of my machinery and software, thank you
I'm sure you know your way around your Mac and are very competent in using it to boost your productivity. I talk about a bigger picture control, that includes proprietary software (you don't and can't know what a proprietary program exactly does. How on earth can you have full control of your computing then? And I'm not the only one to be extremely concerned from NSA's revelations).
Again, I did not want to start a discussion on Apple against Linux or OS X against GNU/Linux. I am as much a happy GNU/Linux user as you are a Mac user, and I have as many arguments and experiences in favor of choosing GNU/Linux, but that's not the point.
it's not about what is better in general, just what works best for you, when you take all the things that matter to you into consideration.
I just wanted to point there is a third option, besides "I'm a Mac, I'm a (Windows) PC". And CT makes the choice of choosing GNU/Linux (as well as Mac) a lot easier and viable. Peace!
Thank you for visiting my site. I'm afraid that when machine-translated, some pages did not have a neat and readable layout. How did they look?
A plan has long been in my mind to make it Japanese/English bilingual ... but no time to do it now.
Wow, nice posts!
Here an ex linux user/(still lover) for more than 9 years. I knew CT because I got offered a Macbook Pro as a present and was looking for an alternative.
Finally came back to Windows 10 (just 2 years ago) and I can't be happier. The more I read about Virtualbox, Wine, Libreoffice... the happier I am actually :P.
There seems to be strict rules about splitting/joining segments of a Studio file (sdlxliff). CT can import this type of file directly, but cannot split/joint segments.
Also note that not all segments can be joined/split even with Studio itself, even when they are not properly segmented.
The following are the ways to "virtually" split/join segments.
A. Virtually splitting a segment:
Select each of the parts that should have appeared as separate segments, and add the translation separately to a TM.
Note that this feature of adding "a portion of the source segment" to a TM is unique to CT, and should be very useful when you have to work with "ill-segmented" files (often sent from your clients (?)).
B. Virtually joining segments:
The next segment's translation should be a white space etc.