Open binali-rustamov opened 4 years ago
Are there any updates on this Issue ?
Unfortunately, the owner of this repository is no longer able to maintain it. Hopefully, someone will fork it and continue the development.
Are there alterantive repositorys or solutions to this ?
I’ll create fork of the repo in the near future.
Any news about that? I would need Avalonia support and .net 6 support. I've already forked the repo and want to help in this case
If someone stumbles again in this thread: PR for net6 and new csproj format is made
What's the story? The repo is obsolete? There is a fork continuation of the effort? Speaking now 'the other side' of core WPF.
I believe the author passed away or had some kind of serious illness (https://dagbladet-holstebro-struer.dk/holstebro/doed-i-135-minutter-christina-haedres-for-at-redde-sin-mand) and there was no person in place to take over ownership. I wouldn't mind taking over but don't know how one could do that.
I believe the author passed away or had some kind of serious illness (https://dagbladet-holstebro-struer.dk/holstebro/doed-i-135-minutter-christina-haedres-for-at-redde-sin-mand) and there was no person in place to take over ownership. I wouldn't mind taking over but don't know how one could do that.
Really, how sadly tragic indeed.
@D-Bullock can you contact me offline from here? I'd like to discuss the possibility you and I picking it up from here, branding issues, and so on, so forth, at your earliest convenience. Cheers, best.
Putting out a general notice, I am keen on continuing the project, under this repository, or a different one, if necessary. I am gathering interesting, thoughts, etc, around the migration planning into contemporary netX-windows
, for starters. Can think about most appropriate .NET Framework
targets as well, before all said and done. So far so good doing the initial migration, but there are couple of potential kerfuffles I feel should be sorted out before making it official bare minimum in a v2.0
. May be able to publish under the same package handle, but if not, will publish in a separate one; will make an effort to keep the RootNamespace
consistent, however, as it is here today. Contact me privately if anyone is interested to see this effort continuance. Cheers 🍻
Q: does anyone happen to know what LC_MESSAGES
is, in the context of these projects? As a locale path, it seems a tad extraneous to me? Perhaps there is some historical basis for it? Partially answered my own question there, but if there are insights, would be fantastic as well. Cheers 🍻 best. Thank you...
Honestly, I do not know what sort of community participation there should be, but I went ahead and created a discord channel committed to things NGettext where folks may formally informally join, contribute, discuss, and where potentially announcements may appear, etc.
Hello, dear! Do you have any plans to add .net core 3.0 support? I can help you with that. :)