Trados Business Manager
Speech to Text
Managed Translation - Enterprise
Translation Management Connectors
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
Internal Trados Ideas Community
RWS Community Internal Group
RWS Access Customer Portal
RWS Professional Services
RWS Training & Certification
RWS Enterprise Technology Partners
Trados Academic Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic Tridion Docs User Group
Tridion Docs Europe & APAC User Group
Tridion UK Meetup
Tridion User Group Benelux
Tridion User Group New England
Tridion User Group Ohio Valley
Tridion West Coast User Group
WorldServer User Group
Trados GroupShare Ideas
Trados Studio Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
RWS Language Cloud TMS Ideas
RWS Language Cloud Terminology Ideas
RWS Language Cloud Online Editor Ideas
Managed Translation - Enterprise Ideas
Tridion Docs Ideas
Tridion Sites Ideas
LiveContent S1000D Ideas
Events & Webinars
To RWS Documentation
To RWS Support
Detecting language please wait for.......
We would like to use Target Word Count for calculating the lines in the target version for certain file types.
Calculating by word works fine, but if we tick the "Calculate by line" box, only the segments are counted; no characters and consequently no lines show up in the report. It doesn't matter if we fill the box for "Characters per line" or tick "Include spaces".
Can anyone help?
Thank you for your findings.
We see from your comments inconsistencies based on how your project was initiated.If you "Translate Single Document", it seems the findings in the report are minimal and lacking, despite as you say you enable "Calculate by line"
This has been logged for improvement under SDLCOM-3048
The short term work around to this problem is: if you create a Project in Studio using the Project Wizard/with a template (optional) - you get a correct report output.
Thanks for the quick reply.
We always use projects, so this alone can't be the reason why it's not working. I experimented a little bit and it seems that the report only works when I create a project using the Default template.
We can make it work this way, but it would be great if at some point it would work for all projects.
I was too quick there; now the report doesn't work with the Default template either and even the project that just a few minutes ago produced the correct report now comes up with zeros only.
I guess we'll have to find a different solution.