Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 8 October 2019 at 1:00 Eastern

[Henrik Levkowetz <[e-mail]>]

Hi Alissa,

On 2019-10-08 16:11, Alissa Cooper wrote:
> Hi Robert,
> 
>> On Oct 4, 2019, at 11:37 AM, Robert Sparks <[e-mail]> wrote:
>> 
>> Some notes for the call.
>> 
>> On 10/3/19 1:09 PM, Russ Housley wrote:
>>> Tools Call Agenda -- 8 October 2019 at 1:00 Eastern
>>> 
>>> 
>>> JOIN WEBEX MEETING
>>> https://ietf.webex.com/ietf/j.php?MTID=m440dd848726339c03e605b9956e38bac
>>> Meeting number (access code): 640 103 570
>>> Meeting password: tools
>>> 
>>> JOIN BY PHONE
>>> 1-877-668-4493 Call-in toll free number (US/Canada)
>>> 1-650-479-3208 Call-in toll number (US/Canada)
>>> Meeting number (access code): 640 103 570
>>> Meeting password: tools
>>> 
>>> 
>>> 1. Datatracker Projects
>>>    - Expected Datatracker Releases -- Robert and Henrik
>>>      -- https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/PLAN
>> 
>> The priorities in the plan have been tuned. Please look and see that they still meet expectations.
> 
> The 5th item down says:
> 
> "Review and change the draft submission and handling code to deal
> with UTF-8 instead of ascii before upload of utf-8 drafts should be
> permitted.”
> 
> How is this working now given that we started allowing utf-8 drafts
> months ago?

The status has been changing gradually over the last few months.  The
first step was to change idnits to not issue errors for non-ASCII contents,
only warnings.  The next step was when we started accepting and converting
V3 XML uploads, which provides an improved ability to use non-ASCII.

However, all parts of the code is still not fully able to deal with non-ASCII:
If V3 XML is not used for upload, but just a text-format draft is submitted,
the code that extracts author data from text has problems if it's given
non-ASCII author names.  This will not change with the transition to Python 3;
we will either have to go back and refine the complex code that tries to
figure out author names and addresses from text-only uploads, or (less work
and better results) change the approach to requiring XML in order to support
non-ASCII author names.

The parts of the item you point at which refers to open() in general has
been accomplished with the rewrite that gave Python3 compatibility.


Regards,

	Henrik