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

Jump to bottom

The import of source texts should not be done on the project import page #195

Open
GoogleCodeExporter opened this issue Mar 13, 2015 · 1 comment
Open

The import of source texts should not be done on the project import page #195

GoogleCodeExporter opened this issue Mar 13, 2015 · 1 comment
Labels
auto-migrated Complexity-High Priority-High Type-Enhancement Version-2.1

Comments

@GoogleCodeExporter
Copy link
Collaborator 

The creation of files and contexts is a thing that affects all locales, thus 
the import of source texts should be separated in order to make users aware of 
the difference between doing an import of source texts and doing an import of 
translations.

See option "Do not add texts, just add found translations for existing texts" 
in the import panel.

Original issue reported on code.google.com by alex...@gmail.com on 27 Sep 2011 at 6:01
@GoogleCodeExporter
Copy link
Collaborator Author 

You can't do an import for all locales from the web interface.

Original comment by alex...@gmail.com on 12 Oct 2011 at 6:05

  • Added labels: Version-2.1, Complexity-High

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Complexity-High Priority-High Type-Enhancement Version-2.1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter