Hi Carmen,

No it doesn't... but there is an app on the OpenExchange called StudioInQuote which allows you to report with standard lines.  This gives you the ability to report keystrokes, which is essentially character count plus spaces.

The good thing about this app is it's free and it uses the analysis from your Studio Project, and you can also customise the reporting into Word or Excel if you like so it's a format ready for use with your clients.  You can find a help guide to this app here if you want to see how it works?

Regards

Paul

Hi Carmen,

Most likely reason, as I came across this myself when I reminded myself how this app works are these:

1. You need to have run an analysis first, not just a wordcount, and
2. You must check the format (word, excel, clipboard) AND the template type

Then you should get proper counts.

See if that helps?

I would also add that we have an action to redo this application as a integrated view in Studio with better functionality. So if you have any ideas for this once you start using it I'd be glad to hear them. You can post them in here : http://community.sdl.com/appsupport

Regards

Hi Carmen,

It can count whatever you like :-)  If you use this setting for example:

You can get a report showing this for example:

This is a default and a quick solution would be to make the numbers for a standard line "1".  This was you would see this:

So the 3497 would be the count including spaces in this case.

A better solution of course would be to create your own custom template and use an appropriate field value to pull the chars directly.  I have loaded the list of tokens referred to in the help to drop box too, so you may be able to create your own template with this.  Having said that, something doesn't quite look right to me at the moment in how this is working so I'm going to add this to the development item we have on our list to make sure this is all working properly.  Once it's done I'll write something up to explain how it all works and provide an example of how to do this.

In the meantime maybe you can use the workaround to get your count, or even have a play with the fields and see what you come up with.  Sorry this isn't a better solution at then moment.  I think this app has good potential, but needs a few loose ends tidying up.

Regards