|
|
|
10-26-2017, 09:48 AM
|
#361
|
Human being with feelings
Join Date: Sep 2008
Location: Location
Posts: 5,563
|
There are a few minor issues with the following:
- When using the rubber band library settings in 'Project settings' (Projekteinstellungen), you see this and it's all good:
But when using Reapitch with the same settings
it looks like this:
I know, this is due to the fact that ReaPlugs are not localized, but it looks a bit weird.
- The two strings added in the [prefs_auto_help] section are imho a bit misleading or it might be, that it's just me who doesn't understand them:
Code:
8A324097713011D9=By default, each instance of a pooled automation item has a separate baseline and amplitude setting.
and
Code:
DFC1BE2EA2856F00=By default, automation will be written into existing automation items if any, and the underlying envelope if not.
They say "By default", but what is the default? Is it when the checkboxes are ticked or when they're not ticked?
Also, it might be a bit nit-picky and I'm sorry for that; it's just that I want understand what's going on. It says "existing automation items if any, and the underlying envelope if not." How can an envelope be 'underlying' in the case when no automation item exists in this envelope?
What am I missing or misunderstanding here?
-Data
Last edited by Mr. Data; 10-26-2017 at 10:48 AM.
|
|
|
10-26-2017, 01:08 PM
|
#362
|
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 15,746
|
Quote:
Originally Posted by ecl
Ok ¡¡¡
One more thing... I'm checking my translation from the beginning and found some lines with a number that I hadn't translated, such like:
F19F199E8BEFFBD6=Tree1
D9B12705AD844C62=List1
A27E076F9E7EA1E3=Progress1
What is that "Number 1 " for ?
- Do we have to translate those lines ?
Thanks ¡¡¡
Very Happy for Localization Updates ¡¡¡
|
You can remove those lines, they are unused
|
|
|
10-27-2017, 06:51 AM
|
#363
|
Human being with feelings
Join Date: Jul 2014
Posts: 637
|
Perfect Removing then ¡¡¡
Ok for Sws Template Mr.Data ¡¡¡
Already merged, updating and translating ¡¡
|
|
|
11-09-2017, 07:00 AM
|
#364
|
Human being with feelings
Join Date: Jul 2016
Location: Japan
Posts: 71
|
Quote:
Windows: improve support for application/user paths with non-latin characters
|
I saw this in v5.60 changelog, I downloaded the newest (v5.62) and confirmed that the problem I had mentioned at #325 has been solved (at least in portable mode)!
Good news for all users around the world!! Thanks a lot!!!!
|
|
|
11-13-2017, 06:54 AM
|
#365
|
Human being with feelings
Join Date: Jul 2014
Posts: 637
|
Simbol...
Hi Again ¡¡
What does the symbol in the picture means ?
Can we remove it and translate or is affecting to something else ?
Thanks ¡¡
|
|
|
11-13-2017, 11:53 AM
|
#366
|
Human being with feelings
Join Date: Jul 2016
Location: Japan
Posts: 71
|
Quote:
Originally Posted by ecl
Hi Again ¡¡
What does the symbol in the picture means ?
Can we remove it and translate or is affecting to something else ?
Thanks ¡¡
|
That is "access key".
https://docs.microsoft.com/en-us/dot...forms-controls
We can use it to improve UX of our langpacks.
(At least on Windows. I don't know how about on Mac)
Especially in some language composed totally by non-latin characters like Japanese,
it's impossible to jump to desired menu items by pressing a key of a common initial letter of them.
(e.g. "View" -> press M to jump to " Mixer" -> M again to " Master Track" -> M again to " Monitoring FX" ...)
So I make full use of access keys for my Japanese langpack like this.
But of course access keys can also be useful in latin-character-based language,
so it may be nice to preserve them, I think.
Last edited by Phroneris; 11-13-2017 at 11:58 AM.
Reason: image attatchment
|
|
|
11-14-2017, 10:29 AM
|
#367
|
Human being with feelings
Join Date: Jul 2014
Posts: 637
|
All clear ¡¡¡
Great Explained ¡¡¡
THANKS A LOT ¡¡¡
|
|
|
11-14-2017, 06:53 PM
|
#368
|
Human being with feelings
Join Date: Sep 2008
Location: Location
Posts: 5,563
|
Found yet another few issues with the latest langpack:
- In the render cueue window entries in these columns aren't localizable. It's quite important, not just to be able to translate the word "delay"; there's also a certain necessity to have the values in the string (e.g. "delay %ds" or for instance "%s %dch %.1fkHz %dbit") because of white-spacing and so on.
- The string "Recently used" isn't localizable, no matter wherever it appears.
- The tooltip of time selection, loop selection, regions and markers can't be done either.
- These submenu items won't translate whatsoever (although I'm sure, they did before).
- When creating a JS plug-in, there's no way to translate "new effect".
- These actions appear translated in the 'Main' and in the 'Main (alt recording)' list, but in all others they show up like this:
- An 'umlaut' issue in the dropdown menu of the video processor, whilst the menu in the editor of a dedicated video processor item works well.
- Also, there are some strings like "initializing..." or "Project: loading effect: " (and maybe others, depending on the resources the project loads) that show up in the splash screen, when loading a project, that can't be translated. Even the calculation tool didn't help here.
IMO it's not necessary to create a new langpack file for these. It just would be nice if the strings could be made accessible to translation.
-Data
Last edited by Mr. Data; 11-17-2017 at 09:01 PM.
|
|
|
11-15-2017, 11:06 AM
|
#369
|
Human being with feelings
Join Date: Sep 2008
Location: Location
Posts: 5,563
|
A quick word to you other translaters:
Maybe you already had this idea yourself, but I found out that it's a good option to have a look at the changelog of new (pre)releases. Here you can see which parts are likely to have gone through changes compared to earlier releases and you might not need to trawl through the whole program to find them. This could save a lot of time, because it can help to find strings that appear in English again, although you've translated them before.
-Data
|
|
|
11-15-2017, 12:54 PM
|
#370
|
Human being with feelings
Join Date: Jul 2014
Posts: 637
|
Quote:
Originally Posted by Mr. Data
A quick word to you other translaters:
Maybe you already had this idea yourself, but I found out that it's a good option to have a look at the changelog of new (pre)releases. Here you can see which parts are likely to have gone through changes compared to earlier releases and you might not need to trawl through the whole program to find them. This could save a lot of time, because it can help to find strings that appear in English again, although you've translated them before.
-Data
|
Thanks Mr.D ¡¡¡
That's one of the thing I also do to make it more organized ¡¡¡
Merge tool is totally necessary at least for me.
I follow your reports, are the same here.
I'm Still working with new template update and making a complete review ¡¡¡¡
Crazy but Enjoying Again ¡¡
XDDXXXDXXDXDXD
|
|
|
11-15-2017, 06:08 PM
|
#371
|
Human being with feelings
Join Date: Sep 2008
Location: Location
Posts: 5,563
|
Could we please have access to all the strings in all different appearances of '[DLG_158] ; IDD_SURFACEEDIT' as well as their dropdown menus where necessary, not forgetting the 'Listen' window?
The whole block ('[DLG_158] ; IDD_SURFACEEDIT') looks like this:
Code:
[DLG_158] ; IDD_SURFACEEDIT
ED0AE3021E21F18C=Control Surface Settings
DFD3E9DC03AA3AAC=Control surface mode:
D595332891E352CE=Apply settings
...But all these are missing:
Code:
MIDI input:
MIDI output:
Surface offset (tracks):
Size tweak:
(leave at 9 unless you know what you're doing)
(usually 8, but can be more for multichannel HUI)
(0: first fader=master. 1: first fader=first track)
Ignore fader moves when fader is not being touched
Map F1-F8 to go to markers
Ignore global bank offsets (always map to tracks specified)
Device name:
Pattern config:
Mode:
Device port:
Device IP:
Local listen port:
Local IP:
Run web server on port:
Username:password:
(blank for none)
User pages...
Built-in pages...
Use rc.reaper.fm
ID:
Access URL:
Receive on port:
Send to port:
Host IP:
Device IP:
Listen...
Allow binding messages to REAPER actions and FX learn
If outgoing packets are dropped by the network, try increasing these values:
Outgoing max packet size:
Wait between packets:
Also the dropdown menus:
Code:
Behringer BCF2000 (using preset l)
Frontier AlphaTrack
Frontier Tranzport
HUI (partial)
Mackie Control Extender
Mackie Control Universal
OSC (Open Sound Control)
PreSonus FaderPort
Web browser interface
YAMAHA 01X
Code:
Default
LogicPad
LogicTouch
(refresh list)
(open config directory)
Code:
Device IP/port
Device IP/port [send only]
Local port
Local port [receive only]
Configure device IP+local port
Disabled
-Data
Last edited by Mr. Data; 04-14-2018 at 04:48 PM.
|
|
|
11-16-2017, 04:40 AM
|
#372
|
Human being with feelings
Join Date: Jul 2014
Posts: 637
|
Also these Strings are translated and open in every section but not translated in Reaper:
D62932A5C72ACCBB=Aplicar Cambios de Edición a Todos los Items del Mismo Nombre
D475F7AB7314098E=Aplicar Cambios de Edición a Todos los Items del Mismo Nombre que Estén en la misma Pista
3C4653C38684563B=Aplicar Cambios de Edición a Todas las Tomas Activas del Mismo Nombre
C5C24397EF0DB674=Aplicar Cambios de Edición a Todas las Tomas Activas del Mismo Nombre que Estén en la Pista
Propagate is Cool ¡¡
Other thing - What does IDE means ?
I know that is mentioned in Theme, Reascript, but don't what's refred to...
Last edited by Javier Robledo; 11-16-2017 at 05:37 AM.
Reason: add
|
|
|
11-16-2017, 08:18 PM
|
#373
|
Human being with feelings
Join Date: Sep 2008
Location: Location
Posts: 5,563
|
Quote:
Originally Posted by ecl
Also these Strings are translated and open in every section but not translated in Reaper:
D62932A5C72ACCBB=Aplicar Cambios de Edición a Todos los Items del Mismo Nombre
D475F7AB7314098E=Aplicar Cambios de Edición a Todos los Items del Mismo Nombre que Estén en la misma Pista
3C4653C38684563B=Aplicar Cambios de Edición a Todas las Tomas Activas del Mismo Nombre
C5C24397EF0DB674=Aplicar Cambios de Edición a Todas las Tomas Activas del Mismo Nombre que Estén en la Pista
Propagate is Cool ¡¡
|
These work perfectly here.
Quote:
Originally Posted by ecl
Other thing - What does IDE means ?
I know that is mentioned in Theme, Reascript, but don't what's refred to...
|
I reckon, it stands for Interactive Development Environment.
-Data
|
|
|
11-17-2017, 08:48 PM
|
#374
|
Human being with feelings
Join Date: Sep 2008
Location: Location
Posts: 5,563
|
I discovered a few other things:
-Data
Last edited by Mr. Data; 11-17-2017 at 09:21 PM.
|
|
|
11-18-2017, 02:12 AM
|
#375
|
Human being with feelings
Join Date: Jul 2014
Posts: 637
|
Quote:
Originally Posted by Mr. Data
These work perfectly here.
I reckon, it stands for Interactive Development Environment.
-Data
|
All Right Now ¡¡¡¡¡
Thanks ¡¡¡¡¡
|
|
|
11-20-2017, 09:13 PM
|
#376
|
Human being with feelings
Join Date: Sep 2008
Location: Location
Posts: 5,563
|
Found another few entries that aren't in the template and can't be translated, probably belonging into section [menu], since other entries in this menu are also located there. These are menu items in the Media Explorer.
Code:
35E3D51B66AA2577=Changes will be reverted if the plugin cache is cleared
17DDC80B83E43242=Include "No category"
AE59FA2FAFF05064=Include "No developer"
-Data
|
|
|
12-03-2017, 03:17 PM
|
#377
|
Human being with feelings
Join Date: Sep 2008
Location: Location
Posts: 5,563
|
Got another issue. This time with the grouping matrix.
If many attributes in the grouping window are ticked and then we hover the mouse over the according cell in the matrix, we get this funny incredibliy long one-line tooltip, which nerely always is truncated, if the grouping window isn't big enough (but sometimes even, if, it is, maybe because the buffer for tooltip text might be too small). Additionally, if you're not in group 1 but in group 50 or even 64 there's no chance to ever see the tooltip completely:
I tried to format it into a multi-line tooltip, but this is not possible in a satisfying way:
As you can see, I was only able to split the lines immediately following the words 'Master' and 'Slave', but not after the comma.
Also, it isn't possible to change these entries into'Master,\n' and 'Slave,\n', because firstly the comma (coming out of nirvana) would still be there and secondly the comma (and linefeed) isn't wanted in every case e.g. at end of the tooltip text.
There is more than one string 'D990EA186C48B88B=, ' in the langpack file, one even in the [common] section, but this can't be used, since it would most probably mess other things up.
What we'd need in the langpack would be a string (assumingly in the [grouping] section), that covers this special case and lets us change the string ', ' into ',\n'.
Trying to put the string 'D990EA186C48B88B=, ' into the
[grouping] section and change it to 'D990EA186C48B88B=,\n' didn't help either BTW.
-Data
Last edited by Mr. Data; 12-05-2017 at 06:45 AM.
|
|
|
12-08-2017, 11:46 AM
|
#378
|
Human being with feelings
Join Date: Jul 2016
Location: Japan
Posts: 71
|
In connection with the grouping matrix, I found two text garblings here:
1. M(aster) and S(lave) character icons on detail mode
2. Tooltips with many contents on non-detail mode
|
|
|
12-08-2017, 12:18 PM
|
#379
|
Human being with feelings
Join Date: Sep 2008
Location: Location
Posts: 5,563
|
Hi Phroneris,
I'm a bit confused about your screenshots, showing the non-detailed grouping. As you can see in my posting, there are 64 groups; in your screenshots I only see 32.
Do you have the newest pre-release installed?
Greets to you and Nippon.
-Data
|
|
|
12-09-2017, 07:56 AM
|
#380
|
Human being with feelings
Join Date: Jul 2016
Location: Japan
Posts: 71
|
Thanks Data, when I saw yours I just had the same question as to why you have no less than 64 groups.
My REAPER is v5.62/x64. Not pre-released one.
Now I've checked my portable v5.62 with the completely initial(...maybe) settings and confirmed that it also has only 32 groups.
What's that...
It may mean German is twice as strong, haha.
|
|
|
12-14-2017, 07:50 AM
|
#381
|
Human being with feelings
Join Date: Jul 2016
Location: Japan
Posts: 71
|
Quote:
REAPER 5.70: Carry The Zero
Groups
・ support up to 64 track groups per project
|
Oh, I see!
|
|
|
02-20-2018, 03:16 AM
|
#382
|
Human being with feelings
Join Date: Jul 2016
Location: Japan
Posts: 71
|
ReaScript problem.
GetTrackEnvelopeByName() and GetTakeEnvelopeByName() get envelope names as translated by langpacks.
So some scripts using these functions (e.g. https://forum.cockos.com/showthread.php?t=181934 ) don't work on well-localized REAPER.
Here's an example.
'8FC86C263760ACB9=Volume' in [envname] and [item] or [common].
Then how should it be solved...?
My idea is: let existing Get[Track/Take]EnvelopeByName() get original English envelope names (in the above example, 'Volume' will be reterned anyway) and establish new functions named Get[Track/Take]EnvelopeByLocalizedName() to get localized ones ('yo track volume トラック音量', 'yeah take volume テイク音量' or 'GLOBAL VOLUME!!').
...It's just an idea, but I hope it will help.
P.S.
I guessed ViewPrefs() might also results in the same error because of its string pageByName argument, but in the first place it seems not to work correctly even in English :P https://forum.cockos.com/showthread.php?t=187480
Last edited by Phroneris; 02-20-2018 at 11:30 PM.
Reason: not only Volume
|
|
|
02-20-2018, 03:23 AM
|
#383
|
Human being with feelings
Join Date: Jul 2016
Location: Japan
Posts: 71
|
Additionally, let me report non-latin garblings on the variable browser of ReaScript IDE.
Not only values themselves, but also 'Name' and 'Value' headers are garbled.
|
|
|
02-22-2018, 03:22 PM
|
#384
|
Human being with feelings
Join Date: Sep 2008
Location: Location
Posts: 5,563
|
Quote:
Originally Posted by Phroneris
Then how should it be solved...?
My idea is: let existing Get[Track/Take]EnvelopeByName() get original English envelope names (in the above example, 'Volume' will be reterned anyway) and establish new functions named Get[Track/Take]EnvelopeByLocalizedName() to get localized ones ('yo track volume トラック音量', 'yeah take volume テイク音量' or 'GLOBAL VOLUME!!').
...It's just an idea, but I hope it will help.
|
But this would mean a user would have to rewrite/modify his/her own scripts to get them localized correctly. To introduce extra routines to solve localizing problems that in the end do the same as already existing ones, might therefore possibly not really be the best way to go. Probably it's a better solution to modify existing functions, so that all already written scripts, using these functions, automatically would work correct in the desired language in the first place.
But I somehow doubt, that it will ever happen that all these functions which might use some (whatever) localized string(s) will be rewritten. (sigh!)
-Data
Last edited by Mr. Data; 02-22-2018 at 03:33 PM.
|
|
|
02-25-2018, 09:32 AM
|
#385
|
Human being with feelings
Join Date: Jan 2018
Posts: 12
|
Hello guys.
I started to translate the template in my language.
I have just a question. Sometimes I find lines with a "&" character inside the sentence, what's it there for?
|
|
|
02-25-2018, 09:53 AM
|
#386
|
Human being with feelings
Join Date: Jun 2009
Location: Croatia
Posts: 24,798
|
That's accellerator for menu alt-walks.
|
|
|
02-26-2018, 07:07 AM
|
#387
|
Human being with feelings
Join Date: Jan 2018
Posts: 12
|
Quote:
Originally Posted by EvilDragon
That's accellerator for menu alt-walks.
|
Ah, ok. Is that like for shortcuts? Thank you btw.
|
|
|
02-26-2018, 10:13 AM
|
#388
|
Human being with feelings
Join Date: Sep 2008
Location: Location
Posts: 5,563
|
Well, sort of. But it isn't a Reaper thing.
It is used in most apps.
If you have a menu open, you often see underlined characters in its items. If you insert a '&' preceeding a char this char will be underlined in the menu and the user can just press the corresponding key to choose this menu item.
Having an item called "H&ello" would give "Hello" in the menu and the user can trigger it by pressing e.
-Data
|
|
|
03-06-2018, 09:50 PM
|
#389
|
Human being with feelings
Join Date: Sep 2008
Location: Location
Posts: 5,563
|
Would be nice to have an update for the next (official) build, considering some, partly already mentioned missing things.
A quick (not necessarily complete) summary:
- [DLG_158] ; IDD_SURFACEEDIT:
This block consists of.
Code:
[DLG_158] ; IDD_SURFACEEDIT
ED0AE3021E21F18C=Control Surface Settings
DFD3E9DC03AA3AAC=Control surface mode:
D595332891E352CE=Apply settings
But all these are still missing for different strings the window shows, depending on the selection you do in this dropdown menu.
Code:
Behringer BCF2000 (using preset l)
Frontier AlphaTrack
Frontier Tranzport
HUI (partial)
Mackie Control Extender
Mackie Control Universal
OSC (Open Sound Control)
PreSonus FaderPort
Web browser interface
YAMAHA 01X
And these are:
Code:
MIDI input:
MIDI output:
Surface offset (tracks):
Size tweak:
(leave at 9 unless you know what you're doing)
(usually 8, but can be more for multichannel HUI)
(0: first fader=master. 1: first fader=first track)
Ignore fader moves when fader is not being touched
Map F1-F8 to go to markers
Ignore global bank offsets (always map to tracks specified)
Device name:
Pattern config:
Mode:
Device port:
Device IP:
Local listen port:
Local IP:
Run web server on port:
Username:password:
(blank for none)
User pages...
Built-in pages...
Use rc.reaper.fm
ID:
Access URL:
Allow binding messages to REAPER actions and FX learn
If outgoing packets are dropped by the network, try increasing these values:
Outgoing max packet size:
Wait between packets:
Receive on port:
Send to port:
Host IP:
Device IP:
Listen...
Allow binding messages to REAPER actions and FX learn
If outgoing packets are dropped by the network, try increasing these values:
Outgoing max packet size:
Wait between packets:
None
Default
LogicPad
LogicTouch
(refresh list)
(open config directory)
Device IP/port
Device IP/port [send only]
Local port
Local port [receive only]
Configure device IP+local port
Disabled
...Not forgetting the 'Listen' window itself and strings that might be shown there:
- [DLG_269] ; IDD_BUTTONFINDER
The dropdown menues are missing still:
- The context menu of the undo history isn't complete yet, especially the strings in the submenu of 'Undo state information' (like 'Total size: %d bytes' and such) are not available for translation, I reckon these are strings looking like 'Track %d %s: ' or '%s %d %s', where the first %s is something like 'Track' and the second %s is something like 'FX' or so and the whole menu item is a combination of more than one string, where the second part might be something like 'changed (%d bytes)' or '%d -> %d bytes'.
This menu holds items like 'Project Config: changed (%d bytes)', 'Master Config: changed (%d bytes)' and on top (greyed out) 'Total size: %d bytes'
- The entries in most columns of the render queue list can't be translated still and the date-format (YY-MM-DD) looks somewhat weird unlike in the undo history, where it is shown as usual in German format (DD.MM.YYYY):
- We need to be able to insert linefeeds in the tooltip of the grouping window, cos it's most likely that it gets truncated otherwise, especially when using higher group numbers.
- The string "Recently used" isn't localizable, no matter wherever it appears.
- These submenu items won't translate in the FX browser, but in the FX window they do.
- When creating a JS plug-in, there's no way to translate "new effect".
- These actions appear translated in the 'Main' and in the 'Main (alt recording)' list, but in all others they show up like this:
- An 'umlaut' issue in the dropdown menu of the video processor.
- Another 'umlaut' or special character issue becomes obvious, when exporting a note sheet as PDF.
An original like this:
... looks, when exported, like this:
- Just saw that also the string "Main toolbar", used in some menus still won't translate.
- And the strings in the debug console are also missing.
-Data
Last edited by Mr. Data; 03-21-2018 at 03:12 PM.
|
|
|
03-13-2018, 07:46 PM
|
#390
|
Human being with feelings
Join Date: Jul 2016
Location: Japan
Posts: 71
|
Quote:
Originally Posted by Mr. Data
But this would mean a user would have to rewrite/modify his/her own scripts to get them localized correctly. To introduce extra routines to solve localizing problems that in the end do the same as already existing ones, might therefore possibly not really be the best way to go. Probably it's a better solution to modify existing functions, so that all already written scripts, using these functions, automatically would work correct in the desired language in the first place.
But I somehow doubt, that it will ever happen that all these functions which might use some (whatever) localized string(s) will be rewritten. (sigh!)
-Data
|
Thanks Data.
Do you mean you're recommending something like... "leave Get XXEnvelopeByName() as is and establish Get XXEnvelopeByEnglishName() newly" or "give Get XXEnvelopeByName() a new optional argument to make it return its English name only if that argument is specified"?
Anyway, we probably have different viewpoints.
You seem to suppose that users of scripts are developers themselves and/or people using the same language and it is developers' efforts that should be minimized.
Meanwhile, I assume that scripts are used by various REAPER fans around the world and it is efforts of end users who don't have development ability that should be minimized.
And my another thought is, well, currently this function must be used in at best English scripts. Maybe it's not so major one as it affects destructively yet.
Then I checked 1056 packages I had downloaded from 9 repositories through ReaPack. As a result, I found 36 scripts using Get XXEnvelopeByEnglishName() and confirmed ALL of them retrieve envelopes only by English names regardless of whether directly or not.
I also searched on GitHub as possible, but there are no ReaScripts using localized envelope names with this function.
(The only thing I'm interested in is https://github.com/reaper-oss/sws/bl...r/sws_util.cpp , the bottom two and their __localizeFunc(), but I don't know how we can use them.)
If adopting my idea, another pending issue is whether developers notice the specification change...
But, even if they don't see REAPER's changelog, they must see API reference, so I feel like it'll be okay to write it there.
P.S.
Perhaps this talk should be in developers' thread rather than here...? Sorry if so :P
|
|
|
03-14-2018, 08:37 AM
|
#391
|
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 15,746
|
Quote:
Originally Posted by Mr. Data
Would be nice to have an update for the next (official) build, considering some, partly already mentioned missing things.
A quick (not necessarily complete) summary:
|
Thanks for the list! Hopefully doing all of these, except for the theme element finder, as this is something so obscure I really don't want to pollute the langpacks with it
|
|
|
03-14-2018, 07:12 PM
|
#392
|
Human being with feelings
Join Date: Sep 2008
Location: Location
Posts: 5,563
|
Thank you, Justin!
I remember now, some time ago you were talking about this Element Finder thing and that it might be tricky to include it in the template.
Quote:
Originally Posted by Phroneris
Thanks Data.
Do you mean you're recommending something like... "leave GetXXEnvelopeByName() as is and establish GetXXEnvelopeByEnglishName() newly" or "give GetXXEnvelopeByName() a new optional argument to make it return its English name only if that argument is specified"?
Anyway, we probably have different viewpoints.
You seem to suppose that users of scripts are developers themselves and/or people using the same language and it is developers' efforts that should be minimized.
|
Hi Phroneris,
no, you misunderstood I reckon (or we misunderstand each other ).
I meant that there should be no difference for the user when (s)he writes a script in whatever language. So, if for instance an English speaking user sends a script to a Japanese user, both could use it without the need of modifying anything. In your Example, if you have a function called "Get XXEnvelopeByName()" it should work in every language automatically, no matter whether the name of the envelope is in Japanese, Cyrillic, Latin or whatever characters. Otherwise there would have to be functions for each language that all would do the same. In the German version, for instance, REAPERs envelopes have German names for volume, mute, pitch etc. and the function should handle it in English, German, Japanese ... whatever.
So in my view it is the task of developers, to make these functions work in every language, if they don't do already anyway.
And just because I assume that many users who write scripts aren't developers, it should be that way, so they don't have to bother with languages, especially if they plan to spread their work around the world.
-Data
Last edited by Mr. Data; 03-14-2018 at 07:18 PM.
|
|
|
03-15-2018, 05:40 AM
|
#393
|
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 15,746
|
Quote:
Originally Posted by Mr. Data
But this would mean a user would have to rewrite/modify his/her own scripts to get them localized correctly. To introduce extra routines to solve localizing problems that in the end do the same as already existing ones, might therefore possibly not really be the best way to go. Probably it's a better solution to modify existing functions, so that all already written scripts, using these functions, automatically would work correct in the desired language in the first place.
But I somehow doubt, that it will ever happen that all these functions which might use some (whatever) localized string(s) will be rewritten. (sigh!)
-Data
|
BTW - a more reliable way to get an envelope by an identifier is to use GetSetMediaTrackInfo(track,"P_ENV","<VOLENV") etc.
but.. making it so that Get*EnvelopeByName() search the english names first, then the localized names (but of course programmers must use the english names if they want it to work universally).
Last edited by Justin; 03-15-2018 at 05:48 AM.
|
|
|
03-15-2018, 05:05 PM
|
#394
|
Human being with feelings
Join Date: Sep 2008
Location: Location
Posts: 5,563
|
Quote:
Originally Posted by Justin
BTW - a more reliable way to get an envelope by an identifier is to use GetSetMediaTrackInfo(track,"P_ENV","<VOLENV") etc.
but.. making it so that Get*EnvelopeByName() search the english names first, then the localized names (but of course programmers must use the english names if they want it to work universally).
|
If I get that right you make a distinction between a 'normal' user who writes scripts and a programmer like e.g. SWS or yourself. If so, this makes absolute sense to me and is what I meant actually. So, if a user uses a function that gives back a name of some knob or fader or whatever for, say, an UI, (s)he should see that name if it's localized, but internally the function surely must be handled in English to make it universal.
My point was, that a user who uses REAPER in another language as English shouldn't be forced to take care of this.
But I see that this might be a major task to achieve this and maybe it's not even important. It was just a thought.
-Data
|
|
|
03-16-2018, 08:12 PM
|
#395
|
Human being with feelings
Join Date: Jul 2016
Location: Japan
Posts: 71
|
Quote:
Originally Posted by Phroneris
Thanks Data.
Do you mean you're recommending something like... "leave GetXXEnvelopeByName() as is and establish GetXXEnvelopeByEnglishName() newly" or "give GetXXEnvelopeByName() a new optional argument to make it return its English name only if that argument is specified"?
|
I found my mistake. "make it read the English name" is correct. Sorry.
Quote:
Originally Posted by Mr. Data
Hi Phroneris,
no, you misunderstood I reckon (or we misunderstand each other ).
I meant that there should be no difference for the user when (s)he writes a script in whatever language. So, if for instance an English speaking user sends a script to a Japanese user, both could use it without the need of modifying anything. In your Example, if you have a function called "Get XXEnvelopeByName()" it should work in every language automatically, no matter whether the name of the envelope is in Japanese, Cyrillic, Latin or whatever characters. Otherwise there would have to be functions for each language that all would do the same. In the German version, for instance, REAPERs envelopes have German names for volume, mute, pitch etc. and the function should handle it in English, German, Japanese ... whatever.
So in my view it is the task of developers, to make these functions work in every language, if they don't do already anyway.
And just because I assume that many users who write scripts aren't developers, it should be that way, so they don't have to bother with languages, especially if they plan to spread their work around the world.
-Data
|
I, I'm getting confused. Because of lack of my English ability, I can no longer understand even whether we're aim to the same destination or the opposite one, sorry...
Anyway the only thing I can recognize clearly is,
Quote:
Originally Posted by Justin
but.. making it so that Get*EnvelopeByName() search the english names first, then the localized names (but of course programmers must use the english names if they want it to work universally).
|
... is that this must be one of EXACTLY THE BEST solutions.
Many thanks Justin. I'm looking forward to this implementation.
And it seems okay to close this theme.
|
|
|
03-16-2018, 10:31 PM
|
#396
|
Human being with feelings
Join Date: Sep 2008
Location: Location
Posts: 5,563
|
Quote:
Originally Posted by Phroneris
I, I'm getting confused. Because of lack of my English ability, I can no longer understand even whether we're aim to the same destination or the opposite one, sorry...
|
Well, I think we're heading to the same destination, at least as I understand it.
It might just be a matter of words, 'cos English isn't my native Language either.
-Data
|
|
|
04-04-2018, 05:15 AM
|
#397
|
Human being with feelings
Join Date: Jul 2016
Location: Japan
Posts: 71
|
Garbling report: - Wave shape menu of Click Source Properties
Code:
[metronome]
;90C3CF77963D43DF=Sine - soft start
;06F40FE0CBACEBB2=Sine - hard start
;758BE04F40035B56=(old deprecated)
;^2AF10D61DA454203=Triangle
Note: the same menu in "Metronome and pre-roll settings" is okay, but both depend on the same lines of a langpack.
- Performance Meter
Code:
[cpumeter]
;4CF6043E6041E61E=cur/avg:
;01FDED75265EB99E=range:
- Plug-in preset menu of DX and video processing fx (similar to Mr.Data's #390)
Code:
[dx]
;^274E7C84B3E58DB8=Reset to factory default
;^0EC28D42C155A657=---- User Presets (.rpl) ----
;^93244D3BB94E6F33=No preset
Code:
[video_processing]
;^28450354F52CB7AE=Reset
;^0EC28D42C155A657=---- User Presets (.rpl) ----
;^93244D3BB94E6F33=No preset
Note: VST and JS are okay.
- "Preserve:" menu of Crossfade Editor
Code:
[fadeedit]
;^3BEB0AE437FA2F12=center
;^1B262DDE53BE63B5=start
;^0DBD7F7EE933458C=end
- Variable header of JS IDE (similar to my #384)
Code:
[jsfx_ide]
;BB07DD2F46B76299=Refs
;^DCEF2B4D03DE723C=Name
;^772CECA01AD73CB4=Value
- "Grid" in the grid menu of "Quantize Events"
Code:
[midi]
;0E20B188F8964553=Grid
Note: the same entry in the note length menu of MIDI editor is okay.
- CC list of MIDI event property
Note: the same entries in CC lane menu are okay.
Code:
[midi_et]
;F7C99BD39EBB01D9=Bank Select MSB
;and so on...
- "Phase reset" menu of Parameter Modulation LFO
Code:
[parmmod]
;2762372D6D14F1E5=On seek/loop (deterministic output)
;EB06AC7EBF68A535=Free-running (non-deterministic output)
|
|
|
04-04-2018, 05:20 AM
|
#398
|
Human being with feelings
Join Date: Jul 2016
Location: Japan
Posts: 71
|
I cannot translate these entries naturally because of some word order difference between English and Japanese.
So I wish these entries written by %s format:
- Metronome pattern help
Code:
[metronome]
;66C31BA5D527D8CB=Pattern should be
;AA2CC191B64B730E=More will be discarded, fewer will be padded with
Ideal:
Code:
;XXXXXXXXXXXXXXXX=Pattern should be %s. More will be discarded, fewer will be padded with %s.
- Alert message of "Time signature marker position"
Code:
[marker]
;C7B4DAF847DAFE0C=Move time signature change to
Ideal:
Code:
;XXXXXXXXXXXXXXXX=Move time signature change to %s?
- Mousemap actions in the action list of MIDI editor
Code:
[mousemap]
;9965C532C14FFE31=Set default mouse modifier action for
;^D89CC7186B79C49A=to
Ideal (just like BF0CAFC24857E546 in [actions_fmt] section!):
Code:
;XXXXXXXXXXXXXXXX=Set default mouse modifier action for \"%s %s\" to \"%s\"
- Some actions
Code:
[midi_actions]
;9F7B5C942E0C2D22=CC: Set CC lane to
;DBBAB3326B686454=Insert note:
;39E2633651F5ADAD=Cursor: Advance
;1D1C89DBB1032FAB=Set length for next inserted note:
;14B9227A11B91CFC=Edit: Set note length to
Ideal:
Code:
;XXXXXXXXXXXXXXXX=CC: Set CC lane to %s
;XXXXXXXXXXXXXXXX=Insert note: %s
;XXXXXXXXXXXXXXXX=Cursor: Advance %s
;XXXXXXXXXXXXXXXX=Set length for next inserted note: %s
;XXXXXXXXXXXXXXXX=Edit: Set note length to %s
Note:
This is the same wish with a bit different reason.
I translate actions with their original English expressions using "@@" separator, like this.
Code:
DBE0EEA73EA7A24B=編集: 元に戻す @@ Edit: Undo
This is a strategy for easy search by entering English filter words regardless of incompleteness of my langpack (whether an action is translated or not), because it's too hard to translate a huge number of all actions.
So I wish actions with automatic postfixes are also written by %s format.
(... or, it will be great too if the action filter gets an option like "also filter by original English sentences")
|
|
|
04-04-2018, 05:21 AM
|
#399
|
Human being with feelings
Join Date: Jul 2016
Location: Japan
Posts: 71
|
Other issues:
-- That's all!
|
|
|
04-04-2018, 08:46 AM
|
#400
|
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 15,746
|
Quote:
Originally Posted by Phroneris
Optional "Close" translation in the action list doesn't affect.
Code:
[DLG_274] ; IDD_ACTIONS
;^BAC64C1B2E060EE5=Close
|
That string in the "actiondialog" section is what needs to be translated (sorry for the confusion, we'll remove the strings from DLG_274 to avoid future issue).
I can't duplicate this here on Win10, lemme try Win7 I guess?
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 04:18 AM.
|