Theme's style.css not detected when in a subdirectory

[bradyvercher]

I'm working on bundling this package as the engine for node-wp-i18n (which is used by grunt-wp-i18n), but am running into a few failing tests due to slight differences in the way they work.

WordPress supports themes that are in a subdirectory of the theme root directory, but this command doesn't detect style.css files that aren't in the theme root and doesn't include a way to specify where to find the main file with the package metadata.

There could potentially be multiple nested themes in a themes in a theme directory, which would pose a problem for automatically detecting the correct theme when running wp i18n from the theme root, but the most common use case is to use the root directory for development and config related files, with style.css and templates in a subdirectory. This structure can be found in the Make theme, Sage, and WP Rig.

Here's the issue in node-wp-i18n where support was requested and added.

[swissspidy]

Huh, I knew I saw this code before but somehow surprised WordPress still supports that.

Should be as easy as updating MakePotCommand::get_main_file_data(). Doesn't hurt to refactor that method anyway.