Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Skip gettext steps when disabled #18

Closed
dankohn opened this issue Jun 29, 2017 · 1 comment
Closed

Skip gettext steps when disabled #18

dankohn opened this issue Jun 29, 2017 · 1 comment
Labels

Comments

@dankohn
Copy link

dankohn commented Jun 29, 2017

In our repo, we have disabled gettext support. However, running the sync produces:

$ rake translation:sync
* Downloading YAML source editions.
* Applying YAML source editions.
* Updating POT file.
* Generating POT file from YAML files.
* Saving new PO files.
* Creating new MO files.
* Saving new translation YAML files.
* Saving new localization YAML files (with non-string values).
* Collecting YAML localization entries

----------
Use this URL to translate: http://translation.io/david-a-wheeler/cii-best-practices-badge
----------

Shouldn't the middle 4 steps involving POT, PO and MO files be skipped?

@MichaelHoste
Copy link
Member

MichaelHoste commented Sep 1, 2017

They are somewhat skipped using an empty list of files to parse : https://github.com/aurels/translation-gem/blob/master/lib/translation_io/client/base_operation/update_pot_file_step.rb#L9

We can't unfortunately totally ignore Gettext since we use its internal format to sync with the backend either with YAML or Gettext.

But it should not slow down the process of syncing. Is it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants