(there are win32 and OSX versions there, and the source which you can compile if you get WDL, too).

Usage (from the command line):

Code:

merge_langpack english.txt mylanguage.txt > new.txt

Run this, then inspect new.txt to make sure everything looks right. Note that comments from mylanguage.txt will likely not be preserved. new.txt will have some comments with ####### ... telling you what is new, and what is possibly obsolete in your langpack.

The lines that begin with ;^ mean that this is an optional override for the particular string in that section (it would also be in the common section). You can remove those lines, but the next time you do a merge it will get added again by the merge tool...

I'm interested in your comments, and if you have suggestions for tweaks to this tool that would help speed up your work, let me know!

I tried to use the section [trackrecstatus] to shorten the recinput display. Lots of changes were ok, but I couldn't change some.
For example, how do you change what is displayed if you have a certain MIDI channel (any but "All" - I use ch 1 in this example)) selected as track input? If I arm the track for recording disabled it shows (per default):

Code:

"monitoring, record disabled: MIDI: All: Channel 1"

I'd much prefer it to say

Code:

"mon, no rec: M: All: Ch 1"

I got it so far as to read

Code:

"mon, no rec: MIDI: All: Channel 1"

I can live (hesitantly) with "MIDI", but would love to abbreviate "Channel". Is that possible and how?

I admit, it's not really localization I am doing right now , but the word "Channel" would need to be translated as well, so I think there must be a way?

Can't enter any command line it fails before... maybe it's not X64 ready ?
I've no X86 OS to test...

Ahh, are you just running it from Windows GUI? Unfortunately it is a command line application, so you would generally run cmd.exe first, then go to the directory where you have it download, via something like:

I did the merging (thanks Ollie!) and it looks OK. Now, the thing is I'm seeing problems with accents when I translate a new word. All previous words with accents are OK, it's just happening with new translations. I tried different coding (ANSI, etc) and none of them worked.

I did the merging (thanks Ollie!) and it looks OK. Now, the thing is I'm seeing problems with accents when I translate a new word. All previous words with accents are OK, it's just happening with new translations. I tried different coding (ANSI, etc) and none of them worked.

1) Look for "Confirm Preset Delete" and change it for "Confirmar Eliminar Preconfiguración". Save it.
2) Start REAPER, insert a new track, insert ReaEQ, load one of its presets, click on the "+" symbol and "Delete preset". You should see this:

3) Now, if you look for "Rename preset" and change it for "Renombrar preconfiguración" and save it, that text will look OK:

Cool, thanks guys -- fixing these UTF-8 oversights (they worked before, because we were allowing the ANSI strings through, but converting everything to UTF-8 is allowing us to catch the missed things) -- most of these should be fixed in pre5, once that is out if you could give sshots of places that do not work, that'd be great.

Cool, thanks guys -- fixing these UTF-8 oversights (they worked before, because we were allowing the ANSI strings through, but converting everything to UTF-8 is allowing us to catch the missed things) -- most of these should be fixed in pre5, once that is out if you could give sshots of places that do not work, that'd be great.

'color' stubbornly refuses to translate in midi actions.
I suspect quite a few others don't either, which I saw when I loaded leet.txt
Also I'm not sure what's going on with explorer actions, these weren't leetified, but did retain my 'bar' instead of 'measure' from the previous langpack.
Steve

This, I think, needs to be considered changing even in the original English version
(Found in "Preferences -> Playback"), because the description doesn't make obvious, in which situation the checkbox has to be ticked.

Should I tick it when I want Reaper to stop at the end of the project or
should I tick it when I want Reaper to repeat at the end of the project.

When ticked it does stop at the end of the project, so IMO it should say

This, I think, needs to be considered changing even in the original English version
(Found in "Preferences -> Playback"), because the description doesn't make obvious, in which situation the checkbox has to be ticked.

Should I tick it when I want Reaper to stop at the end of the project or
should I tick it when I want Reaper to repeat at the end of the project.

When ticked it does stop at the end of the project, so IMO it should say

-Data

If repeat is on, though, it will repeat to the start, which isn't stopping... So maybe "Stop (or loop to start, if repeat enabled) at end of project"?

Maybe "Stop playback at end of project if repeat is disabled", because it would make it more consistent, when looking at the option below (which is "Stop playback at end of loop if repeat is disabled").

Funnily enough, I just came across this, because of a very obscure German translation somebody else did.