Jump to content

Search the Community

Showing results for tags 'i18n'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Welcome Aboard
  • Kerbal Space Program 2
    • KSP2 Dev Updates
    • KSP2 Discussion
    • KSP2 Suggestions and Development Discussion
    • Challenges & Mission Ideas
    • The KSP2 Spacecraft Exchange
    • Mission Reports
    • KSP2 Prelaunch Archive
  • Kerbal Space Program 2 Gameplay & Technical Support
    • KSP2 Gameplay Questions and Tutorials
    • KSP2 Technical Support (PC, unmodded installs)
    • KSP2 Technical Support (PC, modded installs)
  • Kerbal Space Program 2 Mods
    • KSP2 Mod Discussions
    • KSP2 Mod Releases
    • KSP2 Mod Development
  • Kerbal Space Program 1
    • KSP1 The Daily Kerbal
    • KSP1 Discussion
    • KSP1 Suggestions & Development Discussion
    • KSP1 Challenges & Mission ideas
    • KSP1 The Spacecraft Exchange
    • KSP1 Mission Reports
    • KSP1 Gameplay and Technical Support
    • KSP1 Mods
    • KSP1 Expansions
  • Community
    • Science & Spaceflight
    • Kerbal Network
    • The Lounge
    • KSP Fan Works
  • International
    • International
  • KerbalEDU
    • KerbalEDU
    • KerbalEDU Website

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Skype


Twitter


About me


Location


Interests

Found 1 result

  1. When I internationalized XT Landertrons, I crawled through the config files and internationalized everything by hand. No big deal, since there's just five parts and a handful of notification strings. I'd like to internationalize HGR, though, which has dozens of parts, so I'm a lot more interested in an automated solution. I'm envisioning a script that operates on a folder and goes through each part and pulls out the title, manufacturer, description, and tags into an en-us.cfg file. Meanwhile, each autoloc tag gets generated automatically, in a format like "#autoLOC_[short_name_or_abbr_for_mod]_[partname]_title" (and "_desc", "_mfg", and "_tags"). If nobody's made a script like this, I'll make one in Python and submit it to @taniwha's cfgnode library, but I figured I'd ask around first. (@linuxgurugamer, have you made something like this?)
×
×
  • Create New...