You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For most of the log lines, they don't need entries for other languages.
Some log lines may benefit from having other languages, e.g. Map, StartsUsing, or Ability, though I can't say for certain as I don't do any translations, nor do I write triggers against non-english log files.
Additionally, it may be good to note somewhere or somehow what documents still need translations, though that's only tangentially related to this issue. (e.g. there is no /docs/ko-KR/LogGuide.md)
Either way, until #138 and #139 are merged, we can't really flag these as not needing translation since they're being moved to a new file as part of those PRs.
Closes#157. I agree with @valarnin 's point there that certain example
log lines could benefit from translations.
But since we do not have any translated versions of `LogGuide` at the
moment, and the unit tests are all based on the `en` lines, I think it
makes sense to at least suppress the warnings for now to prevent clutter
on the `missing_translations` pages until it becomes relevant.
Closes#157. I agree with @valarnin 's point there that certain example
log lines could benefit from translations.
But since we do not have any translated versions of `LogGuide` at the
moment, and the unit tests are all based on the `en` lines, I think it
makes sense to at least suppress the warnings for now to prevent clutter
on the `missing_translations` pages until it becomes relevant. ef00e90
Hi there,
I don't think we should translate the examples lines, is it possible to remove it from the missing translation page ?
Regards,
moon.
The text was updated successfully, but these errors were encountered: