Why do my translation files still contain original source strings?



1 comment

  • Avatar

    This really doesn't work for us. We have our own fallback logic.


    For example: nl-BE should fallback to nl first, then to en and only then to our base language, tlh-KL

    Now, if a translator wants to override something in nl for nl-BE, he has to copy the entire nl file and adjust the changes. This really doesn't work well.


    I think you should leave the fallback to the consumer of the api, or allow fallback configuration.

    Comment actions Permalink

Please sign in to leave a comment.