Thank you for the good news and a big compliment to all the contributors who have saved Frescobaldi for now!
I will try and look through everything as soon as possible. This time it probably will not necessitate a lot of changes, but since Frescobaldi has many commands, menu items and other features, I will have to look in every corner, so nothing remains unattended. And there may be the manual, too. This may take a while, but I am happy to take care of it and to contribute at least to the localisation. Unfortunately I am not a programmer, and for something like Frescobaldi the learning curve would certainly be too steep for a beginner. At least I'd expect so. All the best Hajo Baess Am Donnerstag, dem 16.01.2025 um 11:04 +0100 schrieb Federico Bruni: > > > Il giorno mer 15 gen 2025 alle 14:13:30 -08:00:00, Knute Snortum > <ksnor...@gmail.com> ha scritto: > > On Wed, Jan 15, 2025 at 1:51 PM Hajo Baess <ha...@posteo.de> wrote: > > > I can't wait to see Frescobaldi 4.0.0 being released. In the > > > flatpak > > > everything seems to be ok so far (although I have not done a > > > real > > > in- > > > depth testing). The only thing - a glitch which already was > > > present > > > in > > > 3.3.0 - is the English context menu when you right-click in the > > > editor > > > although I use the German localisation. > > > > I don't see this is the Frescobaldi issues tracker. If you want to > > enter it, here's the URL: > > > > https://github.com/frescobaldi/frescobaldi/issues > > No need to open a new issue. It's already tracked here: > https://github.com/frescobaldi/frescobaldi/issues/1735 > > > > > > > Last year I have done this localisation which was almost a > > > complete > > > rewrite of the older one. Maybe I should look over it again, or > > > should > > > I better wait until the next version will have been released? > > > What's > > > your opinion? > > > > No reason to wait if you want to get started on it. > > > > New translations are welcome. > The target release date is 20th of January, but it depends on how the > Windows and macOS packaging is going to work (see the latest PRs on > GitHub). > > > >
