Unicode in VOTable

[Sipőcz, Brigitta]

Hi Markus,

I've now cobbled together a function and a couple of tests that's
perhaps not ultra-robust and needs some review (attached, use
whatever license you need).  And... well, would anyone volunteer to
massage that into astropy?  I have a bit of stagefright when it comes
to their io.votable module, in particular when it's about introducing
a function we don't even need just now...

Next astropy release is in October, so if we get something in now, there is still a lot of time to test and massage it into a form that is OK to be released.
As for the PR workflow, I would recommend to open a draft PR with the code you currently have (I couldn't open/download it, I guess outlook was trying to be too clever); then it will land on Tom's and my desk and we will be able to amend it as needed along singing off the review on it.
Unless of course someone else wants to pick it up and open the PR.

Bottom line, it's still early in the development cycle, and I feel it would be beneficial to get such improvements in sooner rather than right before a release is cut. If you think October is too soon to get this all ready from the VO side, then my recommendation would stay the same, aim the PR to be ready early in a release cycle so we can go and downstream test it in pyvo/astroquery/anywhere else as much as possible.

Cheers,
 Brigitta


________________________________
From: apps <apps-bounces at ivoa.net> on behalf of Markus Demleitner via apps <apps at ivoa.net>
Sent: 16 June 2025 07:54
To: apps at ivoa.net <apps at ivoa.net>
Subject: Re: Unicode in VOTable

Dear Apps folks,

On Thu, Jun 12, 2025 at 06:46:45PM +0000, Sipőcz, Brigitta via apps wrote:
> Gregory:
>> Contributing that “unsliced UTF-8 truncation to octets” function to
>>
> Astropy’s VO tools would be most useful.
>
> Yes please.

It turns out that that's not the nice little finger exercise to
reward oneself right before going home.  Surprisingly, it's actually
a bit of code and conceptially fairly complicated.

I've now cobbled together a function and a couple of tests that's
perhaps not ultra-robust and needs some review (attached, use
whatever license you need).  And... well, would anyone volunteer to
massage that into astropy?  I have a bit of stagefright when it comes
to their io.votable module, in particular when it's about introducing
a function we don't even need just now...

Thanks,

          Markus


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/apps/attachments/20250616/d47956d2/attachment.htm>