[ omegat-Feature Requests-3440267 ] Display encoding and filter used in list of project files

[SourceForge.net <no...@so...>]

Feature Requests item #3440267, was opened at 2011-11-19 07:38
Message generated for change (Comment added) made by didierbr
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=520350&aid=3440267&group_id=68187

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: OmegaT Application
Group: 2.6
Status: Open
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Guido Leenders (guido_leenders)
Assigned to: Martin Fleurke (martinfleurke)
Summary: Display encoding and filter used in list of project files

Initial Comment:
I work with various translators, not all experienced OmegaT or even Trados users. When translating text with a technical origin (user interface labels) instead of marketing stories, they are often confused.

One of the issues frequently coming back is character set encoding and filter applied. Through procedures and instructions I have been able to reduce the problems.

But I would like to suggest a change to make it easier for people to understand what is happening.

The project files list currently describes the filename and the number of segments.

It would be great if the column list could be extended by:

1. Characters set encoding determined by OmegaT (for text files, such as XML, HTML, etc).
2. Filter used (for instance, based upon configuration various filters might work for HTMLO or XML).
3. Number of words in the segments.
4. Number of characters in the segments.

And totals on number of words and characters as with Segments.

----------------------------------------------------------------------

>Comment By: Didier Briel (didierbr)
Date: 2012-09-14 06:19

Message:
>encoding info for XML parser is fixed. Can you test it?

It still doesn't work in all cases. For DocBook, it works, but for OpenDoc
or OpenXML I got "OpenDoc" or "OpenXML" as the encoding.

Didier

----------------------------------------------------------------------

Comment By: Martin Fleurke (martinfleurke)
Date: 2012-09-14 03:06

Message:
encoding info for XML parser is fixed. Can you test it?

Documentation: The character encoding used for a specific file, and the
filter used are now shown in the filelist.
Number of words/chars have NOT been added. Please add a new Feature request
for those if they are still required.

----------------------------------------------------------------------

Comment By: Jean-Christophe Helary (brandelune)
Date: 2012-09-13 10:25

Message:
It looks like the encoding info is not properly acquired. See screenshot.

----------------------------------------------------------------------

Comment By: Didier Briel (didierbr)
Date: 2012-09-13 09:57

Message:
Fixed in SVN (/trunk).

Didier

----------------------------------------------------------------------

Comment By: Guido Leenders (guido_leenders)
Date: 2011-11-19 07:38

Message:
Character set encoding and filter used might also be displayed when working
on a file in the bottom right corner.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=520350&aid=3440267&group_id=68187