Huge shout-out for the team behind Okapi!

[Víctor Parra García]

Hi folks! Today I don't come with a weird tricky question as usual. I just downloaded the last snapshot and realized the Excel filter now supports character limits which was a huge stopper in my workflow. It's not perfect yet cause it's static (you can just set a fixed number instead of it picking it up from the stated column) but we can see the shape it's taking and, god, this is just GREAT! 

THANKS SO MUCH FOR THE AMAZING JOB!

[Chase Tingley]

Hi Victor,

I'm glad you found this one useful!  We had run into a need for this feature at LILT as well, so this addition was designed by my colleague Ena and implemented by Denis.

I'm curious about your suggested improvement -- you want to be able to specify that a given column contains the maxwidth value for that specific row?

ct

On Wed, Feb 12, 2025 at 11:33 AM Víctor Parra García <vicpar...@gmail.com> wrote:

Hi folks! Today I don't come with a weird tricky question as usual. I just downloaded the last snapshot and realized the Excel filter now supports character limits which was a huge stopper in my workflow. It's not perfect yet cause it's static (you can just set a fixed number instead of it picking it up from the stated column) but we can see the shape it's taking and, god, this is just GREAT! 

THANKS SO MUCH FOR THE AMAZING JOB!

--
You received this message because you are subscribed to the Google Groups "okapi-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to okapi-users...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/okapi-users/16cd6c7c-8797-4af6-b089-29e3d747ffbdn%40googlegroups.com.

[Víctor Parra García]

Yeah, exactly.

Let's think we have:

Source in Column A, Target in Column B and  Maxwidth   (in figures) in Column C so, instead of applying a static  maxwidth, the parser could be able to take the figure from the stated column for that specific row, this way, we can have dynamic  maxwidth, each row would have it's own.

[Nathan Cardenas]

I agree, this would be very useful!

Bonus points if it works with a formula in the cell that assigns/calculates the maxwidth. Though rare, I've seen this in source files now and then.

[Marc Mittag]

what would be really cool is to extend this to work with separate columns also for

- minheight

- minwidth

- maxheigth

- sizeunit-heigth

- sizeuit-width

Then we could use okapi as default parser for such stuff in translate5 for our pixel- and character-based length and amount of lines check without having to write own parsers anymore :-)

This would mean, that when the next client comes, that needs something like this, we likely will fund the dev for this :-)

To view this discussion visit https://groups.google.com/d/msgid/okapi-users/a415e290-a037-431e-bb56-42edcb7ff70cn%40googlegroups.com.

[Víctor Parra García]

My workaround has always been to use the Metadata Column as a "fake" maxlen column and then use a simple S$R python script to copy that content into maxwidth attribute for the specific segment but definitely having it integrated would be a life-changer.