XYplorer Beta Club

I thought the ref data could be read internally, sorry about that. If something can be done... please do so, as often I come back to ITT to check and copy translated parts. Manually removing accelerators is a slow down.

Buttons: simple recasing or token validation scripts. This would avoid frequent alt-tabbing to a second instance, which I did for my translation and believe me: it's deadly boring.

SkyFrontier wrote:Buttons: simple recasing or token validation scripts. This would avoid frequent alt-tabbing to a second instance, which I did for my translation and believe me: it's deadly boring.

But scripting has no access to ITT. How should that work then? Via clipboard?

Yes, no direct edit box manipulation but simple *src = clip, recase/whatever, out to clip* scripts.
As simple as a single CTB, perhaps having no menu displayed on right click (ie, right click should only fire the second stored script) unless a 'ctrl' or whatever is pressed along with the click.

Well, that's not possible I'm afraid. No scripting here, since MLS/ITT will also be present in the Home Edition (which has no scripting).

However, I can add shortcuts to change the case of letters or words.
Note that this (from v7.50.0008 - 2008-09-01 15:35) works already now:

By far the most used function was 'title', and scripting allows me to make exceptions for prepositions (this is the key point, here! I *always* followed the developer choices concerning formatting on GUI).
Followed by sentence
then lower
upper, never.

Hmmmm... no support for scripting? Another reason why they should go for pro...

>is the real problem the size of the button? Make it non-standard, ie, smaller, rectangle at the ITT...

SkyFrontier wrote:By far the most used function was 'title', and scripting allows me to make exceptions for prepositions (this is the key point, here! I *always* followed the developer choices concerning formatting on GUI).
Followed by sentence
then lower
upper, never.

Hmmmm... no support for scripting? Another reason why they should go for pro...

>is the real problem the size of the button? Make it non-standard, ie, smaller, rectangle at the ITT...

If you work <our strings in the clipboard, simply run a 2nd parallel XY instance with your clipboard-mangling script on a button.

SkyFrontier wrote:I thought the ref data could be read internally, sorry about that. If something can be done... please do so, as often I come back to ITT to check and copy translated parts. Manually removing accelerators is a slow down.

Buttons: simple recasing or token validation scripts. This would avoid frequent alt-tabbing to a second instance, which I did for my translation and believe me: it's deadly boring.

admin wrote:If you work <our strings in the clipboard, simply run a 2nd parallel XY instance with your clipboard-mangling script on a button.

back 2 square 1...

@admin
Since there is no spell checking available in ITT, would it be possible to add a function to export all translated strings as plain text file?
It would be easier to open it in some word processor and do the check.

fenixproductions wrote:@admin
Since there is no spell checking available in ITT, would it be possible to add a function to export all translated strings as plain text file?
It would be easier to open it in some word processor and do the check.

Sure, good idea!

The status icon (or another GUI element) should provide a way to copy all search and replaced items (original and translation) for further extra revision - sometimes a batch, blind search and replace can cause more harm than help.

Bug in the ITT: Translating a fieldset caption always changes the caption of the "Translation preview" box too.

tux. wrote:Bug in the ITT: Translating a fieldset caption always changes the caption of the "Translation preview" box too.

Uhm, fieldset caption? Sorry, blackout. What do you mean?

The ITT applies the previews to the wrong border.

LOL, das ist ja lustig!

Testest du dein Zeug nicht?