[Octave-bug-tracker] [bug #63645] .octaverc ignored when octave spawned from cgi-script

[anonymous]

URL:
  <https://savannah.gnu.org/bugs/?63645>

                 Summary: .octaverc ignored when octave spawned from
cgi-script
                 Project: GNU Octave
               Submitter: None
               Submitted: Thu 12 Jan 2023 03:35:34 PM UTC
                Category: Other
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Other
                  Status: None
             Assigned to: None
         Originator Name: Daniel Rypl
        Originator Email: drypl@fsv.cvut.cz
             Open/Closed: Open
                 Release: 6.2.0
         Discussion Lock: Any
        Operating System: GNU/Linux
           Fixed Release: None
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Thu 12 Jan 2023 03:35:34 PM UTC By: Anonymous
After upgrade to GNU Octave 6.2.0 on Debian 5.10.140-1 the output
of octave ignored the encoding of the text strings in the source m-file. This
was resolved by __mfile_encoding__("...") command in .octaverc file no matter
whether system-wide, personal or in current working directory, but only in the
case when octave was called from terminal. When called from cgi-script of web
application (eg. from a perl script using system command), .octaverc is
ignored (again no matter whether system-wide, personal or in current working
directory). The non-ascii characters in printed text are replaced by
question-mark characters.







    _______________________________________________________

Reply to this item at:

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

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