Right now, I mean, it's using the locs [localized strings], what we call the loc string. So, I mean, it does, but the problem is there's various kinds of data associated with these items that are in different places. And what we haven't done is really built that out, but it does use the localized item name. But there are other kinds of fields and stuff that it could be built out. In fact, one of the bugs that we had, one of the bugs that we had when we first added it is that it was just using the loc name and not the localized name. And it would make it really confusing because some things are really close to the actual end string and some things just aren't at all. And you would search for certain stuff and it wouldn't find them. And the reason is because it was searching the loc ID, but not the localized name, but that's not the case anymore. But there are other kinds of fields that it's not searching on. And sometimes I think to make that a little bit confusing, sometimes there's different strings that are shown in different UIs. So like, for example, the shop UI might use a different string for the purchasable display from the item ports editing and stuff like that. So more to be done, but it is using the localized name.