#118311: "Major ambiguity with ${tkn_playerName} leading to many grammatical problems "
Hvad handler denne rapport om?
Hvad skete der? Vær venlig og vælg nedenunder
Hvad skete der? Vær venlig og vælg nedenunder
Vær sød at undersøge, om der allerede er sendt en besked om emnet
Hvis ja, venligst STEM for denne rapport. Rapporter med flest stemmer er dem der får PRIORITET!
# | Status | Votes | Game | Type | Title | Last update |
---|
Detaljeret beskrivelse
• Venligst kopier/indsæt fejlmeddelelsen du ser på din skærm, hvis der er en.
${tkn_playerName} may select a location to place ${tkn_mapToken}
When reading this in the traduction center, we assume that ${tkn_playerName} is a third person subject.
It seems however that this particular sentence is only used with a second person subject, ${tkn_playerName} always resumes to "you" for the sentence above.
This is very misleading as "playerName"' should be a player name.
Any text where the subject of a verb can be at the second person or at the 3rd person depending on the context should be split.
Most game have dual sentence like "${you} may...." and "${actplayer}...."
This leads to very very frequent grammatical errors in multiple languages including French.
On the other hand, in the following sentence, ${tkn_playerName} does become a third person subject
${tkn_playerName} may place Agents
This is a mess.
I can almost never tell in the traduction center if the ${tkn_playerName} is second person or 3rd person or can be both (shouldn't be both because the grammatical forms are very different in many languages and you can't reasonably make a traduction that works for both uses)
----------
Take for instance :
${tkn_playerName} must select a Concession to Tax
This has been translated to
${tkn_playerName} doit choisir une concession à taxer
This works fine when it is used for 3rd person:
HighMelting doit choisir une concession à taxer
But this is ugly and incorrect:
Vous doit choisir une concession à taxer
It should be;
Vous devez choisir une concession à taxer
And there is no solution that isn't very ugly:
${tkn_playerName} doit/devez choisir une concession à taxer
Une concession à taxer doit être choisie par ${tkn_playerName}
Trust me, both are ugly and never used .
---------------------------
Now...
We also don't want to redo all the translations....
I think the best way forward is this:
1) Whenever a sentence with ${tkn_playerName} can currently be used both for "you" AND for a third person subject, it should be split in 2 sentences in the translation center and the NEW sentence should be the one for "you" and use the unambiguous ${you}
1) Whenever ${tkn_playerName} in a sentence with can currently only be used as a second person subject, it should either be changed to ${you} or you could put "you" in the context if that is what is needed to avoid having to redo the translation from scratch
Don't hesitate to message me if need be.• Venligst forklar hvad du ønsker at gøre, hvad du gjorde og hvad der skete
see above• Hvilken browser bruger du?
Google Chrome v121
• Venligst kopier/indsæt tekst vist på engelsk i stedet for dit sprog. Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.
${tkn_playerName} may select a location to place ${tkn_mapToken}
When reading this in the traduction center, we assume that ${tkn_playerName} is a third person subject.
It seems however that this particular sentence is only used with a second person subject, ${tkn_playerName} always resumes to "you" for the sentence above.
This is very misleading as "playerName"' should be a player name.
Any text where the subject of a verb can be at the second person or at the 3rd person depending on the context should be split.
Most game have dual sentence like "${you} may...." and "${actplayer}...."
This leads to very very frequent grammatical errors in multiple languages including French.
On the other hand, in the following sentence, ${tkn_playerName} does become a third person subject
${tkn_playerName} may place Agents
This is a mess.
I can almost never tell in the traduction center if the ${tkn_playerName} is second person or 3rd person or can be both (shouldn't be both because the grammatical forms are very different in many languages and you can't reasonably make a traduction that works for both uses)
----------
Take for instance :
${tkn_playerName} must select a Concession to Tax
This has been translated to
${tkn_playerName} doit choisir une concession à taxer
This works fine when it is used for 3rd person:
HighMelting doit choisir une concession à taxer
But this is ugly and incorrect:
Vous doit choisir une concession à taxer
It should be;
Vous devez choisir une concession à taxer
And there is no solution that isn't very ugly:
${tkn_playerName} doit/devez choisir une concession à taxer
Une concession à taxer doit être choisie par ${tkn_playerName}
Trust me, both are ugly and never used .
---------------------------
Now...
We also don't want to redo all the translations....
I think the best way forward is this:
1) Whenever a sentence with ${tkn_playerName} can currently be used both for "you" AND for a third person subject, it should be split in 2 sentences in the translation center and the NEW sentence should be the one for "you" and use the unambiguous ${you}
1) Whenever ${tkn_playerName} in a sentence with can currently only be used as a second person subject, it should either be changed to ${you} or you could put "you" in the context if that is what is needed to avoid having to redo the translation from scratch
Don't hesitate to message me if need be.• er der adgang til denne tekst i oversættelsessystem? Hvis ja, er det blevet oversat inden for 24 timer?
see above• Hvilken browser bruger du?
Google Chrome v121
• Forklar venligst dit forslag præcist og sammenfattende, så det er så let som muligt at forstå, hvad du mener.
${tkn_playerName} may select a location to place ${tkn_mapToken}
When reading this in the traduction center, we assume that ${tkn_playerName} is a third person subject.
It seems however that this particular sentence is only used with a second person subject, ${tkn_playerName} always resumes to "you" for the sentence above.
This is very misleading as "playerName"' should be a player name.
Any text where the subject of a verb can be at the second person or at the 3rd person depending on the context should be split.
Most game have dual sentence like "${you} may...." and "${actplayer}...."
This leads to very very frequent grammatical errors in multiple languages including French.
On the other hand, in the following sentence, ${tkn_playerName} does become a third person subject
${tkn_playerName} may place Agents
This is a mess.
I can almost never tell in the traduction center if the ${tkn_playerName} is second person or 3rd person or can be both (shouldn't be both because the grammatical forms are very different in many languages and you can't reasonably make a traduction that works for both uses)
----------
Take for instance :
${tkn_playerName} must select a Concession to Tax
This has been translated to
${tkn_playerName} doit choisir une concession à taxer
This works fine when it is used for 3rd person:
HighMelting doit choisir une concession à taxer
But this is ugly and incorrect:
Vous doit choisir une concession à taxer
It should be;
Vous devez choisir une concession à taxer
And there is no solution that isn't very ugly:
${tkn_playerName} doit/devez choisir une concession à taxer
Une concession à taxer doit être choisie par ${tkn_playerName}
Trust me, both are ugly and never used .
---------------------------
Now...
We also don't want to redo all the translations....
I think the best way forward is this:
1) Whenever a sentence with ${tkn_playerName} can currently be used both for "you" AND for a third person subject, it should be split in 2 sentences in the translation center and the NEW sentence should be the one for "you" and use the unambiguous ${you}
1) Whenever ${tkn_playerName} in a sentence with can currently only be used as a second person subject, it should either be changed to ${you} or you could put "you" in the context if that is what is needed to avoid having to redo the translation from scratch
Don't hesitate to message me if need be.• Hvilken browser bruger du?
Google Chrome v121
• Hvad blev der vist på skærmen, da du blev blokeret (Blank skærm? Noget af spilbrugerfladen? Fejlmeddelelse?)
${tkn_playerName} may select a location to place ${tkn_mapToken}
When reading this in the traduction center, we assume that ${tkn_playerName} is a third person subject.
It seems however that this particular sentence is only used with a second person subject, ${tkn_playerName} always resumes to "you" for the sentence above.
This is very misleading as "playerName"' should be a player name.
Any text where the subject of a verb can be at the second person or at the 3rd person depending on the context should be split.
Most game have dual sentence like "${you} may...." and "${actplayer}...."
This leads to very very frequent grammatical errors in multiple languages including French.
On the other hand, in the following sentence, ${tkn_playerName} does become a third person subject
${tkn_playerName} may place Agents
This is a mess.
I can almost never tell in the traduction center if the ${tkn_playerName} is second person or 3rd person or can be both (shouldn't be both because the grammatical forms are very different in many languages and you can't reasonably make a traduction that works for both uses)
----------
Take for instance :
${tkn_playerName} must select a Concession to Tax
This has been translated to
${tkn_playerName} doit choisir une concession à taxer
This works fine when it is used for 3rd person:
HighMelting doit choisir une concession à taxer
But this is ugly and incorrect:
Vous doit choisir une concession à taxer
It should be;
Vous devez choisir une concession à taxer
And there is no solution that isn't very ugly:
${tkn_playerName} doit/devez choisir une concession à taxer
Une concession à taxer doit être choisie par ${tkn_playerName}
Trust me, both are ugly and never used .
---------------------------
Now...
We also don't want to redo all the translations....
I think the best way forward is this:
1) Whenever a sentence with ${tkn_playerName} can currently be used both for "you" AND for a third person subject, it should be split in 2 sentences in the translation center and the NEW sentence should be the one for "you" and use the unambiguous ${you}
1) Whenever ${tkn_playerName} in a sentence with can currently only be used as a second person subject, it should either be changed to ${you} or you could put "you" in the context if that is what is needed to avoid having to redo the translation from scratch
Don't hesitate to message me if need be.• Hvilken browser bruger du?
Google Chrome v121
• Hvilken del af reglerne blev ikke respekteret ved BGA-tilpasningen
${tkn_playerName} may select a location to place ${tkn_mapToken}
When reading this in the traduction center, we assume that ${tkn_playerName} is a third person subject.
It seems however that this particular sentence is only used with a second person subject, ${tkn_playerName} always resumes to "you" for the sentence above.
This is very misleading as "playerName"' should be a player name.
Any text where the subject of a verb can be at the second person or at the 3rd person depending on the context should be split.
Most game have dual sentence like "${you} may...." and "${actplayer}...."
This leads to very very frequent grammatical errors in multiple languages including French.
On the other hand, in the following sentence, ${tkn_playerName} does become a third person subject
${tkn_playerName} may place Agents
This is a mess.
I can almost never tell in the traduction center if the ${tkn_playerName} is second person or 3rd person or can be both (shouldn't be both because the grammatical forms are very different in many languages and you can't reasonably make a traduction that works for both uses)
----------
Take for instance :
${tkn_playerName} must select a Concession to Tax
This has been translated to
${tkn_playerName} doit choisir une concession à taxer
This works fine when it is used for 3rd person:
HighMelting doit choisir une concession à taxer
But this is ugly and incorrect:
Vous doit choisir une concession à taxer
It should be;
Vous devez choisir une concession à taxer
And there is no solution that isn't very ugly:
${tkn_playerName} doit/devez choisir une concession à taxer
Une concession à taxer doit être choisie par ${tkn_playerName}
Trust me, both are ugly and never used .
---------------------------
Now...
We also don't want to redo all the translations....
I think the best way forward is this:
1) Whenever a sentence with ${tkn_playerName} can currently be used both for "you" AND for a third person subject, it should be split in 2 sentences in the translation center and the NEW sentence should be the one for "you" and use the unambiguous ${you}
1) Whenever ${tkn_playerName} in a sentence with can currently only be used as a second person subject, it should either be changed to ${you} or you could put "you" in the context if that is what is needed to avoid having to redo the translation from scratch
Don't hesitate to message me if need be.• Er regel-brudddet synligt i e
see above• Hvilken browser bruger du?
Google Chrome v121
• Hvad var den spilhandling du ønskede at udføre?
${tkn_playerName} may select a location to place ${tkn_mapToken}
When reading this in the traduction center, we assume that ${tkn_playerName} is a third person subject.
It seems however that this particular sentence is only used with a second person subject, ${tkn_playerName} always resumes to "you" for the sentence above.
This is very misleading as "playerName"' should be a player name.
Any text where the subject of a verb can be at the second person or at the 3rd person depending on the context should be split.
Most game have dual sentence like "${you} may...." and "${actplayer}...."
This leads to very very frequent grammatical errors in multiple languages including French.
On the other hand, in the following sentence, ${tkn_playerName} does become a third person subject
${tkn_playerName} may place Agents
This is a mess.
I can almost never tell in the traduction center if the ${tkn_playerName} is second person or 3rd person or can be both (shouldn't be both because the grammatical forms are very different in many languages and you can't reasonably make a traduction that works for both uses)
----------
Take for instance :
${tkn_playerName} must select a Concession to Tax
This has been translated to
${tkn_playerName} doit choisir une concession à taxer
This works fine when it is used for 3rd person:
HighMelting doit choisir une concession à taxer
But this is ugly and incorrect:
Vous doit choisir une concession à taxer
It should be;
Vous devez choisir une concession à taxer
And there is no solution that isn't very ugly:
${tkn_playerName} doit/devez choisir une concession à taxer
Une concession à taxer doit être choisie par ${tkn_playerName}
Trust me, both are ugly and never used .
---------------------------
Now...
We also don't want to redo all the translations....
I think the best way forward is this:
1) Whenever a sentence with ${tkn_playerName} can currently be used both for "you" AND for a third person subject, it should be split in 2 sentences in the translation center and the NEW sentence should be the one for "you" and use the unambiguous ${you}
1) Whenever ${tkn_playerName} in a sentence with can currently only be used as a second person subject, it should either be changed to ${you} or you could put "you" in the context if that is what is needed to avoid having to redo the translation from scratch
Don't hesitate to message me if need be.• Hvad forsøgte du at gøre for at udløse denne spilhandling?
see above• Hvad skete der, da du forsøgre at gøre dette (fejlmeddelelse, meddelelsesstatusbjælke, ...)?
• Hvilken browser bruger du?
Google Chrome v121
• I hvilket stadie af spillet opstod problemet (hvad var den daværende spilinstruktion)?
${tkn_playerName} may select a location to place ${tkn_mapToken}
When reading this in the traduction center, we assume that ${tkn_playerName} is a third person subject.
It seems however that this particular sentence is only used with a second person subject, ${tkn_playerName} always resumes to "you" for the sentence above.
This is very misleading as "playerName"' should be a player name.
Any text where the subject of a verb can be at the second person or at the 3rd person depending on the context should be split.
Most game have dual sentence like "${you} may...." and "${actplayer}...."
This leads to very very frequent grammatical errors in multiple languages including French.
On the other hand, in the following sentence, ${tkn_playerName} does become a third person subject
${tkn_playerName} may place Agents
This is a mess.
I can almost never tell in the traduction center if the ${tkn_playerName} is second person or 3rd person or can be both (shouldn't be both because the grammatical forms are very different in many languages and you can't reasonably make a traduction that works for both uses)
----------
Take for instance :
${tkn_playerName} must select a Concession to Tax
This has been translated to
${tkn_playerName} doit choisir une concession à taxer
This works fine when it is used for 3rd person:
HighMelting doit choisir une concession à taxer
But this is ugly and incorrect:
Vous doit choisir une concession à taxer
It should be;
Vous devez choisir une concession à taxer
And there is no solution that isn't very ugly:
${tkn_playerName} doit/devez choisir une concession à taxer
Une concession à taxer doit être choisie par ${tkn_playerName}
Trust me, both are ugly and never used .
---------------------------
Now...
We also don't want to redo all the translations....
I think the best way forward is this:
1) Whenever a sentence with ${tkn_playerName} can currently be used both for "you" AND for a third person subject, it should be split in 2 sentences in the translation center and the NEW sentence should be the one for "you" and use the unambiguous ${you}
1) Whenever ${tkn_playerName} in a sentence with can currently only be used as a second person subject, it should either be changed to ${you} or you could put "you" in the context if that is what is needed to avoid having to redo the translation from scratch
Don't hesitate to message me if need be.• Hvad skete der, da du forsøgte at udføre denne spilhandling (fejlmeddelelse, meddelelsesstatusbjælke, ...)?
see above• Hvilken browser bruger du?
Google Chrome v121
• Venligst beskriv display problemet. Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.
${tkn_playerName} may select a location to place ${tkn_mapToken}
When reading this in the traduction center, we assume that ${tkn_playerName} is a third person subject.
It seems however that this particular sentence is only used with a second person subject, ${tkn_playerName} always resumes to "you" for the sentence above.
This is very misleading as "playerName"' should be a player name.
Any text where the subject of a verb can be at the second person or at the 3rd person depending on the context should be split.
Most game have dual sentence like "${you} may...." and "${actplayer}...."
This leads to very very frequent grammatical errors in multiple languages including French.
On the other hand, in the following sentence, ${tkn_playerName} does become a third person subject
${tkn_playerName} may place Agents
This is a mess.
I can almost never tell in the traduction center if the ${tkn_playerName} is second person or 3rd person or can be both (shouldn't be both because the grammatical forms are very different in many languages and you can't reasonably make a traduction that works for both uses)
----------
Take for instance :
${tkn_playerName} must select a Concession to Tax
This has been translated to
${tkn_playerName} doit choisir une concession à taxer
This works fine when it is used for 3rd person:
HighMelting doit choisir une concession à taxer
But this is ugly and incorrect:
Vous doit choisir une concession à taxer
It should be;
Vous devez choisir une concession à taxer
And there is no solution that isn't very ugly:
${tkn_playerName} doit/devez choisir une concession à taxer
Une concession à taxer doit être choisie par ${tkn_playerName}
Trust me, both are ugly and never used .
---------------------------
Now...
We also don't want to redo all the translations....
I think the best way forward is this:
1) Whenever a sentence with ${tkn_playerName} can currently be used both for "you" AND for a third person subject, it should be split in 2 sentences in the translation center and the NEW sentence should be the one for "you" and use the unambiguous ${you}
1) Whenever ${tkn_playerName} in a sentence with can currently only be used as a second person subject, it should either be changed to ${you} or you could put "you" in the context if that is what is needed to avoid having to redo the translation from scratch
Don't hesitate to message me if need be.• Hvilken browser bruger du?
Google Chrome v121
• Venligst kopier/indsæt tekst vist på engelsk i stedet for dit sprog. Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.
${tkn_playerName} may select a location to place ${tkn_mapToken}
When reading this in the traduction center, we assume that ${tkn_playerName} is a third person subject.
It seems however that this particular sentence is only used with a second person subject, ${tkn_playerName} always resumes to "you" for the sentence above.
This is very misleading as "playerName"' should be a player name.
Any text where the subject of a verb can be at the second person or at the 3rd person depending on the context should be split.
Most game have dual sentence like "${you} may...." and "${actplayer}...."
This leads to very very frequent grammatical errors in multiple languages including French.
On the other hand, in the following sentence, ${tkn_playerName} does become a third person subject
${tkn_playerName} may place Agents
This is a mess.
I can almost never tell in the traduction center if the ${tkn_playerName} is second person or 3rd person or can be both (shouldn't be both because the grammatical forms are very different in many languages and you can't reasonably make a traduction that works for both uses)
----------
Take for instance :
${tkn_playerName} must select a Concession to Tax
This has been translated to
${tkn_playerName} doit choisir une concession à taxer
This works fine when it is used for 3rd person:
HighMelting doit choisir une concession à taxer
But this is ugly and incorrect:
Vous doit choisir une concession à taxer
It should be;
Vous devez choisir une concession à taxer
And there is no solution that isn't very ugly:
${tkn_playerName} doit/devez choisir une concession à taxer
Une concession à taxer doit être choisie par ${tkn_playerName}
Trust me, both are ugly and never used .
---------------------------
Now...
We also don't want to redo all the translations....
I think the best way forward is this:
1) Whenever a sentence with ${tkn_playerName} can currently be used both for "you" AND for a third person subject, it should be split in 2 sentences in the translation center and the NEW sentence should be the one for "you" and use the unambiguous ${you}
1) Whenever ${tkn_playerName} in a sentence with can currently only be used as a second person subject, it should either be changed to ${you} or you could put "you" in the context if that is what is needed to avoid having to redo the translation from scratch
Don't hesitate to message me if need be.• er der adgang til denne tekst i oversættelsessystem? Hvis ja, er det blevet oversat inden for 24 timer?
see above• Hvilken browser bruger du?
Google Chrome v121
• Forklar venligst dit forslag præcist og sammenfattende, så det er så let som muligt at forstå, hvad du mener.
${tkn_playerName} may select a location to place ${tkn_mapToken}
When reading this in the traduction center, we assume that ${tkn_playerName} is a third person subject.
It seems however that this particular sentence is only used with a second person subject, ${tkn_playerName} always resumes to "you" for the sentence above.
This is very misleading as "playerName"' should be a player name.
Any text where the subject of a verb can be at the second person or at the 3rd person depending on the context should be split.
Most game have dual sentence like "${you} may...." and "${actplayer}...."
This leads to very very frequent grammatical errors in multiple languages including French.
On the other hand, in the following sentence, ${tkn_playerName} does become a third person subject
${tkn_playerName} may place Agents
This is a mess.
I can almost never tell in the traduction center if the ${tkn_playerName} is second person or 3rd person or can be both (shouldn't be both because the grammatical forms are very different in many languages and you can't reasonably make a traduction that works for both uses)
----------
Take for instance :
${tkn_playerName} must select a Concession to Tax
This has been translated to
${tkn_playerName} doit choisir une concession à taxer
This works fine when it is used for 3rd person:
HighMelting doit choisir une concession à taxer
But this is ugly and incorrect:
Vous doit choisir une concession à taxer
It should be;
Vous devez choisir une concession à taxer
And there is no solution that isn't very ugly:
${tkn_playerName} doit/devez choisir une concession à taxer
Une concession à taxer doit être choisie par ${tkn_playerName}
Trust me, both are ugly and never used .
---------------------------
Now...
We also don't want to redo all the translations....
I think the best way forward is this:
1) Whenever a sentence with ${tkn_playerName} can currently be used both for "you" AND for a third person subject, it should be split in 2 sentences in the translation center and the NEW sentence should be the one for "you" and use the unambiguous ${you}
1) Whenever ${tkn_playerName} in a sentence with can currently only be used as a second person subject, it should either be changed to ${you} or you could put "you" in the context if that is what is needed to avoid having to redo the translation from scratch
Don't hesitate to message me if need be.• Hvilken browser bruger du?
Google Chrome v121
Rapporthistorik
For the "context" in the traduction center, what would help us for French (but I'm sure other languages too) is something along the line:
- is it a command from the player to the game ( in French we will use the infinitive for that "kill" -> "tuer" )
- or is it instead a command form the game to the player (in French we will use the imperative for that "kill" -> "tuez" )
- or is it a description (this will usually translate into an indicative in French "you kill" -> "vous tuez" but an infinitive can also work)
It is usually best to split sentences than can be used in such different contexts into multiple entries in the traduction center..
------------------------------------------------
Hanging texts like for instance " ( 2 remaining)" can be very delicate and should usually be avoided because:
- the literal translation is "restant" but that is most often not the best translation. If it is instead integrated in each of the sentences that uses it, it's easier to choose the best word for the context.
- "restant" is the masc form. If we don't know the related gender, we should probably write "restant(e)" or "restant·e"
- there might be languages where putting that hanging text at the end will not be normal. And care should obviously be taken so that it still work for right to left languages
Now I understand that this has downsides to: I you have many sentences that can sometimes have that hanging part and sometimes not or sometimes a different hanging part, that can be annoying...
And this can also recoup the recommendation since the hanging part is often present or not depending on whether it is used as a command from the player to the game or as a description.
------------------------------
I think it should be fine to switch sentences to use ${you}. I set it up this way initially because some of the player names (and 'you' when in the title bar) need to have a text-shadow, but I have found another way to solve that. Alternatively if that doesn't work I can change it to ${tkn_you} as a backup solution. But it will cause some retranslation / extra translations.
I cannot do anything about the context in the translation center. It's just the file name of the file where it's defined.
With the (x remaining) I see your point, but BGA actually recommends to use nested logs to limit the number of translations (though I guess with the amount of text in a game like Pax Ren I am not sure how much that matters). But I will take a look at it as this probably concerns sentences suffering from the ${you} issue as well so I might just be able to change them as a retranslation is needed anyway.
Note that some entries will have to be split like the one below as they are used both for 'you' and for third person. I don't think there are that many of them but there are some and it's a bit difficult to detect all the instances from within the game.
${tkn_playerName} must select a Concession to Tax
The entries that were used for both instances should be split automatically. I basically need to mark a string for translation and BGAs system detects if there are duplicates and only add them once. In the code this is already split so two strings '${tkn_playerName} must select a Concession to Tax' were marked for translation, while now it will be two different ones.
The (x remaining) should also be better translatable now.
Tilføj noget til denne rapport
- Et andet bord-ID / træk ID
- Løste F5 problemet?
- Skete problemet flere gange? Hver gang? Tilfældigt?
- Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.