gettext-parser
gettext-parser copied to clipboard
Parse and compile gettext po and mo files, nothing more, nothing less
In our project we use both tools for different parts of our translation pipeline. Unfortunately the inconsistency creates very noisy commits. Bringing them closer together will make reviewing changes made...
The main motivation behind this PR is that `readable-stream` is difficult for bundlers to handle due to circular dependencies (see https://github.com/nodejs/readable-stream/issues/348). I believe this might be the cause behind the...
I'd like to save the name of the control variable for plural forms. I will amend `_parseComments` and `_drawComments` to accept and output ` #$ varname ` bound to `comments.control`...
I'd like to get rid of the 'comments' ... how can I do that?
For now, to be able to pass multiple references for translation i need to concatenate them with `\n` symbols. Would be great if we could pass those references as array....
I have a .po file whose translations are handled with `Poedit` and I get _obsolete entries_ in my `.po` files. The parser fails when it encounters them. ## Reproduction `en.po`...
this is the PR that contains all the changes listed in #82 There are no dramatic changes, however, we may decide to move to 8.1.0 (and not 8.0.1) because of...
In order to avoid making a huge PR with generic changes, I'm going to write a tracking issue here that lists the changes I would like to propose, in that...
This pull request addresses the need for consistent documentation within the repository by adding JSDoc comments where they were previously missing. This enhances code readability and maintainability. Each file has...
In this PR we are going to update - [X] *Readme* replaces `require` (cjs) with `import` (esm), adds installation instruction - [ ] package.json - version update according to semver...