Search Unity

Bug Attribute "Smart" not applied for new Locale (string tables)

Discussion in 'Localization Tools' started by zdolezal, Jul 21, 2021.

  1. zdolezal

    zdolezal

    Joined:
    Sep 27, 2017
    Posts:
    75
    1) Have table with some smart strings.
    2) Create new locale
    3) Export / import new localizations for new locale (maybe optional)
    4) Smart flags are not set for new locale. -> you need to check all entries and click it manually
     
  2. karl_jones

    karl_jones

    Unity Technologies

    Joined:
    May 5, 2015
    Posts:
    8,281
    If I understand correctly this is by design. We don't assume that an entry will be smart just because it is for another Locale.
    We could look into it and maybe if all the entries are smart then set it to be the same or parse the string and see if it's smart. Can you please file a bug report and we will look into it?
     
  3. zdolezal

    zdolezal

    Joined:
    Sep 27, 2017
    Posts:
    75
    I haven't had such case tbh...

    Once smart in the source language, smart in all others as well for every one of them.
     
  4. karl_jones

    karl_jones

    Unity Technologies

    Joined:
    May 5, 2015
    Posts:
    8,281
    Yeah it does seem to be more common. At the moment the flag for smart is stored on a per entry basis so when a new entry is added the value is defaulted to off. It does make sense to turn it on if all other entries are the same. I'll add a ticket to look into it as a new default.
     
  5. zdolezal

    zdolezal

    Joined:
    Sep 27, 2017
    Posts:
    75
    That seems like a good solution, thank you.
     
    karl_jones likes this.