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

Feature Request - Bulk copy from original #142

Closed
garretthyder opened this issue Apr 17, 2018 · 4 comments
Closed

Feature Request - Bulk copy from original #142

garretthyder opened this issue Apr 17, 2018 · 4 comments
Assignees
Milestone

Comments

@garretthyder
Copy link
Collaborator

Locale used: English Variants

Hi @Mte90 I realize this is more useful for variant languages like en_CA, en_AU, etc.
But am thinking a massive timesaver for those variant languages, and possible other variants when GlotPress updates to have language hierarchies, would be to have an additional option in the bulk dropdown for copying from the original.
Currently to do this you open the row, then click 'Copy from original' and finally 'Add translation'. Then rinse and repeat for the next one.
This bulk option would enable you to copy 15 strings in two steps.

Hope that makes sense,
Cheers

@Mte90
Copy link
Owner

Mte90 commented Apr 17, 2018

So you mean that all the translated terms are injected in the textarea?

I am wondering if it is the right behaviour. Right now in glotpress we are evaluating what to do for terms with more than 1 translation.
In any case seems that I can implement without so many problems.

The best probably is another link near copy from original with a text copy translated terms or something like that. Maybe with an hotkey :-)

@garretthyder
Copy link
Collaborator Author

Sorry @Mte90 although that's a cool idea, wasn't what I was going for.

I'm thinking in this dropdown menu for bulk actions add a 'Copy' option like this;
screen shot 2018-04-17 at 10 05 14 am

And when you have rows checked off and you select this action it would copy the original string and submit it as the translation.
This only really helps in english variants where most strings have no adjustments needed so just get copied and submitted.

In my workflow I would scan the results and only check off those which don't have glossary terms and then I'm left with only strings that need attention.

Hope that clarifies.
Thanks

@Mte90
Copy link
Owner

Mte90 commented Apr 18, 2018

Seems that can be interesting, maybe the auto insert and submit can have a check for translations where there only terms with a glossary to avoid bad subsmission of translation with incomplete stuff.

@garretthyder
Copy link
Collaborator Author

Good call, maybe it would submit all rows without glossary terms but open those with terms and have a warning like the current behaviour for submitting a single string with untranslated glossary term.

@Mte90 Mte90 added this to the 1.3 milestone May 6, 2018
Mte90 added a commit that referenced this issue Jul 4, 2018
@Mte90 Mte90 closed this as completed Jul 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants