LangPack French bug, we are stuck, until these issues are resolved

[leejul]

Configuration:
• Mac os 10.15.7
• Windows 10 pro (for comparisons)
• Computer: macmini i7 2,3 ghz


Various detailed and completed issues to help developers fix bugs as quickly as possible.
We count on the resolution of these bugs to be able to progress in our work and thus make benefit from our long work of translation and resizing of the windows to all the french-speaking users of Reaper.


Question:
Is there a quick way or tool to locate Reaper menu, dialog or specific window in the LangPack Template file?


Issue 1 : (very important and essential)
Problem: There are lots of windows in Windows that are not resized the same on MacOS.
How can you resize windows and have it work on both operating systems?
It is important to fix this problem.
Windows and Mac windows are too different when translating and resizing.
Thanks.
Expected: Resizings done on MacOS should also work on Windows. Otherwise, you would need a LangPack file for each system. Which is too complicated and too much work.





Issue 2 (This issue does not appear on Windows but there are other issues near this location like truncated drop down menus etc.)
Langpack : [MIDIEDIT]
Problem: I can't resize the window ‘key snap’ = «Magnétisme à la clé» in French.
Several strings are missing.
Expected: Possibility of resizing.




Issue 3
Problem: When I activate in the preferences the option: «rounded macos buttons» = «boutons macos arrondis» in french, long words (English or French) in the drop-down menus at the bottom of the MIDI window are truncated: «hauteur tonal» (= pitch n english) and «tous les canaux» = «all channels» in english. They cannot be resized. If we deactivate “rounded macos buttons”, there is no longer a problem.
Expected: Possibility of resizing or correction of the bug related to the “rounded macos buttons” option.




Issue 4
problem: In “Project settings” then the “media” tab, then the option “format for apply fx, glue, freeze etc” then “custom”, I cannot resize the “choose format for apply fx” window /glue/freeze= Choisir le format pour appliquer les fx/fusionner/geler/etc» in french.

Same for the option just below « default format for project/region render » = «format par defaut pour le rendu du projet/région» in french, I can't resize the window.

It is probably necessary to be able to resize the outline of the window, i.e., probably the OK, CANCEL buttons and perhaps the title of the window, so that the middle resizes.
Expected: Possibility of resizing.



Issue 5
Problem: It is not possible to resize the "theme adjuster" window
Expected: Possibility of resizing.




Issue 6 : (Works under windows 10 pro)
Langpack : IDD_MEDIAITEMPROPS
problem: It is not possible to translate the following English words into French in the item properties window:
• item timebase
• take name
• loop source
• preserve pitch when changing rate
• choose new file
• rename file
• update all similar items in project with new filename
• new folder
• peak
• true peak,
Expected: We can translate these words




Issue 7 :
Langpack : IDD_SAVEOPTIONS
problem : It is not possible to resize the "save as" or “new project” windows
Expected: Possibility of resizing.

[tohubohu]

Bump!

[tohubohu]

Bump

[Justin]

Issue 1 : (very important and essential)
Problem: There are lots of windows in Windows that are not resized the same on MacOS.

Hmm is the child dialog also getting resized in that case? It doesn't look like it's using the full width...

Issue 6 : (Works under windows 10 pro)
Langpack : IDD_MEDIAITEMPROPS

Strings such as "Item timebase:", strings that have an & in them, this will require a workaround, which is to calculate the ID of the string without the &, and set that in the language pack. You can use:

https://landoleet.org/i8n/string_calculator.html

to calculate, for example:

7FA9D4B370190166=Item time&base:

you'd paste "Item timebase:" and get:

267E13103BEC6742=Item timebase:

(sorry for the need for the workaround, perhaps we can remove this requirement at some point)

[tohubohu]

Hello, it's me who takes care of the resizing because Leejul is blind.

Originally Posted by Justin

Hmm is the child dialog also getting resized in that case? It doesn't look like it's using the full width...

Issue 1
I don't quite understand your answer.
I have resized the windows correctly on mac Os and when I open the translation file in Windows, the resizes sometimes don't work. For example, screenshots.

Originally Posted by Justin

Strings such as "Item timebase:", strings that have an & in them, this will require a workaround, which is to calculate the ID of the string without the &, and set that in the language pack. You can use:

https://landoleet.org/i8n/string_calculator.html

to calculate, for example:

7FA9D4B370190166=Item time&base:

you'd paste "Item timebase:" and get:

267E13103BEC6742=Item timebase:

(sorry for the need for the workaround, perhaps we can remove this requirement at some point)

Issue 6
thank you, I managed to work around the problem except for:

• update all similar items in project with new filename
• new folder
• peak
• true peak

And for the other issues, did you manage to find anything? Do you think you have time to watch this please?
if not, what should we do? thank you

[tohubohu]

Bump

[Justin]

Originally Posted by tohubohu

Hello, it's me who takes care of the resizing because Leejul is blind.



Issue 1
I don't quite understand your answer.
I have resized the windows correctly on mac Os and when I open the translation file in Windows, the resizes sometimes don't work. For example, screenshots.

Edit: the issue is that the text for this checkbox is just too long -- when you increase the size of the dialog in general, it proportionately moves the checkbox. Can you shorten the text?

As a side note, mouseover text for that checkbox wasn't supported, adding support for that now (so you can put more explanation in there).

• update all similar items in project with new filename
• new folder
• peak
• true peak

And for the other issues, did you manage to find anything? Do you think you have time to watch this please?
if not, what should we do? thank you

Fixing these! Except hmm "new folder" where is that?

[Edison]

Originally Posted by Justin

Can you give me a link to the latest version of the langpack to test against?

Fixing these! Except hmm "new folder" where is that?

Hi Justin,

I take this moment to make a request.

Could you please look into this issue?
https://forum.cockos.com/showpost.ph...&postcount=173


Kind regards,

[tohubohu]

Originally Posted by Justin

Edit: the issue is that the text for this checkbox is just too long -- when you increase the size of the dialog in general, it proportionately moves the checkbox. Can you shorten the text?

As a side note, mouseover text for that checkbox wasn't supported, adding support for that now (so you can put more explanation in there).

Hello
we are having difficulty understanding what you want to explain to us about issue 1. I will try to be clearer in explaining the problem.
1 - I'm on mac os 10.15.7
2 - I created a portable version of Reaper on my desktop to work on a default Reaper (the one downloaded from the site).
3 - I put the "REAPER_SWS_FRC.ReaperLangPack" file (this is the file translated into French) in the Langpack folder.
4 - I open this file with Visual Code.
5 - I use the code "5CA1E00000000000=1.0 1.0" to resize all the windows I want in Reaper and I move the numbers as I want as needed.
6 - Once it suits me, I save this translation file
7 - I now want to use this same translation file with reaper on Windows 10.
8 - I open my windows 10 on my mac, via the VMware fusion application.
9 - I drag our translation file, scaled on mac os, into the Langpack folder of the Windows 10 Reaper.
10 - I open Reaper
11 - I notice that in certain places of Reaper, the resizings do not work any more like under Mac Os.
12 - At the very beginning of the thread, in issue 1, I showed an example (among others) of the difference in resizing that we observe between Mac os and Windows 10 with the same translation file.
So that's the problem! We don't have the same resizes depending on whether we are on Windows and mac os.
(I hope the English translation from google is clear

[Justin]

Originally Posted by tohubohu

Hello
we are having difficulty understanding what you want to explain to us about issue 1. I will try to be clearer in explaining the problem.
1 - I'm on mac os 10.15.7
2 - I created a portable version of Reaper on my desktop to work on a default Reaper (the one downloaded from the site).
3 - I put the "REAPER_SWS_FRC.ReaperLangPack" file (this is the file translated into French) in the Langpack folder.
4 - I open this file with Visual Code.
5 - I use the code "5CA1E00000000000=1.0 1.0" to resize all the windows I want in Reaper and I move the numbers as I want as needed.
6 - Once it suits me, I save this translation file
7 - I now want to use this same translation file with reaper on Windows 10.
8 - I open my windows 10 on my mac, via the VMware fusion application.
9 - I drag our translation file, scaled on mac os, into the Langpack folder of the Windows 10 Reaper.
10 - I open Reaper
11 - I notice that in certain places of Reaper, the resizings do not work any more like under Mac Os.
12 - At the very beginning of the thread, in issue 1, I showed an example (among others) of the difference in resizing that we observe between Mac os and Windows 10 with the same translation file.
So that's the problem! We don't have the same resizes depending on whether we are on Windows and mac os.
(I hope the English translation from google is clear

ah I think I understand this problem, fixing for the next build/release!

[tohubohu]

Originally Posted by Justin

Hmm is the child dialog also getting resized in that case? It doesn't look like it's using the full width...



Strings such as "Item timebase:", strings that have an & in them, this will require a workaround, which is to calculate the ID of the string without the &, and set that in the language pack. You can use:

https://landoleet.org/i8n/string_calculator.html

to calculate, for example:

7FA9D4B370190166=Item time&base:

you'd paste "Item timebase:" and get:

267E13103BEC6742=Item timebase:

(sorry for the need for the workaround, perhaps we can remove this requirement at some point)

Hello again,
thank you first of all for issue 1, we hope it will be resolved because it is the most important.

ISSUE 6

I come back to you regarding issue 6.

1 - I'm on mac os 10.15.7 and reaper 6.66
2 - I put our French translation file named "REAPER_SWS_FRC.ReaperLangPack" in reaper's langpack folder.
2 - I open reaper, create a track, then create an item and I open the item properties window.
3 - As explained in the first message, I notice that in the item properties window on Reaper Mac OS (and not on Windows 10 where all is ok), the following words are always in English (while they are translated into French in our translation file "REAPER_SWS_FRC.ReaperLangPack"):

• item timebase
• source loop
• take name
• preserve pitch when changing rate
• choose new file
• rename file
• update all similar items in project with new file name
• peak
• true peak

4 – So I use your workaround via this link https://landoleet.org/i8n/string_calculator.html

5 - "Item Timbase" is now code 267E13103BEC6742
"loop source" is now code 6EF8B21B2A28E6CA
"Take name" is now code 4B72743D091519BF
"preserve pitch when changing rate" is now code 64B6651DCB1D575C
"choose new file" is now code 9B35919175721ABC
"rename file" now has code 33B0245676178345

6 – The words translate well into French in the item properties window.

7 - For:
• “update all similar items..”
• Peak
• True Peak
I can't change the codes to make a French translation. It may be available in a future version of reaper, since you seem to have found the solution.

8 – I save the translation file

9 - I open Windows 10 on VMware fusion on my Mac.

10 – I drag the translation file into the langpack folder

11 – I open reaper, then the item properties window

12 - and there, the words :

• item timebase
• source loop
• take name
• preserve pitch when changing rate
• choose new file
• rename file

that I had managed to make appear in French on mac os, using your workaround, are in English on Windows 10. And that is a problem

[tohubohu]

Originally Posted by Justin

Fixing these! Except hmm "new folder" where is that?

I couldn't find the "new folder" either.
I think it is somewhere else in other windows. Other issues to be resolved later.

[Justin]

the latest +dev build should fix a lot of these things (the special handling of strings with & in them should no longer be necessary, and the sizing issue on Windows should be resolved)

[tohubohu]

Originally Posted by Justin

the latest +dev build should fix a lot of these things (the special handling of strings with & in them should no longer be necessary, and the sizing issue on Windows should be resolved)

Hello,

ISSUE 1

Overall, it has improved, but there are still issues between Windows and Mac Os. Here is an example screenshot. You can compare both mac and windows windows. The two sizing problems are rated 1 and 2





ISSUE 6

There is still a problem here with the translation file on mac, we do not see all the words that cause problems. (I no longer use your workaround. If I understand correctly, there is no longer any need.)
Here are four screenshots to see that the words are truncated compared to the translation file. thank you.

[Justin]

Originally Posted by tohubohu

Hello,

ISSUE 1

Overall, it has improved, but there are still issues between Windows and Mac Os. Here is an example screenshot. You can compare both mac and windows windows. The two sizing problems are rated 1 and 2

I think these differences are somewhat to be expected. If you increase the scaling of the window there should be sufficient room.

ISSUE 6

There is still a problem here with the translation file on mac, we do not see all the words that cause problems. (I no longer use your workaround. If I understand correctly, there is no longer any need.)
Here are four screenshots to see that the words are truncated compared to the translation file. thank you.

Thanks, fixing!

[tohubohu]

Originally Posted by Justin

I think these differences are somewhat to be expected. If you increase the scaling of the window there should be sufficient room.
Thanks, fixing!

ISSUE 1

I still found in several places important differences between mac and Windows, especially in the project settings.
I think the problem is not completely solved. Do you have any idea where it could come from? Because otherwise it is in a way a return to square one. You have to resize on Mac Os and Windows, and maybe also on Linux.

[Justin]

Originally Posted by tohubohu

ISSUE 1

I still found in several places important differences between mac and Windows, especially in the project settings.
I think the problem is not completely solved. Do you have any idea where it could come from? Because otherwise it is in a way a return to square one. You have to resize on Mac Os and Windows, and maybe also on Linux.

The fonts are different so you'll get different required space for each platform. If there are big inconsistencies as you previously had reported, we can look at them, but the ones in the screenshot are simply you running out of space.

[tohubohu]

Originally Posted by Justin

The fonts are different so you'll get different required space for each platform. If there are big inconsistencies as you previously had reported, we can look at them, but the ones in the screenshot are simply you running out of space.

ok, thanks, indeed, it's about font size.

ISSUE 7
I come back to you again concerning issue 7 which poses a problem, because the options to check below are still important and we do not see them written in full. I don't know if there is a solution but I can't solve the problem.
menu : save as, open project
On the other hand, you can see on screenshots that some buttons around the window are in English and not translated into French :
'new folder',
'cancel'...
...
Did you fix the problem previously?

[Justin]

Looking at the scaling for the "copy media" etc checkboxes.

Re: New Folder, Save as:, Search, etc -- those are all OS-provided and should be localized by the OS?

[tohubohu]

Originally Posted by Justin

Re: New Folder, Save as:, Search, etc -- those are all OS-provided and should be localized by the OS?

I do not know.
On Windows 10, I see that there is no problem with these words. They are translated into French.
the problem is only on Mac OS

[tohubohu]

Originally Posted by Justin

Looking at the scaling for the "copy media" etc checkboxes.

same problem on Win 10 and Mac OS

[tohubohu]

Hello,

Issue 1 is resolved.
issue 7 is resolved except for the translation of "save as", "new folder" "cancel" etc...but it is not very urgent.
thanks.

Issue 6 is almost resolved.
There is still an important problem with "update all similar items in project with new filename" that is truncated.

[Justin]

Originally Posted by tohubohu

Hello,

Issue 1 is resolved.
issue 7 is resolved except for the translation of "save as", "new folder" "cancel" etc...but it is not very urgent.
thanks.

Issue 6 is almost resolved.
There is still an important problem with "update all similar items in project with new filename" that is truncated.

For issue 6 did you set the scaling for that section?

[tohubohu]

Originally Posted by Justin

For issue 6 did you set the scaling for that section?

Sorry, it's ok. there are so many things that I forgot to try the window sizing again. it works.

[tohubohu]

I think issue 2 is important to fix as well. There is also a link with issue 3.
issue 3 is related but less serious because related to less important options.

ISSUE 2

It is not possible to resize all this.

On Windows 10, below you see the screenshot and all the truncated words.



focus on the problems









On Mac it works except for the word 'magnetisme à la clé'. see screenshot



Focus on the problem






ISSUE 3

On the other hand, still on Mac Os, it no longer works when the 'rounded macOS buttons' option is activated. see screenshot.





focus on the problems

[tohubohu]

Bump

[Justin]

For issue 2, the fix is a little tricky, but you should have the same values for

[midiedit]
7A1F9306EBC070C6=Magnétiser la clé
4417D0C297FFFC34=Magnétiser la clé:

and

[midi_DLG_102] ; IDD_EDIT
4417D0C297FFFC34=Magnétiser la clé:

The reason that the size is off is that your langpack has a different string from the [midiedit] and [midi_DLG_102] contexts (it's quirky and we could make it consistent on our end, but it's easier and more reliable to fix it on yours! midi_DLG_102 defines the width of the control, and midiedit will be what is actually displayed).

You can set an width-scaling value for [midi_DLG_102] if you want to make all of the combo box fields a bit wider

[tohubohu]

Originally Posted by Justin

For issue 2, the fix is a little tricky, but you should have the same values for

[midiedit]
7A1F9306EBC070C6=Magnétiser la clé
4417D0C297FFFC34=Magnétiser la clé:

and

[midi_DLG_102] ; IDD_EDIT
4417D0C297FFFC34=Magnétiser la clé:

The reason that the size is off is that your langpack has a different string from the [midiedit] and [midi_DLG_102] contexts (it's quirky and we could make it consistent on our end, but it's easier and more reliable to fix it on yours! midi_DLG_102 defines the width of the control, and midiedit will be what is actually displayed).

You can set an width-scaling value for [midi_DLG_102] if you want to make all of the combo box fields a bit wider

Hello

1 – I am on mac os 10.15.7
2 - Initial issue is that 'magnétisme à la clé' (snap to key) is truncated and drop down boxes are truncated when choosing 'rounded mac button' option
3 – To try to fix it, I do a test, I put in [midiedit] 5CA1E00000000000=1.4 1.0
4 – Then I put in [midi_DLG_102]; IDD_EDIT 5CA1E00000000000=1.4 1.0
5 - it enlarges the dropdown areas so it works with the 'rounded mac button' option
6 - On the other hand, "magnétisme à la clé" is always truncated. And I believe I did what you told me.

7 – I am testing on windows 10
8 - the initial problem is that the dropdown boxes are truncated, and there is no problem with 'magnétisme à la clé'
9 – I apply the same resizings
10 – Everything is ok.

[tohubohu]

In fact, on mac, it works when you write exactly the same "magnétisme à la clé" in all three places. So now I understand. That works. I must have misunderstood.
Thanks.
maybe it should be written on the default translation file to warn future translators?

[tohubohu]

issues 1, 3, 6, 7 and the last 10 are resolved or a solution has been found.

issue 8 is an important window.

https://forum.cockos.com/showthread.php?t=270191

What do you suggest as a solution please?

[tohubohu]

issues 1, 3, 6, 7, 8 and the last 10 are resolved or a solution has been found.

ISSUE 2 : almost completely solved

I'm just coming back to you to let you know a little thing about issue 2.

On windows, at the bottom of the midi window, when you put 1.5 for example for the first resizing digit, the midi transport bar stretches strangely whereas it doesn't on mac. It's not very embarrassing but it's not very beautiful.


WINDOWS 10

without resizing


with resizing 1.5





MAC OS 10.15.7

without resizing


with resizing 1.5

[tohubohu]

Hello,

ISSUE 1: OK

ISSUE 2: OK
No need to fix weird resizing on Windows 10. I won't go up to 1.5 magnification.
https://forum.cockos.com/showpost.ph...9&postcount=31

ISSUE 3: OK

ISSUE 4: Not fixed

ISSUE 5: OK
no need to correct issue 5 on the theme adjuster. I found workarounds (lowercase letters, line breaks...)

ISSUE 6: OK

ISSUE 7: OK
Not necessarily need to correct on Mac the words which are in English.
https://forum.cockos.com/showpost.ph...1&postcount=18

ISSUE 8: OK

ISSUE 9: Noted to be fixed in 6.67 but I tested and still not fixed.
https://forum.cockos.com/showthread.php?t=270195

ISSUE 10: OK

ISSUE 11: OK
we're going to let it go, because it's not going to suit people.

thank you for all these corrections

[Justin]

For Issue #4, you should set the scale for the outer window, via e.g.:

[DLG_259] ; IDD_SINKCONFIG
5CA1E00000000000=1.4

[tohubohu]

Originally Posted by Justin

For Issue #4, you should set the scale for the outer window, via e.g.:

[DLG_259] ; IDD_SINKCONFIG
5CA1E00000000000=1.4

ISSUE 4 : OK

There is only ISSUE 9 left and it will be ok

Other possible issues will probably be less important but necessary if you want something clean

thks

[Justin]

For issue 9 perhaps you can shorten the action names a little? Making the user scroll the listview to read it all isn’t ideal…

[tohubohu]

Originally Posted by Justin

For issue 9 perhaps you can shorten the action names a little? Making the user scroll the listview to read it all isn’t ideal…

It's complicated to shorten everything and it's a shame because there it is clear.
In the actions window, you can scroll using the bar at the bottom of the window.
But in the custom actions window, it doesn't work. The bar at the bottom of the window does not go all the way to the right.
It's weird that it works in one window and not the other

[tohubohu]

Issue 5