|
|
|
|
|
"isolated solo button doesn't blink but operates (it stops isolating)" That is normal, also clicking on "solo" resets solo state, and "audition" button disables auditioning. The Solo Isolate button only blinks when a track is solo isolated (solo is enabled). |
|
|
yes, that's what I was wanting to say (sorry) the solo isolate doesn't blink when you isolate a solo |
|
|
I've applied the patch Ardour 6.0-rc1-31-g1c7c0533c2 I have not found the "loAcate" and I don't know what you mean with "2 ticked boxes empty behind glue to bars & beats" session-props.png (33,466 bytes) |
|
|
is "défilement" what audio-engineers use for "transport" in french? I was under the impression that it's "le transport" |
|
|
Sorry for the mix I have done between "tape speed", that in my young years on Studer 24 we used to call "vitesse de défilement" or "vitesse de transport" and the (transport, rec. ready etc..) remote control, that we called "télécommande" these years... Would you like that I change that in all entries including "Transport" and add a bz2 file here, or do you prefers in another issue? For the glue to bars.. I joined here what I have, but it's not on the rc1 build, it was the pre1-403 that I have build I can see loacate in gtk2_ardour/po : line 2155, as shown in the image joined session_properties_misc.png (166,430 bytes) gtk2_ardour_po.png (181,449 bytes) |
|
|
I replace the loacate image so it's faster for you to see it: and then I see that something is wrong in the translation too! I will fix it with "transport" lines of course, and check another time just to be sure no other error is included... Translation is not a quick'N'easy task and I don't think I can do that for a non-musical software ;) I will build the rc tomorrow morning too, and let you know about the glue to bars missing. Please tell me if you prefers another issue or add the new fix here? loacate2.png (135,219 bytes) |
|
|
updating the translation this morning I remember it clearly, after looking at the Studer MKII french specs! "défilement" is used for anything about the tape movement (or stop): it can be something in the hardware, the tape itself, or the movement (forward, rewind, play) "transport" is used for any man/machine interface that gives control on that movement (eg: Studer remote control that includes rec.ready/auto-input/tape play/locator/etc AND transport) is that ok for you if it's translated in that mood (that "everyone in business" can understand in french), or you prefers transport for every instance? |
|
|
I don't have any personal preference and my French isn't very good either. Yet for some reason I just thought "Transport Masters" -> "Maîtres du Défilement" sounded odd, so I thought I'd ask. Thanks for the explanation. So since this one is about user/machine-control, should it be "Maîtres des Transport"? |
|
|
Re: "For the glue to bars.. " Could it be that is is due to "&" (et sign). |
|
|
It wil be "transport"... I'll try to post here a new patch ASAP, to respond to your 2 notes before. Let say thursday evening, with some luck! |
|
|
All "&" have been replaced, except in 2338: small>i>This can later be changed in Preferences > Appearance./i>/small> Next build, I'll tell you if it was the point! Every "transport" talking about HMI is replaced |
|
|
There were various comments by other translators on Ardour IRC yesterday. Many translations are too long and lead to an unusable GUI. e.g. "Lock" -> "Pas de déplacement horizontal" results in a very big dropdown. It should probably be "Verrouiller" (and "Slide" -> "Glisser" etc.) Various similar phrases that are used in the main toolbar are likewise too long. They should be single-words. Would you mind coordinating this with Olivier Humbert (trebmuh@tuxfamily.org) and Julien Rivaud (frnchfrgg@free.fr)? |
|
|
The 0005 update was merged in 6.0-rc1-77-gf1ec998653 |
|
|
Thanks for the addresses of Olivier & Julien, I will mail them |
|
|
|
|
|
No response from Olivier or Julien yet, but here is a new update with shorter translations. One of they have to be validated I think, it's for the playhead: "Cellule" which is twice shortest than "Tête de Lecture" but might be sort of confusing? Please let me know if it's better to reverse to "Tête de Lecture". Here's a screenshot so you can have a quick look at it. Could you please explain me the use of the "G" column in the Regions List that you can see in that picture? |
|
|
The screenshot looks nice! "Glued|G" the tooltip for that is "Region position glued to Bars|Beats time" : The region's position is not using absolute timecode, but the tempo-map to Music-time (tempo, time-signature). I cannot judge if "Cellule" is appropriate. ProTools uses "curseur de lecture" [1] for "Playhead". but that's even longer than "Tête de Lecture". [1] http://akmedia.digidesign.com/support/compressed/Pro_Tools_12_3_docs_FR.zip might be good for some inspiration regarding naming conventions. |
|
|
The 0006-update was applied in 6.0-rc1-129-gd94a747180 |
|
|
Thanks for the link to the PT docs, but I will stay on Ardour! More seriously, they shows (in 5 minutes, thanks Ctrl+F) that PT translators met the same "flavor': * they talk about "défilement" or "transport" for the same concepts we talked about up here, * they use "tête de lecture" or "curseur de lecture" depending the context, * sometimes they translate "scrubber" > "scrubbing", that I don't even searched in a french dictionnary! * etc... So I think that "Tête" will translate well "Playhead" and shorten "tête de lecture". I mean, there's nothing else related to "tête" in a DAW (header is "en-tête")), and "tête" is understood easily by one who remember the head block in multitrack hardwares. "Cellule" was sounding strange, that's why I have asked you about it. Those PT docs were good to brainstorm! I don't see other strange words in the .po, and can't translate more Lua/MIDI/Video at the moment, so it seems so my work is done now with that last update. I have added some to the tooltip you can see in the image, to explain the functions that I have questionned myself up on for years, just in case some other do!! It was nice, first because it forced to practice english, reading the context with Poedit showed some functions unused, and test to see if Ardour really makes what translations describes has helped to discover new features. Last but not least, it have eased that period out of time we are all living... Could you please add my name to the french translators line in the .po? Capture du 2020-04-28 18-52-15.png (60,987 bytes) |
|
|
I've added the name in the source and applied 0008-update in 6.0-rc1-131-g571067f70b |
|
|
Thanks Robin, I have read "We need people to update and/or write new sections in the manual 36 to reflect all these changes. Please get in touch if you’d like to be a part of this effort." in: https://discourse.ardour.org/t/development-update-6-0-pre1-now-ready-for-testing/103072 Is where you read those lines the good place to get in touch ? |
|
|
The forums are fine to use to get in touch, or the ardour-dev mailing list. |
|
|
ok thanks, I'll go there |
|
|
Using Ardour6 I found some lines not fine. Here's an update. |
|
|
Applied as 6.0-rc1-370-g6c72862801 |
|
|
Issue has been closed automatically, by Trigger Close Plugin. Feel free to re-open with additional information if you think the issue is not resolved. |
- Anonymous
