Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

When localizing with localz, the most recent version is always localized #141

Open
celeste-ramirez opened this issue Jul 8, 2021 · 2 comments
Open

When localizing with localz, the most recent version is always localized #141

celeste-ramirez opened this issue Jul 8, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@celeste-ramirez
Copy link

The attached image shows the log of a localization of Unreal 4.26 first, then an attempted localization of Unreal 4.24 that is skipped. Let me know if more information is needed!
Inkedlocalz localization_LI
@celeste-ramirez
Copy link
Author

celeste-ramirez commented Jul 8, 2021 •
edited
Loading

Note: This isn't the case when using the command line localz and pointing specifically to a package. I was able to localize Python 2.7.18 just fine when localizing it explicitly, and 3.9.5 is the most recent version I have a package of.

@davidlatwe davidlatwe added the bug Something isn't working label Jul 9, 2021
@mottosso
Copy link
Owner

mottosso commented Jul 9, 2021

Thanks for reporting this @celeste-ramirez, any idea of where the problem might be?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mottosso @davidlatwe @celeste-ramirez