Various articles on SCRUM methodology explicitly state that sizing should not focus on time, bur rather on the more abstract "complexity" or "effort needed" of the task.
How should a task be sized if the task is trivial to do, but requires a really long time to complete (say, half the sprint or the whole sprint)? Should it be sized 1, 2, 3, or more like 20-40-Inf?
As an example of such a task, I can give the following:
Convert the translated texts from the technical PDF documentation (10 000+ texts) in the correct translations format for Android and iOS.