Yup. The problem is that using it with the current language/translations architecture in RT would be… challenging to say the least. I think it would be less effort to completely rework RT to use gettext than to try and get weblate to play nice with the current translations setup. Using the pixls Weblate instance is one of the main reasons I’m looking into gettext
In addition to the docs items @darix linked, I’m definitely going to be taking some inspiration from how darktable has integrated gettext with cmake too.
Note that rawpedia on weblate won’t be possible, since authors write in several different languages. In fact, language management will likely be an issue, since there won’t be a primary authoring language.
I find Rawpedia to be quite helpful. Thanks for providing this resource.
Some (English) Rawpedia pages currently display long sections of “garbage” when I try to view in Firefox. (I tried multiple Firefox versions, all Linux).
The issue might be due to one of the templates. For example, Template:K
It is possible that it is something unique to my setup. If so, I apologize. Maybe someone can verify that these pages render correctly or not. But, it seems possible that the issues are related to the recent wiki software updates.
I can confirm they don’t render properly in Firefox on Windows 11. I have no other browsers installed, other than Edge (which I try to not run because it screws up defaults, etc., when it does).
Yep, I do see the same thing and you might be right with the template being the problem and not transcluding correctly. I’m back from vacation and will hopefully have some time to look at this more now.
It was indeed an extension that parsed those templates better ParserFunctions. I’ve just re-enabled that extension and it seems to have corrected the issue. Thanks for the heads up!
I think part of it was waiting for a creation of/migration to a RawTherapee github org - I know @Morgan_Hardwood wanted to do some thinking along those lines as far as actual org naming the last time the topic was discussed?
Hopefully I’ll have more time to actually do coding contributions again (as opposed to just popping in here to discuss things) starting sometime in March.
Sorry for the radio silence all. I’ve been pushing hard to do a website migration for my job that is consuming my time at the moment. This is near the top of my personal projects list when I can find some time!
Heh, it happens. Actually this discussion has inspired me to push for an internal wiki at work to potentially get migrated to a similar implementation (git + hugo). For our software teams I think it’s a no-brainer, but the whole concept might get sunk by the problem of git being alien to non-software types. Politically I think sharepoint is going to win in the end.
Sharepoint. From the company that just yesterday told me in my wife’s Excel spreadsheet that it was read-only, had to save it as another file name, and I went alooking in the ACLs and NOWHERE FOR ANY USER OR GROUP WAS IT MARKED READ-ONLY!!! AAIIIEEEEEAAAA&%^&^&@$!!!
Going downstairs now to install larger hard drives for our picture repository, in nice, simple, easy-to-understand Unix…
Yup. MS has improved greatly over the years (I like VSCode, and WSL2 is a wonderful thing if you’re in a primarily Microsoft shop or are stuck using software that is Windows-only and will likely remain that way for a LONG time…), but Sharepoint is one of their “legacy” products that I dislike.
There’s been a slow push towards containerization/linux/etc in my company, but in general that’s happening within engineering and product development, and IT considers that “engineering’s problem” or “well we’ll hand that to our dedicated engineering support team who are vastly understaffed”.
My old employer was a big user of Sharepoint. On my program, however, it was good old SMB that saved the day, network file shares we could see across the time zones.
I channel my son for ‘modern’ IT vibes. He’s worked for small companies, getting them into the VM/containerization world. His world is all Windows though, Azure and such. He comes to me when he needs Unix stupid pet tricks…
Heh. Big pressure to consider Azure DevOps, I have major concerns it might be too “windows-y”. There’s some discussion of Github Enterprise which I would not mind. There’s no way we’ll be leaving Atlassian JIRA, but frankly I’m hoping that the rest of our Atlassian infrastructure (originally chosen because “integrates with JIRA” but honestly JIRA will integrate equally as well with other solutions…) gets replaced with anything else. I have grown to really hate Bitbucket as a git frontend (per-file history UI/UX is garbage for example, cannot check out a pull request without read access to the PR issuer’s fork, etc.)
(big red flag for ADO that Microsoft has two almost entirely parallel product lines there…)
I’m running into this with my work hugo migration and I’ve actually had good feedback from using the gitlab webui to edit files in-place. Most users just need to edit content markdown files so they can do this quite easily through that interface and never need to know the ins-and-outs of git to do it.
You could even theoretically make the hugo /content/ directory a separate repository so they can only edit content files and not the site config or layouts. And now that I’m saying that out loud I think it might make sense in some cases to explore that.
Another option is to integrate a CMS front-end like https://www.netlifycms.org/ - we actually had that setup for the main RawTherapee website once upon a time to test it and it seemed to work quite well. The benefit there is the WYSIWYG preview of the markdown along with an editorial review process baked in (draft, awaiting approval, published, etc).
I’m actually starting to look at things like https://fastapi.tiangolo.com/ to produce API endpoints for any data submissions that need to happen and to integrate it with my static site for low-effort tasks (filling in a form or something similar that just needs to do something with the data that’s simple). This way the form submit just hits a predefined API endpoint that does one thing mainly.
My old company was sharepoint as well and it’s just a mess of tech stacks all smooshed together in weird and convoluted ways I thought…
One of many reasons to not be using bitbucket. That’s a major part of the problem - Bitbucket Server/Datacenter’s licensing is such that we have to be careful who has an account there. Unless we can escape Bitbucket, I don’t think the hugo approach will be viable. (I am starting to push more aggressively to say that we should consider alternatives to Bitbucket because the JIRA integration is frankly so weak we wouldn’t be missing out on anything - especially since it doesn’t even work half the time.)
Interestingly one of our teams never left gitlab, so I’m considering starting to push for us to just go back.
Yup. This has been stalled lately - I’ve been pretty busy with other things, and the talk of moving all RawTherapee-related repos to a github organization has also stalled.
