[Octave-bug-tracker] [bug #49685] Set .m file encoding on a per-directory basis

[Andrew Janke]

Follow-up Comment #6, bug #49685 (project octave):

> But I agree that the new goal of adding a function that can set the .m file
encoding on a per-directory basis is better.

IMHO a function and PKG_ADD hooks for Octave Forge packages isn't the best
approach: encoding is a property of a file or sets of files on disk, and it'd
be better to express that declaratively with sidecar files that live next to
them in the same file hierarchy, or some internal encoding indicator that's
embedded in the files, instead of requiring procedural manipulation,
especially if that procedural manipulation is tied into `pkg` packaging
insteapd of being a property of arbitrary Octave source trees.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?49685>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/