Currently localization export (manual or by packager) brokes multiline phrases and causes ingame errors. Just example:
Before
L[ [=[Enter spell ID or name (case sensitive) and press OK]=] ] = [=[Gib die Zauber-ID oder den Zaubernamen ein (Groß-/Kleinschreibung beachten) und Drücke OK ]=]
Now
L[=[Enter spell ID or name (case sensitive) and press OK]=] = [=[Gib die Zauber-ID oder den Zaubernamen ein (Groß-/Kleinschreibung beachten) und Drücke OK ]=]
This issue affected my add-on Rarity as well. Currently I'm unable to post updates to that add-on due to this. I submitted a ticket and Torhal responded, saying he has made the developers aware of the issue, and it is affecting multiple add-ons.
Also, in packages tagged as "Alpha" localization is not filled:
local L=l:NewLocale(me,"enUS",true,true)
--@localization(locale="enUS", format="lua_additive_table" , escape-non-ascii=true, same-key-is-true=true, handle-unlocalized="blank" )@
L=l:NewLocale(me,"ptBR")
if (L) then
--@localization(locale="ptBR", format="lua_additive_table" , escape-non-ascii=true, same-key-is-true=true, handle-unlocalized="blank" )@
return
end
L=l:NewLocale(me,"frFR")
if (L) then
--@localization(locale="frFR", format="lua_additive_table" , escape-non-ascii=true, same-key-is-true=true, handle-unlocalized="blank" )@
return
end
L=l:NewLocale(me,"deDE")
if (L) then
--@localization(locale="deDE", format="lua_additive_table" , escape-non-ascii=true, same-key-is-true=true, handle-unlocalized="blank" )@
return
end
L=l:NewLocale(me,"itIT")
if (L) then
--@localization(locale="itIT", format="lua_additive_table" , escape-non-ascii=true, same-key-is-true=true, handle-unlocalized="blank" )@
return
end
L=l:NewLocale(me,"koKR")
if (L) then
--@localization(locale="koKR", format="lua_additive_table" , escape-non-ascii=true, same-key-is-true=true, handle-unlocalized="blank" )@
return
end
L=l:NewLocale(me,"esMX")
if (L) then
--@localization(locale="esMX", format="lua_additive_table" , escape-non-ascii=true, same-key-is-true=true, handle-unlocalized="blank" )@
return
end
L=l:NewLocale(me,"ruRU")
if (L) then
--@localization(locale="ruRU", format="lua_additive_table" , escape-non-ascii=true, same-key-is-true=true, handle-unlocalized="blank" )@
return
end
L=l:NewLocale(me,"zhCN")
if (L) then
--@localization(locale="zhCN", format="lua_additive_table" , escape-non-ascii=true, same-key-is-true=true, handle-unlocalized="blank" )@
return
end
L=l:NewLocale(me,"esES")
if (L) then
--@localization(locale="esES", format="lua_additive_table" , escape-non-ascii=true, same-key-is-true=true, handle-unlocalized="blank" )@
return
end
L=l:NewLocale(me,"zhTW")
if (L) then
--@localization(locale="zhTW", format="lua_additive_table" , escape-non-ascii=true, same-key-is-true=true, handle-unlocalized="blank" )@
return
end
Alar: Can you check that file again? On the new system, every project can use the localization system, whether they use a VCS or manually upload their files - I'm betting you downloaded your alpha file before the localization processor ran on it, which is something your users will not be able to do.
Hi Torhal, actually I waited for it to be in the "approved" status, because I already noticed that in the "new" and in the "Under review" status localization is not yet ready (and it is absolutely logical too).
Now, it's localized.
Maybe you can check if the "approved" status is granted a bit too early.
Very often I tag alphas to check i did not messed something in pkgmeta or forgot a keywors substitution tag open, so I download it as soon as possible and the remove it because I dont want any user having it.
Knowing for certain when Curse is done packaging would be helpful (actually, the preferred solution would imho not to show the file at all until it's ready)
Now, we only miss the fix for the multiline keyboard and we will be good to go
Hi.
Currently localization export (manual or by packager) brokes multiline phrases and causes ingame errors. Just example:
Before
Now
I highlighted missing brackets.
Confirmed. Actually the issue is only in the key. You can have a multiline translation provided the key is not
This issue affected my add-on Rarity as well. Currently I'm unable to post updates to that add-on due to this. I submitted a ticket and Torhal responded, saying he has made the developers aware of the issue, and it is affecting multiple add-ons.
I'm also affected by this issue. Please let us know when it's fixed so we can repackage addons.
We have a ticket in for this currently, sorry for the delay guys
Thank you for responding! I just wanted to point out that this issue is a critical blocker—anyone affected by it cannot use the Curse platform at all.
Also, in packages tagged as "Alpha" localization is not filled:
Alar: Can you check that file again? On the new system, every project can use the localization system, whether they use a VCS or manually upload their files - I'm betting you downloaded your alpha file before the localization processor ran on it, which is something your users will not be able to do.
Hi Torhal, actually I waited for it to be in the "approved" status, because I already noticed that in the "new" and in the "Under review" status localization is not yet ready (and it is absolutely logical too).
Now, it's localized.
Maybe you can check if the "approved" status is granted a bit too early.
Very often I tag alphas to check i did not messed something in pkgmeta or forgot a keywors substitution tag open, so I download it as soon as possible and the remove it because I dont want any user having it.
Knowing for certain when Curse is done packaging would be helpful (actually, the preferred solution would imho not to show the file at all until it's ready)
Now, we only miss the fix for the multiline keyboard and we will be good to go
There's a ticket in to have it not show even for project members until everything is finished processing.
The multiline localization keys have been fixed.
Seems multiline already fixed. Without announcement unfortunately.
Actually it looks like Torhal right above you did announce that they were fixed. Testing now.
Confirmed, it's working now:
This is valid lua, now!
Thank you guys
(Now, if we only could have back the old syntax highlighter in the forum... that would be awesome)
We have a pending ticket for syntax highlighting, but no ETA on its implementation.
Also confirming the localization within the packager now works for multiline phrases.
Point of clarification: Localization is no longer a packager task, so literally any project can now use it.