Skip to Content.
Sympa Menu

edugain-discuss - Re: [eduGAIN-discuss] Sizes of inline logos in eduGAIN metadata

edugain-discuss AT lists.geant.org

Subject: An open discussion list for topics related to the eduGAIN interfederation service.

List archive

Re: [eduGAIN-discuss] Sizes of inline logos in eduGAIN metadata


Chronological Thread 
  • From: Ian Young <ian AT iay.org.uk>
  • To: Davide Vaghetti <davide.vaghetti AT garr.it>
  • Cc: Guy Halse <guy AT tenet.ac.za>, Nicholas S Roy <nroy AT internet2.edu>, Leif Johansson <leifj AT sunet.se>, edugain-discuss AT lists.geant.org
  • Subject: Re: [eduGAIN-discuss] Sizes of inline logos in eduGAIN metadata
  • Date: Mon, 16 Mar 2020 18:26:01 +0000
  • Feedback-id: 217.155.173.110



On 2020-03-16, at 15:58, Davide Vaghetti <davide.vaghetti AT garr.it> wrote:

data:image/gif;base64
data:image/ico;base64
data:image/jpeg;base64
data:image/jpg;base64
data:image/png;base64
data:image/pngl;base64
data:image/vnd.microsoft.icon;base64
data:image/x-icon;base64

Plus a comma in each case ;-)

Good to know all the cases we currently use, though.

Couldn't we just ignore those bytes or am I overlooking something?

I don't think you're really missing anything. My point was simply that if you want standardise something based on file sizes, you need to take that variation into account.

It's also slightly harder to say (and to code) "A data: URL that is more than X bytes when stripped of its prefix up to and including the 'base64,', then converted from Base64 to binary" than it is to say "Any URL that is more than X bytes." But it's obviously not very much harder (except for someone coding this up in XSLT, but I don't know how many people other than myself are that masochistic).

    -- Ian




Attachment: smime.p7s
Description: S/MIME cryptographic signature




Archive powered by MHonArc 2.6.19.

Top of Page