the version from ardour.org ?
Yes. This one indeed.
That seems … impossible. Nothing has changed about the way we build Ardour.
What happens when you try to enable translation and then restart Ardour?
Same here, with 2 differents machines
Debian 12- Mate.
French translation doesn’t work anymore.
translation is enable in preferences.
Problem acknowledged, though not yet understood. Copying the actual executable for 8.11 into the install tree for 8.10 works as expected, so the problem is more subtle than “it wasn’t built with translation support”). Will keep you posted.
1 Like
I’ve done a bit more testing. There’s definitely some weirdness going on with tempo-mapping.
Last night I found that 8.11 wouldn’t move beats within a bar, only the first beat.
I had then installed multiple earlier 8.x versions, some of which I have used in the past year and moved internal beat lines without issue.
I experienced a couple of versions that tempo-mapping didn’t work correctly (tempo markers weren’t placed where I tried to drag the first beat of the bar) and none of the versions I tried (8.1, 8.2, 8.4, 8.6, 8.9, 8.10, all downloaded from here) allowed me to move non-first-beat lines.
However, tonight it’s a different story. I went back to a session where I know I’d dragged beat lines around within a bar and found it was created with 8.6.
I created a new session in 8.6, imported the original guide piano part from the above-mentioned session and successfully tempo-mapped the bar – and the beats within that bar – where there was a rapid slowing down of tempo. In other words, where it didn’t work last night, it worked as expected just now. I’d created a new session yesterday and recorded audio to tempo-map and only the first beats could be moved then. Not so tonight.
Opening tonight’s 8.6 test session in 8.11 and it too worked as expected i.e. any beat could be dragged around.
I repeated the same test in 8.11: creating a new session, importing the guide piano part, tempo-mapping the bar with the rapid ritardando, including all beats within that bar, not just the first one i.e. it worked as expected where last night it hadn’t done so when I created a test session and recorded audio.
Sorry, i should have mentioned it in my first post, but i already tried to deactivate and re-activate translations and restart Ardour in between. Which didn’t change anything.
I can live with it that said, but i guess it might be uncomfortable for some.
The Linux packages for 8.11 on Intel/AMD x86_64 architectures have been updated so that translation works again. Download it again and things will be working.
macOS packages will be updated later this evening (in a few hours).
There was no bug with the executable program at all, but the packages contained incorrectly built “message catalogs”. It was actually sort of a cool bug, but it took a day or more to figure out what was going on.
5 Likes
Thanks for the quick fix. Translations works again.
Will this be available in the Ubuntu studio repositories? (curently 8.10)
I believe that is the responsibility of the ubuntu package maintainers. The official Ardour builds are available here - Download Ardour | Ardour Community
Hi, do you plan to update macos package (for the translation issue)
I’m now using ardour 8.11 (updated from 8.10) with macos intel 10.15
That’s not a big deal but I got used to french version and it’s quite disturbing coming back to english version (though i’m very comfortable with english).
Thanks
The macOS and Linux packages were all updated within a couple of days. We did not do a new release because there were no code changes required to fix the issue, it was just a packaging problem. Unless you obtained 8.11 during the first 2-3 days of its release, the problem is already solved.
See earlier in this thread: Ardour 8.11 released - #16 by paul
I just downloaded the new release this mornig but the issue remains
If you think I can send you a log file or something else to understand what happens, do ask.
But for now that’s okay. Hope the problem will miraculously disappear in next releases 
thanks
Have you made sure that Edit → Preferences → Appearance/Translations has “Use translations” checked?
Also make sure you have some files in your Ardour8.app/Contents/Resources/locale/fr_FR(or similar)/LC_MESSAGES folder
The problem was known to be fixed. It is more likely you have a more mundane issue, like the one Peder described above. Ardour does not translate by default.
Yes “use translation” is checked 
But I don’t have any “locale” folder!
/Applications/Ardour8.app/Contents/Resources
├── ArdourMono.ttf
├── ArdourSans.ttf
├── InfoPlist.strings
├── appIcon.icns
├── ardour.keys
├── ardour.menus
├── clearlooks.rc
├── default_ui_config
├── export
├── fonts.conf
├── icons
├── mcp
├── media
├── midi_maps
├── mixer_settings
├── osc
├── patchfiles
├── plugin_metadata
├── rdf
├── resources
├── scripts
├── system_config
├── templates
├── themes
├── typeArdour.icns
└── web_surfaces
I just downloaded the 8.11 Demo for Mac and I can’t get the translations to work either.
The time stamp on the files and foldes says Feb 6 04:52.
If I read the osx build script correctly there should have been a Resorces/locale folder with all the language subfolders in it, but as pierx pointed out it’s nowhere to be found.
Maybe the demo doesn’t contain any translation files but I suppose pierx is using the paid-for version.
Indeed it is AWOL. if you read the osx build script more closely you’ll notice that the find command which looks or translations used GNU extensions (not available on apple’s BSD find), so translation files were not copied.
Ardour - Log file: build_log.txt shows this…
find: *.mo: unknown primary or operator
now fixed since Fix translation bundling, use BSD*find syntax · Ardour/ardour@125fd41 · GitHub
2 Likes
Nice.
So there should be a a new macOS package in a few days, I take it?