Difference between revisions of "User talk:Nonolemage"

From Team Fortress Wiki
Jump to: navigation, search
m (A few points of interest.)
m (A few points of interest.: Brackets > Braces)
Line 37: Line 37:
 
* 1. You have not added yourself to the [[Team_Fortress_Wiki:Translation_progress/fr|French translator census]] {{lang icon|fr}} yet. If you fancy yourself as a French contributor, I encourage you to add yourself to the list if you plan on staying for a long time.
 
* 1. You have not added yourself to the [[Team_Fortress_Wiki:Translation_progress/fr|French translator census]] {{lang icon|fr}} yet. If you fancy yourself as a French contributor, I encourage you to add yourself to the list if you plan on staying for a long time.
 
* 2. Make sure to [[Help:Language_translation|read translation guidelines]] {{lang icon|en}} to make sure you understand how to best contribute. I am here if you need any assistance, and there are also ways to reach me.
 
* 2. Make sure to [[Help:Language_translation|read translation guidelines]] {{lang icon|en}} to make sure you understand how to best contribute. I am here if you need any assistance, and there are also ways to reach me.
* 3. Despite what your current info boxes boast, you make quite a bit of grammar mistakes in both English and French. I suggest double-checking or even triple-checking your sentences. You can also make use of your browser's built-in corrector to catch silly grammar mistakes before others find them. Such mistakes shouldn't happen more than once after you've corrected them. I am sure you can find ways to better translate in the future; for now, if you feel like your submissions require correction, it is a good idea to add a {{code|correction}} tag between double brackets, so I can do the correction for you. It's not ideal for me to have to manually check all pages you make.
+
* 3. Despite what your current info boxes boast, you make quite a bit of grammar mistakes in both English and French. I suggest double-checking or even triple-checking your sentences. You can also make use of your browser's built-in corrector to catch silly grammar mistakes before others find them. Such mistakes shouldn't happen more than once after you've corrected them. I am sure you can find ways to better translate in the future; for now, if you feel like your submissions require correction, it is a good idea to add a {{code|correction}} tag between double braces, so I can do the correction for you. It's not ideal for me to have to manually check all pages you make.
 
* 4. You've removed tags such as {{code|update trans}} while citing that no more translation was required; however, this type of tag has not much to do with translating, but it points out that the marked page needs an update. Such an update can range from a few words to entire sections. To do so, you must compare the French page with the English page and add the missing bits to the French page, then translate them. You can do so visually or by using text-comparing tools like [https://winmerge.org/ WinMerge] {{lang icon|en}}. If [[User:BrazilianNut|BrazilianNut]] finds and marks a page, it usually means an update is actually needed. Trust me, he knows what he's doing; he would have, in fact, already seen this message. And while you removed these tags, you also left a blank space on each page, some of which I did not fix. BrazilianNut will probably have to place those tags again in the future, which is unnecessary added work.
 
* 4. You've removed tags such as {{code|update trans}} while citing that no more translation was required; however, this type of tag has not much to do with translating, but it points out that the marked page needs an update. Such an update can range from a few words to entire sections. To do so, you must compare the French page with the English page and add the missing bits to the French page, then translate them. You can do so visually or by using text-comparing tools like [https://winmerge.org/ WinMerge] {{lang icon|en}}. If [[User:BrazilianNut|BrazilianNut]] finds and marks a page, it usually means an update is actually needed. Trust me, he knows what he's doing; he would have, in fact, already seen this message. And while you removed these tags, you also left a blank space on each page, some of which I did not fix. BrazilianNut will probably have to place those tags again in the future, which is unnecessary added work.
* 5. Items such as the Beer Stein cannot be translated into something like Chope de bière as no such string can be found in the French localization file in your TF2 copy. An easy way to find out an item's translated name is to use {{code|item name}} or {{code|item link}} between brackets; in this instance, it makes {{item link|Beer Stein}}.
+
* 5. Items such as the Beer Stein cannot be translated into something like Chope de bière as no such string can be found in the French localization file in your TF2 copy. An easy way to find out an item's translated name is to use {{code|item name}} or {{code|item link}} between braces; in this instance, it makes {{item link|Beer Stein}}.
* 6. An update link should use {{code|update link}} between brackets; and not /fr, so [[Jungle_Inferno_Update]] {{lang icon|en}} does not become [[Jungle_Inferno_Update/fr]] {{lang icon|fr}} but {{update link|Jungle_Inferno_Update}} {{lang icon|en}} (translates itself on lang pages).
+
* 6. An update link should use {{code|update link}} between braces; and not /fr, so [[Jungle_Inferno_Update]] {{lang icon|en}} does not become [[Jungle_Inferno_Update/fr]] {{lang icon|fr}} but {{update link|Jungle_Inferno_Update}} {{lang icon|en}} (translates itself on lang pages).
 
* 7. There exist words that I would dub as untranslatable; such words would include Hammer editor terms, which is the software that TF2 mappers use. Trigger, for example, does not become déclencheur but stays as trigger; the same goes for clipping, brush, nodraw, etc.<br><span style="background:#393939;padding:2px 12px;font-family: TF2 Build;font-size: 1em;border-radius: 10px 10px 10px 10px;">[[User:Luno|Luno]] <span style="color:#FC0;letter-spacing:-2px">🪐🌕</span> [[User talk:Luno|<span style="color:#fff">Talk</span>]] <span style="color:#559655;letter-spacing:-2px">/</span> [[Special:Contributions/Luno|<span style="color:#fff">Contributions</span>]] <span style="color:#538AC5;letter-spacing:-2px">/</span> [[Team_Fortress_Wiki:Translation_progress/fr|<span style="color:#4d748b">T</span><span style="color:#fff">ea</span><span style="color:#ab4848">m</span>]]</span> 19:14, 25 January 2024 (UTC)
 
* 7. There exist words that I would dub as untranslatable; such words would include Hammer editor terms, which is the software that TF2 mappers use. Trigger, for example, does not become déclencheur but stays as trigger; the same goes for clipping, brush, nodraw, etc.<br><span style="background:#393939;padding:2px 12px;font-family: TF2 Build;font-size: 1em;border-radius: 10px 10px 10px 10px;">[[User:Luno|Luno]] <span style="color:#FC0;letter-spacing:-2px">🪐🌕</span> [[User talk:Luno|<span style="color:#fff">Talk</span>]] <span style="color:#559655;letter-spacing:-2px">/</span> [[Special:Contributions/Luno|<span style="color:#fff">Contributions</span>]] <span style="color:#538AC5;letter-spacing:-2px">/</span> [[Team_Fortress_Wiki:Translation_progress/fr|<span style="color:#4d748b">T</span><span style="color:#fff">ea</span><span style="color:#ab4848">m</span>]]</span> 19:14, 25 January 2024 (UTC)
  
 
:Something to note, although this is more a suggestion than something you should do. If something like Beer Stein doesn't have a correction, you can put a translation of it in brackets after it. I've done this on Dutch translations where the cosmetic description specifies an English word written on it, i.e. "[...] with "Football" (English for voetbal) [...]".<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 19:20, 25 January 2024 (UTC)
 
:Something to note, although this is more a suggestion than something you should do. If something like Beer Stein doesn't have a correction, you can put a translation of it in brackets after it. I've done this on Dutch translations where the cosmetic description specifies an English word written on it, i.e. "[...] with "Football" (English for voetbal) [...]".<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 19:20, 25 January 2024 (UTC)

Revision as of 19:34, 25 January 2024

Fell free to ask some question or say something ! (Idk why but if you whant, you can)

Slimycheivment Unlocked

Slimychievement Date Notes
Tf soldier duty bound.png

The Mann of Honor
Do you like Slimy's edits? No? Then you will NOT earn this Slimychievement!

January 10th, 2024 Good choice, mate

Good one lad!


Slimyboi500 (talk) User Slimyboi500 Profile.jpg 16:44, 10 January 2024 (UTC)

Slimychievement Date Notes
Tf demoman operation high dive.png

I Know Everything!
Complete Slimy's Ultamite TF2 Quiz.

January 12th, 2024 Quiz complete!

Slimyboi500 (talk) User Slimyboi500 Profile.jpg 17:26, 12 January 2024 (UTC)

A few points of interest.

Salutations, and I would like to personally welcome you to the wiki. Before you continue, I would like to raise a few points with you.

  • 1. You have not added yourself to the French translator census (français) yet. If you fancy yourself as a French contributor, I encourage you to add yourself to the list if you plan on staying for a long time.
  • 2. Make sure to read translation guidelines (English) to make sure you understand how to best contribute. I am here if you need any assistance, and there are also ways to reach me.
  • 3. Despite what your current info boxes boast, you make quite a bit of grammar mistakes in both English and French. I suggest double-checking or even triple-checking your sentences. You can also make use of your browser's built-in corrector to catch silly grammar mistakes before others find them. Such mistakes shouldn't happen more than once after you've corrected them. I am sure you can find ways to better translate in the future; for now, if you feel like your submissions require correction, it is a good idea to add a correction tag between double braces, so I can do the correction for you. It's not ideal for me to have to manually check all pages you make.
  • 4. You've removed tags such as update trans while citing that no more translation was required; however, this type of tag has not much to do with translating, but it points out that the marked page needs an update. Such an update can range from a few words to entire sections. To do so, you must compare the French page with the English page and add the missing bits to the French page, then translate them. You can do so visually or by using text-comparing tools like WinMerge (English). If BrazilianNut finds and marks a page, it usually means an update is actually needed. Trust me, he knows what he's doing; he would have, in fact, already seen this message. And while you removed these tags, you also left a blank space on each page, some of which I did not fix. BrazilianNut will probably have to place those tags again in the future, which is unnecessary added work.
  • 5. Items such as the Beer Stein cannot be translated into something like Chope de bière as no such string can be found in the French localization file in your TF2 copy. An easy way to find out an item's translated name is to use item name or item link between braces; in this instance, it makes Beer Stein.
  • 6. An update link should use update link between braces; and not /fr, so Jungle_Inferno_Update (English) does not become Jungle_Inferno_Update/fr (français) but Jungle Inferno Update (English) (translates itself on lang pages).
  • 7. There exist words that I would dub as untranslatable; such words would include Hammer editor terms, which is the software that TF2 mappers use. Trigger, for example, does not become déclencheur but stays as trigger; the same goes for clipping, brush, nodraw, etc.
    Luno 🪐🌕 Talk / Contributions / Team 19:14, 25 January 2024 (UTC)
Something to note, although this is more a suggestion than something you should do. If something like Beer Stein doesn't have a correction, you can put a translation of it in brackets after it. I've done this on Dutch translations where the cosmetic description specifies an English word written on it, i.e. "[...] with "Football" (English for voetbal) [...]".
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 19:20, 25 January 2024 (UTC)