Translations welcome about edmarketconnector HOT 94 OPEN

Ah, yes, I'm using the actual translations that the game is using for consistency with it. I believe that historically this project has chosen to go with the in-game translation as opposed to a 'more correct' one.

So, even if they are/seem wrong, what I'm proposing to use is still going to be clear enough that an EDMC user will know which suit is being referred to, yes ?

from edmarketconnector.

Hey, i'd just like to make a note here about Polish translation:
The line Error: Can't connect to Inara should either be translated as
Błąd: Nie można połączyć się z serwisem Inara
or
Błąd: Nie można podłączyć się do serwisu Inara
to be correct with polish phrasal rules. połączyć (connect) goes with z (with) while podłączyć (connect) goes with do (to)

from edmarketconnector.

Could you add Korean (Korea) (South, if specification is needed; North is very unlikely to even come across this)? Translation might take quite some time, but I think I can do it.

Edit: 한국어 (Korean) might be a better language name

The only option was plain 'Korean', now added to the translatable list. Be sure to read https://github.com/EDCD/EDMarketConnector/wiki/Translations for our guidelines.

from edmarketconnector.

There are some new translations related to the new Privacy options in 5.1.3. I neglected to upload the changed template before the release, but at least now translators can get us caught up in time for the next release.

from edmarketconnector.

Italian done

from edmarketconnector.

Italian done

Thanks. Added your changes in cafbde8.

Still welcome for more translations - particularly Spanish and Russian.

from edmarketconnector.

I could help on the Spanish one, but I don't play on Spanish client because I like to play in English :P

from edmarketconnector.

I can translate to Latvian, and get some of my friends to do it in Russian maybe. ;)

from edmarketconnector.

Please do join the OneSky project if you would like to make a translation. There are currently 147 phrases, but about half of those are just the Federation/Empire/Combat/etc ranks.

from edmarketconnector.

Could you add the languages you want to be translated, or is it done by me? I dont see an a option to add Latvian or Russian.

from edmarketconnector.

I've added Latvian, Russian and Spanish.
I'll fill in the Russian ranks with info from the Russian Elite wiki.

Do you not see a "Manage Languages" option in the left-hand bar? (Sorry, this is the first time I'm using OneSky).

from edmarketconnector.

No im not seeing them, I assume that`s because i'm not a participant in that project, but then again, i dont see a option to participate in it.

from edmarketconnector.

I've just logged in under another account, and I see what you mean.
Anyway I've added Latvian and Russian so you should now be able to click on them and start editing.

from edmarketconnector.

Hey, I've updated Russian translation, except a few OS X specific strings (no Macs around to check for official translations).

from edmarketconnector.

I've updated Russian translation, except a few OS X specific strings (no Macs around to check for "official" translations).

Thanks. Given that on OSX hotkey/shortcuts are described as Сочетание клавиш, can you translate the remaining two?

from edmarketconnector.

I just did that, should be close enough.

from edmarketconnector.

Thanks. Added Russian in 82b1702.

from edmarketconnector.

Would you like a Dutch (NL/Nederlands) translation? Maybe I can help?

from edmarketconnector.

I've added Dutch. Go for it.
Probably best (and easiest) to leave the Federal, Empire, Combat, etc ranks in English.

from edmarketconnector.

I've completed the Dutch translation - I've left all the ranks alone since there is no official Dutch translation of E:D out. I did, however translate the 3 designations of the ranks since I noticed that the other languages had translations for those as well... (e.g. 'Trade' => 'Handels rang', 'Combat' => 'Gevechts rang').... However, I'm not too sure of these and you might want to change those back to their English counterparts....

Best of luck and thanks for the great app!

Bas - CMDR CoolBreeze

from edmarketconnector.

Great, thanks. Will commit after Christmas.

from edmarketconnector.

Just completed Latvian translation and also like QNimbus left rankings untranslated

from edmarketconnector.

Thanks. I'll also include Latvian in the next release.

from edmarketconnector.

Added Dutch in 4d0ba5e.
Added Latvian in 1fa4ae2.

from edmarketconnector.

Dutch, Latvian and Russian included in Release 2.02.

from edmarketconnector.

I can do the Czech (CS) translation, if you want.

from edmarketconnector.

Great. Have at it.

from edmarketconnector.

Czech translation is done.

We also met with problem with translation of ranks. At the end we decided, that it doesn't looks good and it can be misleading, so all texts associated with ranks stays in English.

CMDRs CatfoodCZ, Mike Stix, DaraCZ

from edmarketconnector.

Thanks. Added Czech in fd86464.

from edmarketconnector.

Czech is included in Release 2.06.

from edmarketconnector.

I'm up for doing a Bulgarian translation :)

from edmarketconnector.

@roshavagarga Great. Bulgarian added to project.

from edmarketconnector.

Can you please add Japanese?

from edmarketconnector.

Japanese added to project.

from edmarketconnector.

Thanks. Japanese translation is done.

from edmarketconnector.

Thanks. Added Japanese in 035f6bb.

from edmarketconnector.

I am willing to translate Finnish, if you want to?

from edmarketconnector.

@FreezeFINN Added, thanks.

from edmarketconnector.

Finnish has been translated. Can you send me the strings file and anything else needed, so I can test the translation before release? Thanks!

from edmarketconnector.

@FreezeFINN Thanks, will do.
How do you want to be listed in the acknowlegements ?

from edmarketconnector.

from edmarketconnector.

Finnish added in b8dfbbc.
Serbian (Latin) added in c3e5aa5.
Pre-release available for testing here.

from edmarketconnector.

from edmarketconnector.

Hello @Marginal

After the ED added support to brazilian portuguese, our community are making many translation projects. can you add brazilian portuguese on oneskyapp?

Regards.

from edmarketconnector.

@rafaelpivatto Done, thanks.

from edmarketconnector.

Hi!Im happy to make translation into Hungarian.im already doing it whit EDDI so got some experience too

from edmarketconnector.

@hermattila Thanks. I’ve added Hungarian. Please register and have at it.
Note that almost half the phrases are combat, trade etc ranks. Up to you if you want to just leave these untranslated.

from edmarketconnector.

@Marginal Hungarian translation done!Happy to help!

from edmarketconnector.

@hermattila Hungarian added in fa76aa6, thanks.

from edmarketconnector.

Could you add one por Portuguese (Portugal)? There are slight differences vs the Brazilian Portuguese.

from edmarketconnector.

@idontcare1996 I've added Portuguese (Portugal). Have at it.

from edmarketconnector.

Portuguese ( Portugal ) translation done! Thanks!

from edmarketconnector.

Hi! I can help translate into Chinese (simplified).

from edmarketconnector.

@zhixianwu Great!! Please do.
Note that about half of the phrases are Federal, Empire, Combat, etc ranks. Feel free to either translate these or leave them untranslated as they appear in English in-game, as you prefer.

from edmarketconnector.

Translation is complete, glad I could help! :)

from edmarketconnector.

Thanks.
Portuguese (Portugal) added in 12acab2, thanks.
Chinese (Simplified) added in 9947e9a, thanks.
Both will be in the next release.

from edmarketconnector.

Just found some translation mistakes in the 3.10 release, e.g. the language name itself hasn't been translated.

Fixes to the mistakes as well as refinements to the phrases that may cause confusion have been made, ready for future releases. ;)

from edmarketconnector.

e.g. the language name itself hasn't been translated.

Oops, I should have caught that.

from edmarketconnector.

@gloowa, done. You can add me to the friends in ED, and report issues You'll find in the translations directly. It will be more noticeable for me... ;-)

from edmarketconnector.

Note that I've added some instructions about translating on the Wiki: https://github.com/EDCD/EDMarketConnector/wiki/Translations

from edmarketconnector.

There's a new phrase 'Use alternate URL method' to be translated. This refers to a new, optional, method of opening Shipyard (ship build) links that should avoid the issues with certain combinations of Windows OS and browser truncating the URL at 2083 characters.

from edmarketconnector.

NB: Don't worry about that update I just pushed to OneSky for all languages, it was just a simple substitution related to a Pull Request I'm working on :

1. We had an awful "Last updated at {HH}:{MM}:{SS}" just to then .format(HH="%H", ...).
2. So I un-screwed that, but then had to update the translation string.
3. It being simple, I did that for not only the en.template, but also all the *.strings files.
4. Rather than hand-edit on OneSky, I uploaded those versions of the files.

It's the "Last updated at %H:%M:%S" phrase for the UI. Note in the comment now about leaving the '%H:%M:%S' as-is.

from edmarketconnector.

Could you add Korean (Korea) (South, if specification is needed; North is very unlikely to even come across this)? Translation might take quite some time, but I think I can do it.

Edit: 한국어 (Korean) might be a better language name

from edmarketconnector.

There's a new phrase Shutting down... to be translated on OneSky now.

from edmarketconnector.

I've just added 4 new phrases related to the upcoming change to how we enforce only a single process (moving to journal directory locking instead of a fragile process check).

from edmarketconnector.

Guess which doofus forgot to download latest translations for 4.2.0 ? Yeah, me.

Given most users shouldn't run into the new messages any way I'll leave it for now. We expect to start 5.0.0 beta in at most a week, and iterate on it when the Odyssey alpha has started, so it can wait for that.

from edmarketconnector.

I've just uploaded an updated translation template.

1. A few new phrases that all give finer-grained reporting on Frontier Authentication issues.
2. One phrase was missing a colon : at the end, so the phrase has changed, translations will need redoing for it: Plugins Without Python 3.x Support:.
3. Deprecated the now defunct (we report the more specific Inara error) Error: Can't connect to Inara.

from edmarketconnector.

Hi, I've worked on the Inara translation for PT-BR. I'd like to help out more in the EDMC OneSky app as a reviewer. Can you grant me permission to Approve and Finalize?

from edmarketconnector.

Hi, I've worked on the Inara translation for PT-BR. I'd like to help out more in the EDMC OneSky app as a reviewer. Can you grant me permission to Approve and Finalize?

f/x: Ath learns how those bits of OneSky work

OK, done. You now have 'moderator' level for PT-BR which allows you to do that sort of thing.

from edmarketconnector.

There are four new phrases, related to application components having been disabled by the new 'killswitch' feature, awaiting translations on OneSky.

from edmarketconnector.

Translated the new phrases. Strangely enough, I did not get a notification from Onesky that new phrases needed translation. I also lost the moderator level for PT-BR.

Could you please unfinalize "String Key: E:D journal file location" #25683103 for me? I'd like to change "diario" to "jornais".

from edmarketconnector.

Translated the new phrases. Strangely enough, I did not get a notification from Onesky that new phrases needed translation. I also lost the moderator level for PT-BR.

Weird, it shows you having Moderator permissions for 'Portugese (Brazil) pt-BR' in the admin interface.

I've selected the whole EDMarketConnector group for you now if that makes any difference.

Could you please unfinalize "String Key: E:D journal file location" #25683103 for me? I'd like to change "diario" to "jornais".

Done. Thanks for the work! :)

from edmarketconnector.

Ok, I know what's going on. Last time when you set me as moderator, I lost it on Inara's translation center. Artie reinstated it (and saw the same thing as you - I had the privilege, but wasn't working). As soon as you set me up again, I checked Inara's and I lost it there as well. I just contacted OneSky support to see if they can help.

Thanks!

from edmarketconnector.

Ok, I know what's going on. Last time when you set me as moderator, I lost it on Inara's translation center. Artie reinstated it (and saw the same thing as you - I had the privilege, but wasn't working). As soon as you set me up again, I checked Inara's and I lost it there as well. I just contacted OneSky support to see if they can help.

🙄 - thanks for letting us know. Here's hoping OneSky fix that soon ....

from edmarketconnector.

I've just been working on getting the translations of Odyssey suit names for display. There's only the 'Flight Suit' that has an actual full translation in each language. The others have some word(s) for 'a suit' and then the English names, i.e. they're treated as proper nouns:

    r'English\UK': {
        'flightsuit':      'Flight Suit',
        'explorationsuit': 'Artemis Suit',
        'tacticalsuit':    'Dominator Suit',
        'utilitysuit':     'Maverick Suit',
    },
    r'German\DE': {
        'flightsuit':      'Flug-Anzug',
        'explorationsuit': 'Artemis-Anzug',
        'tacticalsuit':    'Dominator-Anzug',
        'utilitysuit':     'Maverick-Anzug',
    },
    r'French\FR': {
        'flightsuit':      'Combinaison de vol',
        'explorationsuit': 'Combinaison Artemis',
        'tacticalsuit':    'Combinaison Dominator',
        'utilitysuit':     'Combinaison Maverick',
    },
    r'Portuguese\BR': {
        'flightsuit':      'Traje voador',
        'explorationsuit': 'Traje Artemis',
        'tacticalsuit':    'Traje Dominator',
        'utilitysuit':     'Traje Maverick',
    },
    r'Russian\RU': {
        'flightsuit':      'Летный комбинезон',
        'explorationsuit': 'Комбинезон Artemis',
        'tacticalsuit':    'Комбинезон Dominator',
        'utilitysuit':     'Комбинезон Maverick',
    },
    r'Spanish\ES': {
        'flightsuit':      'Traje de vuelo',
        'explorationsuit': 'Traje Artemis',
        'tacticalsuit':    'Traje Dominator',
        'utilitysuit':     'Traje Maverick',
    },

Now, in English I chose to remove the ' Suit' off the end to make it shorter. After all this text is already on the line with the label 'Suit:' so having it on the end of the name is redundant. Here's what I've done for the other languages:

    'Flug-Anzug':             'Flug',       # DE
    'Artemis-Anzug':          'Artemis',    # DE
    'Dominator-Anzug':        'Dominator',  # DE
    'Maverick-Anzug':         'Maverick',   # DE

    'Traje de vuelo':         'de vuelo',   # ES
    'Traje Artemis':          'Artemis',    # ES
    'Traje Dominator':        'Dominator',  # ES
    'Traje Maverick':         'Maverick',   # ES

    'Combinaison de vol':     'de vol',     # FR
    'Combinaison Artemis':    'Artemis',    # FR
    'Combinaison Dominator':  'Dominator',  # FR
    'Combinaison Maverick':   'Maverick',   # FR

    'Traje voador':           'voador',     # PT-BR
    'Traje Artemis':          'Artemis',    # PT-BR
    'Traje Dominator':        'Dominator',  # PT-BR
    'Traje Maverick':         'Maverick',   # PT-BR

    'Летный комбинезон':      'Летный',     # RU
    'Комбинезон Artemis':     'Artemis',    # RU
    'Комбинезон Dominator':   'Dominator',  # RU
    'Комбинезон Maverick':    'Maverick',   # RU

any comments ? This will be in the 5.0.3 release.

from edmarketconnector.

I believe, just for the default flight suit, the Suit part should remain despite the redundancy because it makes more sense.

Suit: Flight Suit makes more sense than Suit: Flight.

The remaining suits are fine, no need to add Suit to the name.

from edmarketconnector.

I believe, just for the default flight suit, the Suit part should remain despite the redundancy because it makes more sense.

Suit: Flight Suit makes more sense than Suit: Flight.

The remaining suits are fine, no need to add Suit to the name.

For English we had this debate on Discord. 'Suit Flight Suit' just seems inordinately redundant.

"Flight"
Flight What? -eyes look left- Oh!
"Flight Suit" - got it

It's not like 'Flight' there could mean anything else. It then leaves more room, without (further) widening the UI for the chosen loadout name.

As I won't generally see them I'm willing to be convinced to keep the more verbose forms in other languages :D .

from edmarketconnector.

Yes, leaving the UI less cluttered and with more room takes precedence over that suit redundancy.

For english, french, spanish and german I believe the translations you have there make sense, but I don't think "voador" should be the translation for "Flight" in this context. It should be "de voo", since it's a suit used while flying not a suit that flies (flying suit). Fato (or Traje in PT-BR) voador means Flying Suit in the context of a suit that flies (like those suit with small jet engines).

from edmarketconnector.

Although I agree that "de voo" would fit better (and similar to the Spanish translation), the official translation in-game is "voador". Since the PT-BR translation official forum has been marked as private for some time now, there isn't even a place to complain.

from edmarketconnector.

Apologies that we didn't upload a week ago when they went into code, but there are now some new phrases to be translated. If they get done within the next 3 hours they'll make it into the next release, 5.1.0, else they'll wait until the next patch release.

from edmarketconnector.

PT-BR translation updated. I can't approve/finalize though (and OneSky hasn't fixed my permissions yet). On the other hand, I'm not sure you even need translations finalized to export them.

from edmarketconnector.

Just a few moments please ;)(ko-KR)

Edit: it's done! Tho, it might have some inaccuracies-hope users will be able to reed itt corectly

from edmarketconnector.

To be sure it's better known. Yes, we'll back away from trying to translate individual words in phrases, it's just a broken concept: #1074 (comment)

from edmarketconnector.

Translators, do any of you know there are already instances of phrases where the application uses them in more than one place and it doesn't have a single good translation ?

See #1154

from edmarketconnector.

I feared that this could be the case, but due to the very low Korean user count(or, at least those who report bugs/mistakes), I couldn't verify this. So it seems... but without any method(or list of those cases) to check it, the only way would be to fix whenever a mistake is reported.

from edmarketconnector.

I just did a new upload to OneSky. At most there will be three new phrases related to errors sending data to EDDN.

But you should now see much more useful comments on each phrase. These are now auto-generated from in-code comments we add at each use of a translated phrase.

from edmarketconnector.

But you should now see much more useful comments on each phrase. These are now auto-generated from in-code comments we add at each use of a translated phrase.

And now I've said that I've spotted that some of the script output is in error. Taking the wrong comment into account, i.e.

 51         value={
 52             'auto': _('Auto'),  # LANG: 'Auto' label for Coriolis site overr    ide selection
 53             'normal': _('Normal'),  # LANG: 'Normal' label for Coriolis site     override selection
 54             'beta': _('Beta')  # LANG: 'Beta' label for Coriolis site overri    de selection```

coriolis.py: 'Auto' label for Coriolis site override selection; coriolis.py: 'Normal' label for Coriolis site override selection; coriolis.py: Coriolis normal/beta selection - normal; In files: coriolis.py:53; coriolis.py:99; coriolis.py:115;```

That first "'Auto' label for ..." should be "'Normal label for ...", but it's picking up the comment on the previous line, not the actual code line.

from edmarketconnector.

OK, that issue should be fixed. New strings uploaded with what should be very good comments for guiding translations.

Now *IS the time to let us know of any concerns you have with the strings. The aim is to address any issues ready for whenever the 5.2.0 release happens.

from edmarketconnector.

There's a new phrase Inara only accepts Live galaxy data in the update I just uploaded to OneSky.

from edmarketconnector.

Might've noticed before, but I've practically stopped updating the translations(ko-KR) (due to low user counts and shift of focus to other games/job). Should I report it here?

from edmarketconnector.

Might've noticed before, but I've practically stopped updating the translations(ko-KR) (due to low user counts and shift of focus to other games/job). Should I report it here?

I had noticed a number of the translations lagging further and further behind. But, as we're assuming the last produced translations are correct and we don't generally re-use any translated string in a different context I don't think it does any harm to continue to include an increasingly less complete translation. To do so seems better than dropping it entirely.

Thanks for your past work!

from edmarketconnector.

There's some new phrases to be translated with the upload I just made.

NB: Also, this time I decided to choose 'Deprecate' for phrases no longer in the upload. So, shout if you see anything now missing that is actually in our https://github.com/EDCD/EDMarketConnector/tree/develop branch.

from edmarketconnector.

Also, as no-one has ever actually worked on them, I just removed the Norwegian languages.

from edmarketconnector.

And a couple more phrases being uploaded/ingested right now....

from edmarketconnector.