Hi Reynir Gunnlaugsson 

Unfortunately the advice you are receiving is based on something that was never intended in the first place, so it's not surprising it doesn't work.  There are apps that can search in tags, such as the SDLXLIFF Toolkit, but even this will only find tag content in exposed tags.  If the italic controls have been moved externally, as they have in your case then there is no way to use them at all.

Perhaps a possible solution for your very specific case would be this.

1. Hide all the columns that are not italic in Excel
2. Create a new TM and open the file in Studio
3. Copy source to target for everything and update the TM
4. Close the file and now take the original Excel file, with no hidden content, in a proper project for the file
5. Don't do any pretranslation on this file yet so ensure it is empty and nothing has been translated
6. Add the TM you created in 2.
7. Pretranslate the file and then filter on all translated segments, and lock them
8. Then remove the temporary TM and translate the rest of the file as normal with your real TM

Or maybe do the easy thing to solve your problem and just hide the columns with the Latin Text in Excel and translate the file without this text at all.  Wouldn't that be easier?

Regards

Paul

Reynir, I proposed adding a function allowing segments to be filtered by color nearly a year ago, in May 2017. You can upvote the suggestion here if you like.

Dan

Reynir, I proposed adding a function allowing segments to be filtered by color nearly a year ago, in May 2017. You can upvote the suggestion here if you like.

Dan

Hi Dan,

I believe that the Community Advanced Display Filter plug-in has already got your awaited feature. Check it up in the Colors tab

Thank you for the pointer Jesus. I tried that in February and found that it simply did not work, as detailed in this topic. (It may, however, work for others in different language pairs.)

My understanding is that SDL is looking at the problem. It has been noted by SDL that development of the plug-in was more challenging than originally expected, and I suspect that is an issue - fixing it may require more resources than they can justify committing.

Regards,

Dan

Unknown said:

Thank you for the pointer Jesus. I tried that in February and found that it simply did not work, as detailed in this topic. (It may, however, work for others in different language ptagsairs.)

Indeed.  It has nothing to do with language pairs and everything to do with where the colours are set.  So for internal tags the plugin will work.  For external tags it will not and this is the problem.  Getting the information for these colours using the APIs is currently not possible and this is an open source plugin.  The same would apply to other formatting if we were to enhance the plugin to support bold, italic, underline etc.  All good ideas and we'd love to do it!!

Unknown said:

So apparently the bottom line is, that everyone thinks it is a good idea, but SDL is not doing anything about it ?

Hi Reynir Gunnlaugsson 

Interesting conclusion... not sure how you got to it!

Unknown said:

From what I see in this thread from multiple persons, this has been mentioned since April 2017, an app has come forth, which does not work, the advanced filter option does not work, and there is no mentioning of SDL working on this or showing an interest in it. Is there any other conclusion that can be drawn from this ?

Well, nobody said we were doing nothing.  Only you did. Just because we have not said anything doesn't mean we are not working on it.  There are in fact lots of things that we are working on that we don't share with our users.  If we did we would then have to spend much wasted time answering every question, or suggestion for something else, and even comment on how we are doing it all wrong!  It would be a waste of time, despite what Evzen thinks, because you cannot possibly know enough about the restraints on our ability to deliver anything, nor our future strategy.  It might work with opensource development for products but not in a commercial one.

On this thread, which is not the full story, we have logged an enhancement to the APIs internally so we can address this properly.  And we have also got an item of work in our queue for app work to try and resolve this another way.  But like anything it has to sit in the list of work we have on.  So the solution is this:

1. You fix it yourself (it is opensource and you don't have to be restricted by the same things we are... we only use the public APIs)

2. You wait for us to get to it

The second way won't cost you a penny, only time.  The first way is free if you can code, or find a friendly developer to help you with it.

Also note that the fix we are implementing is for colours and not formatting.  So that would be another enhancement altogether... probably similar but still another feature!