Re: [Suggest] NONMEM adds UTF-8 support for csv files

From: "Mark Tepeck" <[email protected]> To: "Nick Holford" <[email protected]>, [email protected] Sent: Monday, June 4, 2018 7:52:28 AM Subject: Re: [NMusers] [Suggest] NONMEM adds UTF-8 support for csv files Hi All, Unfortunately, the latest release of MS Excel 2017 (build 9330.2087 for office 365) becomes more restrictive on SYLK files, which is apparently a step-back update, but really a typical Microsoft behavior ☹ . Even you agree to continue with the warning messages, the latest Excel will end up with a blank sheet. Using #ID is a practical workaround for this situation but definitely not the most intuitive one. On the other hand, even most NONMEM users are already used to some ‘tricks’, this issue still costs unnecessary efforts and deepens the learning curve for NONMEM newbies. Personally, it is surprising to see a well-maintained software lack support for UTF-8 csv files, which are now well supported by all major csv viewers, e.g. Editpad, Notepad++, open office, MS office. If this is a small fix for NONMEM, I sincerely hope that it could become true. This feature might potentially streamline NONMEM runs without adding # , as well as make NONMEM learning more fun. Thank you, Mark On Mon, Jun 4, 2018 at 1:15 AM, Nick Holford < [ mailto:[email protected] | [email protected] ] > wrote: Hi, Excel can open files with ID as the first column header. You just have to agree to continue when Excel shows its warning messages. Personally I use #ID as the first column header which avoids the Excel warnings and also means I don’t need to specify an IGNORE character in NM-TRAN because # is the default. Best wishes, Nick -- Nick Holford, Professor Clinical Pharmacology Dept Pharmacology & Clinical Pharmacology, Bldg 503 Room 302A University of Auckland, [ https://maps.google.com/?q=85+Park+Rd&entry=gmail&source=g | 85 Park Rd ] ,Private Bag 92019,Auckland,New Zealand office:+64(9)923-6730 mobile:NZ+64(21)46 23 53 FR+33(6)62 32 46 72 email: [ mailto:[email protected] | [email protected] ] [ http://holford.fmhs.auckland.ac.nz/ | http://holford.fmhs.auckland.ac.nz/ ] [ http://orcid.org/0000-0002-4031-2514 | http://orcid.org/0000-0002-4031-2514 ] Read the question, answer the question, attempt all questions From: [ mailto:[email protected] | [email protected] ] < [ mailto:[email protected] | [email protected] ] > On Behalf Of HUI, Ka Ho Sent: Monday, June 4, 2018 4:48 AM To: Mark Tepeck < [ mailto:[email protected] | [email protected] ] >; [ mailto:[email protected] | [email protected] ] Subject: [FORGED] [NMusers] 回覆 : [NMusers] [Suggest] NONMEM adds UTF-8 support for csv files Dear Mark Does it work if you don't put "ID" as the first column? Back to the days when I frequently used Excel, this had been the solution for me. Matthew ------ 原有訊息 ------ 寄件者： Mark Tepeck 日期 : 2018 年 6 月 4 日週一 10:41 收件者： [ mailto:[email protected] | [email protected] ] ; 副本： 主旨： [NMusers] [Suggest] NONMEM adds UTF-8 support for csv files Hi NONMEM Users, As a PK scientist, I often manipulate csv files with Microsoft Excel, R, and NONMEM. As some of you may have seen, if the first record in a csv file is a string “ID”, Microsoft Excel would mistake it as an SYLK file which cannot be opened normally by Excel. One workaround is to use any strings other than ID, e.g. id, '‘ID’. However, this may cause new problems in some scenarios. Another potential solution is to use the R function readr::write_excel_csv ('dataframe.csv') to output a csv file with UTF-8 Byte order mark. Unfortunately, this csv file turned out to become unreadable for NONMEM although Excel likes it. Since waiting for bug fixing of Excel by Microsoft is not optimistic, I would truly appreciate it if NONMEM can add UTF-8 support. Thank you, Mark Tepeck