fg-extract-translatable-strings: allow translatable strings to be defined at top-level

Florent Rougonrequested to merge
frougon/flightgear-fgmeta:feature/fg-extract-translatable-strings-extraction-from-top-level-processing-instructions into next

This commit allows one to have XML files scanned by fg-extract-translatable-strings start for instance like this:

<?xml version="1.0"?>

<?FlightGear-tr context="dialog-view"?>
<?FlightGear-tr id="other-views-heading-label" text="Other Views"?>
<?FlightGear-tr id="aircraft-specific-views-heading-label"
                text='"%s" Specific Views'
                comment="%s = name of the selected aircraft"?>
<?FlightGear-tr id="unnamed-view-number-n" text="unnamed view %d"
                comment="%d = view number"?>

Defining translatable strings this way (for automatic extraction) makes sense when they are used in Nasal code embedded in the XML file (the above example is for the View Options dialog).

Merge request reports