This site uses cookies.
Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
For more information, please see the ProZ.com privacy policy.
I'm currently trying to make Heartsome CAT work for me. The problem I'm having is that the segments not located at the start of a paragraph have an extra leading space. I've tried selecting OmegaT and LanguageTool SRX files instead of the default ones, but then the source file gets segmented by paragraphs only. Meanwhile, if I select a presegmented SDLXLIFF file from a Studio project, the resulting Heartsome XLIFF file doesn't have the extra leading spaces.
I'm currently trying to make Heartsome CAT work for me. The problem I'm having is that the segments not located at the start of a paragraph have an extra leading space. I've tried selecting OmegaT and LanguageTool SRX files instead of the default ones, but then the source file gets segmented by paragraphs only. Meanwhile, if I select a presegmented SDLXLIFF file from a Studio project, the resulting Heartsome XLIFF file doesn't have the extra leading spaces.
That's not a problem. That is how it is meant to be.
The space at the beginning of a segment is there because you are dealing with a western language and there actually is a space between two sentences in the source document. If you translate into Chinese, for example, you will not put that space in the target text. If you translate into French for Canada, you might want to put two spaces instead of one.
You can use a custom SRX file and send the space to the skeleton (... See more
That's not a problem. That is how it is meant to be.
The space at the beginning of a segment is there because you are dealing with a western language and there actually is a space between two sentences in the source document. If you translate into Chinese, for example, you will not put that space in the target text. If you translate into French for Canada, you might want to put two spaces instead of one.
You can use a custom SRX file and send the space to the skeleton (the ones you tried are not good examples). It is easy to do but it is really a bad idea.
How do I send the space to skeleton and what are good examples?
Feb 8, 2019
Rodolfo Raya wrote:
That's not a problem. That is how it is meant to be.
The space at the beginning of a segment is there because you are dealing with a western language and there actually is a space between two sentences in the source document. If you translate into Chinese, for example, you will not put that space in the target text. If you translate into French for Canada, you might want to put two spaces instead of one.
You can use a custom SRX file and send the space to the skeleton (the ones you tried are not good examples). It is easy to do but it is really a bad idea.
Regards, Rodolfo
Thank you for your comment, Rodolfo! Strange, I haven't ever encountered segments with a leading space in the editor view inserted by default in any other CAT tool I've tried. How do I send the space to the skeleton then? And what are good examples of SRX files in this case?
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Manage your TMs and Terms ... and boost your translation business
Are you ready for something fresh in the industry? TM-Town is a unique new site for you -- the freelance translator -- to store, manage and share translation memories (TMs) and glossaries...and potentially meet new clients on the basis of your prior work.
Create your account in minutes, and start working! 3-month trial for agencies, and free for freelancers!
The system lets you keep client/vendor database, with contacts and rates, manage projects and assign jobs to vendors, issue invoices, track payments, store and manage project files, generate business reports on turnover profit per client/manager etc.