Updated documentation covering Angular 18
CodeAndWeb opened this issue · 11 comments
Angular 17, 18+
The new documentation now covers installation on
Angular 18+ and is divided into smaller, more readable sections, making it
easier to digest than this big README. It also documents the additional
interfaces and explains how to develop custom plugins.
New documentation: https://ngx-translate.org/
In addition to that, a getting started tutorial is available here:
How to Translate Your Angular App with NGX-Translate
This Demo project
contains 3 simple example projects for Standalone components, NgModules, and
how to use the message format compiler. The branches contain the same
projects for older Angular versions.
Greetings are you part of the ngx-transalate team are you planning to take over the project from combe?
I currently have additional privileges, such as handling tickets on the project: https://github.com/orgs/ngx-translate/people.
However, there isn't a formal "team" structure in place. We've never had meetings to discuss project direction, decision-making, or processes.
I proposed taking over ngx-translate two years ago, but the offer was declined. Olivier wanted to work on a translation editor/internationalization suite himself, but it seems that project has stalled as well (see Locl).
I tried reaching out to Olivier again last week but haven’t received any response—neither via email nor on social media.
I’d like to take over the project since we have the resources to maintain ngx-translate long-term and keep the library active. We develop a translation editor called BabelEdit, and while ngx-translate will remain a free, open-source library, BabelEdit provides the necessary resources for us to continue supporting it. As long as people use BabelEdit to streamline their workflow, we can sustain ngx-translate.
We've been developing and maintaining software tools with regular updates and support since 2010, so we fully understand the commitment required to maintain a project long-term.
If I don’t hear back from Olivier soon, the only remaining option might be to fork the project.
essentialy what we have done is when we dont hear back from the maintainter we put our our organization in front of it @windmillcode/[PACKAGE NAME] you might as well do the same . I know that you have enough resources but if there is any collaboration, promotion or help we can provide let me know. You can also connect with me in the Angular discord im k_j_code there
I've meanwhile forked the project:
@codeandweb/ngx-translate
@codeandweb/http-loader
The current work in progress is available as a beta version on npm.
Greetings our organization's library depends on ngx-translate would like to collaborate especially on testing issues .Even promote by writing articles https://windmillcode.github.io/Windmillcode-Angular-CDK-Docs/
Can you make fork public? Probably all should go migration to your new npm package and all issues will be open at that place
It's already available. I've released V16 of my fork last week. This migration guide explains how to switch to my fork and also explains the benefits of doing so:
Yes, but do we still come to the ngx-translate/core repository to create issues and do PR?
The links on https://ngx-translate.org point to https://github.com/codeandweb/ngx-translate - my forked repo.
I can't do anything here since Olivier ignores all communication and I don't have the right to change anything here.
If all goes well, this should be arranged, soon see #783 (comment)
Got permissions by Olivier to publish updates here...