Skip to content

Releases: SpontanCombust/w3stringsx

v1.3.0

11 May 14:33

Choose a tag to compare

What's Changed

NEW

  • logs now also get written into w3stringsx.log file in w3stringsx.py's directory

FIXES

  • fixed unexpected error when processing decoded .csv file

Full Changelog: v1.2.1...v1.3.0

v1.2.1

13 Nov 22:57

Choose a tag to compare

What's Changed

FIXES

  • Fix a bug that prevented w3strings.exe from being used if it was placed in a folder that contained spaces in its path.

Full Changelog: v1.2.0...v1.2.1

v1.2.0

25 Oct 18:44
fe16473

Choose a tag to compare

What's Changed

NEW

  • support for nonLocalized and nonLocalizedExceptFirst tags in menu XML parsing - nodes with these tags will not be parsed for displayNames
  • ability to parse definition XMLs for localisation keys (files that get packed into .bundle archives)
  • ability to recursively scan entire directories for .ws and .xml files to parse for localisation keys
  • merging parsed localisation keys into existing .csv file instead of overwriting it
  • --warn option to set which level of logs can be printed during the script execution (by default every message is printed)

QoL

  • the script now automatically prevents ID collisions during abbreviated entry completion
  • ";idspace" comment at the beginning of CSV is no longer needed if there is at least one complete entry with valid mod ID
  • encoder and scratch folders are checked and used only in .csv and .w3strings contexts

FIXES

  • fixed arabic language identifier being misspelled as "an" instead of "ar"

Full Changelog: v1.1.0...v1.2.0

v1.1.0

20 Oct 19:14
4b10ede

Choose a tag to compare

What's Changed

NEW

  • XML parsing for displayName attributes
  • WitcherScript parsing for localisation strings; it can be done on an entire "scripts" directory
  • -s or --search option used to filter strings during the search in XML and WS files

CHANGED

  • output option can now accept a path to a specific file instead of just directory, depending on the context
  • different default names for decoded file

FIXES & QoL

  • ability to guess file encoding and thus properly read its contents if it's not regular UTF-8
  • remarks in CLI's help section
  • decoded CSV file automatically has its EOL sequences changed from LF (Unix EOL) to CRLF (Windows EOL)

Full Changelog: v1.0.1...v1.1.0

v1.0.1

18 Oct 20:27
1e15ccf

Choose a tag to compare

What's Changed

  • fixed a bug that caused files which paths had spaces to be unable to get encoded/decoded in #1

Full Changelog: v1.0.0...v1.0.1

v1.0.0

15 Oct 21:54

Choose a tag to compare

Initial release