Improve translation key consistency #265

Closed
tobscure opened this Issue Aug 27, 2015 · 7 comments

Comments

Projects
None yet
2 participants
@tobscure
Member

tobscure commented Aug 27, 2015

We need to solidify our strategy for naming translation keys, and apply it globally for consistency. Initial discussion took place here: http://discuss.flarum.org/d/336-potential-l10n-stumbling-blocks/10

The basic idea is to have context-related suffixes for similar translations (see stumbling block 4) and prefixes to group related translations (stumbling block 5). However, this strategy needs further refinement, and then needs to be applied.

What needs to be done:

  • Go through all components in js/forum/src/components, looking for instances of app.trans, cross-matching the keys with their translations in locale/en.yml. Rename keys where necessary so that they are consistent and descriptive.
  • Through this process, come up with a brief list of rules/guidelines to follow when naming translation keys.
  • Apply the strategy to default extension translations too.
@tobscure

This comment has been minimized.

Show comment
Hide comment
@tobscure

tobscure Aug 27, 2015

Member

@dcsjapan you might be interested in tackling this :)

Member

tobscure commented Aug 27, 2015

@dcsjapan you might be interested in tackling this :)

@tobscure tobscure referenced this issue Aug 28, 2015

Closed

v0.1.0 roadmap (old) #74

19 of 53 tasks complete

@tobscure tobscure added the Cleanup label Aug 28, 2015

@dcsjapan

This comment has been minimized.

Show comment
Hide comment
@dcsjapan

dcsjapan Aug 29, 2015

Member

I'd be happy to ... give me a while to wrap up the aftermath of my translation job and I'll get right on it.

Member

dcsjapan commented Aug 29, 2015

I'd be happy to ... give me a while to wrap up the aftermath of my translation job and I'll get right on it.

@dcsjapan

This comment has been minimized.

Show comment
Hide comment
@dcsjapan

dcsjapan Sep 2, 2015

Member

Okay, I plan to get started on this soonish.

Do you need me to keep a log of key name changes? Any preferences regarding format of the log?

(Come to think of it, I suppose such a log might be of use to the translators, too...)

Member

dcsjapan commented Sep 2, 2015

Okay, I plan to get started on this soonish.

Do you need me to keep a log of key name changes? Any preferences regarding format of the log?

(Come to think of it, I suppose such a log might be of use to the translators, too...)

@tobscure

This comment has been minimized.

Show comment
Hide comment
@tobscure

tobscure Sep 2, 2015

Member

Yes a log would probably be helpful :) Thanks!

Member

tobscure commented Sep 2, 2015

Yes a log would probably be helpful :) Thanks!

@tobscure tobscure added this to the 0.1.0-beta.3 milestone Sep 4, 2015

@justjavac justjavac referenced this issue in justjavac/Flarum Sep 7, 2015

Open

Flarum v0.1.0 开发路线图 #3

18 of 53 tasks complete
@dcsjapan

This comment has been minimized.

Show comment
Hide comment
@dcsjapan

dcsjapan Sep 23, 2015

Member

Just adding a mention here for completeness' sake:

#536

This more or less takes care of the first bullet point in the OP.

Prerequisites for using the changes are noted in the PR description!

Member

dcsjapan commented Sep 23, 2015

Just adding a mention here for completeness' sake:

#536

This more or less takes care of the first bullet point in the OP.

Prerequisites for using the changes are noted in the PR description!

@tobscure

This comment has been minimized.

Show comment
Hide comment
@tobscure

tobscure Jan 7, 2016

Member

Closing as this is done. Thanks again @dcsjapan!

Member

tobscure commented Jan 7, 2016

Closing as this is done. Thanks again @dcsjapan!

@tobscure tobscure closed this Jan 7, 2016

@dcsjapan

This comment has been minimized.

Show comment
Hide comment
@dcsjapan

dcsjapan Jan 7, 2016

Member

I thought this had already been closed! ... You're very welcome!

Member

dcsjapan commented Jan 7, 2016

I thought this had already been closed! ... You're very welcome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment