Translations for decodeJwt function

[baltpeter]

In preparation for: tweaselORG/TrackHAR#81

This can be merged before the changes in TrackHAR are released.

[zner0L]

Suggested change

	"one": "Decode {{ .input }} as a JSON Web Token (JWT).",
	"other": "Decode every element in {{ .mapInput }} as a JSON Web Token (JWT)."
	"one": "Decode {{ .input }} from a JSON Web Token (JWT).",
	"other": "Decode every element in {{ .mapInput }} from a JSON Web Token (JWT)."

I am not sure which preposition fits, but ‘as’ feels wrong.

[baltpeter]

Um, to me "as" sounds fine. "from" is definitely wrong—{{ .input }} is a JWT.

[zner0L]

But this is what "from" canonically is supposed to mean, see e.g. https://www.urldecoder.org/

[baltpeter]

Setting aside that I wouldn't accept a random website as "canonical" (:P), you decode the output (unencoded message) from [an encoding], not the input (encoded message) as in your suggested phrasing.

Unlike our sentence, your canonical source doesn't have a subject in any sentence where it uses "decode from".

[baltpeter]

But in any case, this discussion is not specific to JWT. We are using "as" in all the other decode function translations as well.

[zner0L]

I think maybe we should remove the prepostions altogether.

[baltpeter]

Huh, what would that look like? But I genuinely don't see the issue you have with "as".