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

bsc#1080332, split large strings into smaller combination #9

Merged
merged 2 commits into from Feb 13, 2018

Conversation

Projects
None yet
3 participants
@nick-wang
Copy link
Contributor

commented Feb 11, 2018

Split the large help strings source into smaller strings combination to ease the work of translation, version 4.0.0

@nick-wang nick-wang force-pushed the nick-wang:1080332 branch 5 times, most recently from 8b6c65f to f9f01ff Feb 11, 2018

@nick-wang nick-wang force-pushed the nick-wang:1080332 branch from f9f01ff to e2132d6 Feb 11, 2018

@stanislav-brabec

This comment has been minimized.

Copy link

commented Feb 12, 2018

Now strings look much better. The change will need adjustment of all translations in yast-translations, and additionally some Weblate updates to keep existing suggestions. I just locked the Weblate project.

@lslezak
Copy link
Member

left a comment

Yes, the string are now much easier to translate, thanks! 👍

@lslezak lslezak merged commit 47644ea into yast:master Feb 13, 2018

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
@lslezak

This comment has been minimized.

Copy link
Member

commented Feb 13, 2018

@nick-wang: I still have some questions:

Do we actually need such long and detailed help texts?

I mean it's OK to have a good help text but is this text already available somewhere else? Does our documentation cover this topic? Or is there some online documentation? In that case a simple link might be enough...

@stanislav-brabec

This comment has been minimized.

Copy link

commented Feb 13, 2018

I am not sure what is the standard way to translate helps, but all-in-one-msgid was surely a wrong way. Imagine that English text changes one character, and the whole string becomes fuzzy.

However these strings were translated. For several languages not only once, but even twice. Once by community, second time by contracted translators. I am now working on splitting them by articles, so reviewers will be able to compare both translations.

If you will migrate translations in future, please let me know to save expenses. It contains hundreds of pages of text.

@stanislav-brabec

This comment has been minimized.

Copy link

commented Feb 15, 2018

After the split, the gettext indicates that the exactly same article appears on two places. E. g. the one starting with "

check timeout = n". Is it intended?

Now we have up to 4 different translations for such articles: instance 1 from the community, instance 2 from the community, instance 1 from contracted translators, instance 2 from contracted translators.

@nick-wang

This comment has been minimized.

Copy link
Contributor Author

commented Feb 22, 2018

@lslezak sorry for the late reply, since i just back from a long vacation.
Most contents are included in man page, besides some limitation and recommendation in yast module.
So yes, I think i can simplify it in the next release.

@nick-wang

This comment has been minimized.

Copy link
Contributor Author

commented Feb 22, 2018

@stanislav-brabec Thanks for the translation.
This time only split into pieces without any modification. I think i can simplify the text in future to ease the work.

@stanislav-brabec

This comment has been minimized.

Copy link

commented Feb 22, 2018

To save existing translation work. I just spent several days in splitting of existing translations. Translations as well as suggestion were successfully processed.

The old source repeated some identical columns in two strings. It forced translators to translate the same text twice. As SUSE Linux Enterprise had its own translation in past, up to 4 translations exists for some strings. It was a big waste of translators work.

Now these 3 translations exist as suggestions, at least until translators will review it.

In case of future change, please keep in mind, that the total amount of translation work in these strings reached ~50000 words. If you will drop or change these helps, all this work will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.