I was expecting to have to go through and fix stuff, but you've made some awesome fixes there. Good job.Souen- wrote:
Filled in most of the Japanese blanks, and fixed any mistakes that caught my eyes.
I don't know if it was always 99%, but it is right now.
forum
osu! Community Localisation Project
posted
Total Posts
609
Topic Starter
Translate Chinese FAQ to 97.83%. the only 6 cells i really dont know how to translate TAT
Thanks!peppy wrote:
I was expecting to have to go through and fix stuff, but you've made some awesome fixes there. Good job.
I was translating some Japanese FAQs and noticed... some of these FAQs would only make sense in English, in example, !alot command. Keeping completion in percentage may not be a good idea.
Topic Starter
Added bancho status messages to localisable strings.
Spanish is again at 100%!
Korean is again 100%.
when you apply Korean Localization?
+ please add IRC localization.
when you apply Korean Localization?
+ please add IRC localization.
Finally got Indonesian at 100% (had been doing this together with Winshley, Rei Hakurei, and probably a few others~)
Some strings could still use better translation, but for now it should be fine/understandable enough imo (might look for some other capable and interested translators later to help with wordings and such)
Some strings could still use better translation, but for now it should be fine/understandable enough imo (might look for some other capable and interested translators later to help with wordings and such)
Norwegian is now at 100% because I have nothing better to do.
I'm a bit iffy at some of the strings, but all of them should be decently understandable at this point. Anyone capable of writing a decent translation should probably take a look, or at least tell me if there's anything stupid left.
I'm a bit iffy at some of the strings, but all of them should be decently understandable at this point. Anyone capable of writing a decent translation should probably take a look, or at least tell me if there's anything stupid left.
Indonesian, Filipino, Portuguese and Arabic: please see the remark I wrote in country-maps @ !faq commands.
By the way, I just noticed that some new entries have recently been added in the faq commands, so you might check them out
By the way, I just noticed that some new entries have recently been added in the faq commands, so you might check them out
Updated Japanese, says 100% but there's one row that's not translated.
I'll leave that to somebody that's familiar with osu!mania.
I'll leave that to somebody that's familiar with osu!mania.
Topic Starter
Added candidates for score submission, management, replays and associated errors/messaging.
Topic Starter
MenuTip_29 added.
I added !faq grammar back, it was deleted for some unknown reason.
corrected some spelling mistakes for the german FAQ translation.
Updated Croatian translations, it should be done 100% in the next 48 hours.
Topic Starter
Added new localisable strings for spectator and chat.
I've posted a few questions about some English entries in the google drive document... I don't mind posting them here if it is more comfortable for all of you...
Updated zh-CHS translation of new strings.
Added some it translation...
Perfected the new strings of the French localisation. Thanks to whoever did the job before me!
Little question: where is ChatEngine_AlreadyInMatch used?
Also, it would be nice to have this string available to localise: "You will no longer hear <user>" appearing after having successfully ignored somebody with /ignore.
Little question: where is ChatEngine_AlreadyInMatch used?
Also, it would be nice to have this string available to localise: "You will no longer hear <user>" appearing after having successfully ignored somebody with /ignore.
Updated polish to 100%.
Croatian is at 100%.
Updated Japanese, I left a row blank because I had no idea where it shows that message...
Topic Starter
For now, please make the lines shorter.
added a few more translations + edits here and there for chinese traditional
So this feature has been implemented in the test build:
Apparently, FunSpoiler_BackgroundDim, FunSpoiler_Storyboard, FunSpoiler_Skin and FunSpoiler_Hitsounds are now used twice: in the visual settings popup and in the options menu.
Could it be possible to have seperate strings for both of these locations? One in the singular form for the VS and the other in the plural form for the options menu. Right now, it sounds weird in some languages to have the singular form used in the options menu while all of the beatmaps are concerned by the toggles.
Apparently, FunSpoiler_BackgroundDim, FunSpoiler_Storyboard, FunSpoiler_Skin and FunSpoiler_Hitsounds are now used twice: in the visual settings popup and in the options menu.
Could it be possible to have seperate strings for both of these locations? One in the singular form for the VS and the other in the plural form for the options menu. Right now, it sounds weird in some languages to have the singular form used in the options menu while all of the beatmaps are concerned by the toggles.
Topic Starter
Added beatmap import strings.
@XPJ38 sure, done.
@XPJ38 sure, done.
Great, thanks!
Also, you forgot to use FunSpoiler_Dim_Tooltip for this string here under the Graphics tab:
Btw, I suppose that "(maximum limit: {1}%)" in FunSpoiler_Dim_Tooltip isn't useful anymore now that everybody can dim BGs at 100%?
Also, you forgot to use FunSpoiler_Dim_Tooltip for this string here under the Graphics tab:
Btw, I suppose that "(maximum limit: {1}%)" in FunSpoiler_Dim_Tooltip isn't useful anymore now that everybody can dim BGs at 100%?
Topic Starter
Will fix that later.
Translated something in italian.
tiper