RE: [Suggest] NONMEM adds UTF-8 support for csv files
Mark:
NONMEM does not use or interpret extended UTF-8 code, but perhaps you mean that
NONMEM could filter out bytes>127 when reading in data files that are UTF-8
encoded, and process only bytes <=127. This can certainly be done, and I can
add it to the list of improvements for the next release.
Robert J. Bauer, Ph.D.
Senior Director
Pharmacometrics R&D
ICON Early Phase
820 W. Diamond Avenue
Suite 100
Gaithersburg, MD 20878
Office: (215) 616-6428
Mobile: (925) 286-0769
[email protected]<mailto:[email protected]>
http://www.iconplc.com/
Quoted reply history
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Mark Tepeck
Sent: Tuesday, June 05, 2018 2:56 PM
To: [email protected]<mailto:[email protected]>
Cc: Sebastien Bihorel; STANDING, Joseph (GREAT ORMOND STREET HOSPITAL FOR
CHILDREN NHS FOUNDATION TRUST)
Subject: Re: [NMusers] [Suggest] NONMEM adds UTF-8 support for csv files
Hi Joe and Sebastien,
Thank you for your feedback. Microsoft software is surely not my favorite
platform; However, I have to stick with MS due to the policy for the
organization computer I use.
I agree with Sebastien that there are some easy workarounds. It is indeed easy
on an individual basis, but it can be substantial efforts if accumulated for
all NONMEM users. NONMEM has more than a decade history; why couldn’t it be
made more robust, versatile and user-friendly?
Even if the new feature requested doesn’t benefit every end-user immediately,
it might be useful one day. UFT-8 BOM csv files are widely supported by csv
viewers, which speaks for their value in some scenarios. Why couldn’t it be
supported by NONMEM as well? The most successful software are typically those
constantly evolving and adapting to meet users rather than those ignoring users
feedback and calling them to make an adaption.
Best,
Mark