Tirette Posted June 15 Posted June 15 (edited) Not sure if it could induce a bug or not, but while scripting a little tool around dtc files, I found out that threats name and hint encoding in those may vary between threats types or between F-16 and F-18 dtc files. For example, SAM Hawk MPQ-50 is encoded as "SAM Hawk – MPQ-55" in the F-18 dtc file and as "SAM Hawk - MPQ-55". The difference lies in the dash between Hawk and MPQ: one uses the \u2013 encoded value whereas the other uses \u002d. Don't know if it is intended or not or if it can even induce a bug but i prefer to inform about this. Edited June 15 by Tirette Corrected formulation 1
Recommended Posts