[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #64331] unicode2native demands codepage input
From: |
Qianqian Fang |
Subject: |
[Octave-bug-tracker] [bug #64331] unicode2native demands codepage input on Windows |
Date: |
Wed, 21 Jun 2023 12:14:03 -0400 (EDT) |
URL:
<https://savannah.gnu.org/bugs/?64331>
Summary: unicode2native demands codepage input on Windows
Group: GNU Octave
Submitter: fangq
Submitted: Wed 21 Jun 2023 04:14:01 PM UTC
Category: Octave Function
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Regression
Status: None
Assigned to: None
Originator Name: Qianqian Fang
Originator Email:
Open/Closed: Open
Release: 8.2.0 8.X Series Bug Fix Release
Discussion Lock: Any
Operating System: Microsoft Windows
Fixed Release: None
Planned Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Wed 21 Jun 2023 04:14:01 PM UTC By: Qianqian Fang <fangq>
I have 3 versions of octave installed on a windows machine for testing. For
octave 5.2, the following command returned no error
octave:1> unicode2native('test')
ans =
116 101 115 116
however, the same command failed on 7.3 and 8.2, complaining the optional
parameter codepage is missing.
octave:1> unicode2native('test')
error: unicode2native: CODEPAGE must be a string
error: called from
unicode2native at line 63 column 5
from the latest documentation, codepage input is optional - same as matlab's
counterpart
https://docs.octave.org/v8.2.0/String-encoding.html
I consider this as a regression, and would be appreciated if this can be fixed
- as it now breaks my code working for both matlab and octave.
by the way, it appears that a previously reported bug #60480
(https://savannah.gnu.org/bugs/?60480) has been fixed at least based on my
test (see screenshot)
_______________________________________________________
File Attachments:
-------------------------------------------------------
Date: Wed 21 Jun 2023 04:14:01 PM UTC Name: octave_unicode2native.png Size:
56KiB By: fangq
<http://savannah.gnu.org/bugs/download.php?file_id=54852>
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?64331>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #64331] unicode2native demands codepage input on Windows,
Qianqian Fang <=
- [Octave-bug-tracker] [bug #64331] unicode2native demands codepage input on Windows, Dmitri A. Sergatskov, 2023/06/21
- [Octave-bug-tracker] [bug #64331] unicode2native demands codepage input on Windows, Qianqian Fang, 2023/06/21
- [Octave-bug-tracker] [bug #64331] unicode2native demands codepage input on Windows, Dmitri A. Sergatskov, 2023/06/21
- [Octave-bug-tracker] [bug #64331] unicode2native demands codepage input on Windows, Markus Mützel, 2023/06/23
- [Octave-bug-tracker] [bug #64331] unicode2native demands codepage input on Windows, Dmitri A. Sergatskov, 2023/06/23
- [Octave-bug-tracker] [bug #64331] unicode2native demands codepage input on Windows, Markus Mützel, 2023/06/23
- [Octave-bug-tracker] [bug #64331] unicode2native demands codepage input on Windows, Markus Mützel, 2023/06/23
- [Octave-bug-tracker] [bug #64331] unicode2native demands codepage input on Windows, Markus Mützel, 2023/06/23
- [Octave-bug-tracker] [bug #64331] unicode2native demands codepage input on Windows, Dmitri A. Sergatskov, 2023/06/23
- [Octave-bug-tracker] [bug #64331] unicode2native demands codepage input on Windows, Markus Mützel, 2023/06/26