Add Hungarian localization #274

yuryleb · 2019-02-28T06:21:57Z

Issue

Initial Hungarian translation contributed by @kiskunk initally discussed in #271.
Thanks a lot!

Tasklist

Review
Add changelog entry
Test with osrm-frontend (?)

alexwyattdev

Some of these turned out a bit differently from what I expected after Transifex, so I had to do some updating on Transifex. Sorry for the inconvenience.

yuryleb · 2019-02-28T14:13:00Z

No problem, that's the review goal is 😉

alexwyattdev · 2019-03-01T17:32:35Z

No problem, that's the review goal is 😉

Ok, will I get a new notification if the new review is available, or I have to check back regularly? Thanks.

yuryleb · 2019-03-01T17:48:01Z

I'll add comment here and then you'll get a notification. Did you already update translation on Transifex?

alexwyattdev · 2019-03-01T18:47:07Z

I'll add comment here and then you'll get a notification. Did you already update translation on Transifex?

Yes, I did it before commenting on the review here.

yuryleb · 2019-03-01T20:01:22Z

IMHO missing whitespace after {modifier} in new name stuff:

        "merge": {
            "default": {
                "default": "Soroljon be {modifier}",
                "name": "Soroljon be {modifier}a(z) {way_name} felé",
                "destination": "Soroljon be {modifier} ehhez: {destination}"
            },

alexwyattdev · 2019-03-01T20:54:59Z

IMHO missing whitespace after {modifier} in new name stuff:

        "merge": {
            "default": {
                "default": "Soroljon be {modifier}",
                "name": "Soroljon be {modifier}a(z) {way_name} felé",
                "destination": "Soroljon be {modifier} ehhez: {destination}"
            },

Fixed it, tho it's really hard to keep track since almost every value exist 6 times.

yuryleb · 2019-03-02T13:53:18Z

Actually no, only destination was changed but name still need for whitespace:

        "merge": {
            "default": {
                "default": "Soroljon be {modifier}",
                "name": "Soroljon be {modifier}a(z) {way_name} felé",
                "destination": "Soroljon be {modifier} a(z) {destination} irányába"
            },

And there are several similar cases, I recommend to use Transifex search for translated strings with }a pattern.

alexwyattdev · 2019-03-02T14:24:40Z

I only saw one, fixed, then searched for }a and found nothing. Is it possible to remove the ultimate redundancy somehow so every string would be there only 1 times?

yuryleb · 2019-03-02T19:41:17Z

I pushed your updated translation, please review result again.

IMHO there are extra whitespaces in name and ref now 😉

        "phrase": {
            "two linked by distance": "{instruction_one} , majd {distance} múlva, {instruction_two}",
            "two linked": "{instruction_one} , majd {instruction_two}",
            "one in distance": "{distance} múlva {instruction_one}",
            "name and ref": "{name} ( {ref} )",
            "exit with number": "{exit} kijárat"
        },

alexwyattdev · 2019-03-02T19:54:50Z

Sorry, i wanted to make sure there is always whitespace, tomorrow I will check them, so to be clear there can be braces and commas after them ?

yuryleb · 2019-03-02T20:11:01Z

I suppose there should be just "name and ref": "{name} ({ref})",

yuryleb · 2019-03-02T20:15:20Z

test/fixtures/v5/other/way_name_ref_name.json

@@ -18,6 +18,7 @@
        "fi": "Käänny vasempaan tielle Way Name (Ref1)",
        "fr": "Tourner à gauche sur Way Name (Ref1)",
        "he": "פנה שמאלה לWay Name (Ref1)",
+        "hu": "Forduljon be balra a(z) Way Name ( Ref1 ) irányába",


Here is extra whitespaces sample

alexwyattdev

Changed a few lines again on Transifex.

yuryleb · 2019-03-04T20:20:56Z

languages/translations/hu.json

-                "namedistance": "Hajtson {direction} felé a(z) {way_name} , {distance} távolságig"
+                "default": "Hajtson a(z) {direction} irányába",
+                "name": "Hajtson a(z) {direction} irányába a(z) {way_name} szakaszon",
+                "namedistance": "Hajtson a(z) {direction} irányába a(z) {way_name} felé {distance}  távolságig"


Extra whitespace after {distance} IMHO

yuryleb · 2019-03-04T20:22:00Z

languages/translations/hu.json

-                    "name": "Hajtson a körforgalomba, majd hagyja el a körforgalmat a(z) {way_name} felé",
-                    "destination": "Hajtson a körforgalomba, majd hagyja el a körforgalmat a(z) {destination} irányába"
+                    "name": "Hajtson a körforgalomba, majd hagyja el a körforgalmat a(z) {way_name}  felé",
+                    "destination": "Hajtson a körforgalomba, majd hagyja el a körforgalmat a(z) {destination}  irányába"


And here after {way_name} and {destination} too

yuryleb · 2019-03-04T20:23:50Z

Next commit pushed. But now there are extra whitespaces 😞

alexwyattdev · 2019-03-04T20:31:52Z

Transifex really plays out its cards... oh well, tried to fix them all.

alexwyattdev

Fixed on transifex

yuryleb · 2019-03-06T06:21:49Z

Committed last fix. Translation looks good for me now 👍

BTW maybe you could also add translation to the frontend? It's necessary just add new hu.js into i18n folder with similar content:

module.exports = {
  name: 'English',
  key: 'en',
  'Open in Debug Map': 'Open in Debug Map',
  'Open in Mapillary': 'Open in Mapillary',
  'GPX': 'Export GPX file',
  'Open in editor': 'Open in editor',
  'Open in JOSM': 'Open in JOSM',
  'Select language': 'Select language',
  'Start - press enter to drop marker': 'Start - press enter to drop marker',
  'End - press enter to drop marker': 'End - press enter to drop marker',
  'Via point - press enter to drop marker': 'Via point - press enter to drop marker'
};

and register it in src/localization.js?

You could do this in your own new pull request or just send/type translation for me.
Then I could test your localization for osrm-text-instructions together with frontend.

alexwyattdev

Looks good, also I created a pull request for the frontend language file.

yuryleb · 2019-03-06T20:43:42Z

Translation is also checked with frontend:

So if all is ok, maybe this could be merged?

Also IMHO new version of whole package should be released already, maybe maintainers could do this finally?

/cc @1ec5

alexwyattdev · 2019-03-06T20:55:39Z

Translation is also checked with frontend:

So if all is ok, maybe this could be merged?

Also IMHO new version of whole package should be released already, maybe maintainers could do this finally?

/cc @1ec5

It looks and reads correct.

yuryleb · 2019-03-08T21:29:15Z

Maybe @danpaz could merge this PR?

1ec5 · 2019-03-19T16:58:40Z

languages/translations/hu.json

+        "modes": {
+            "ferry": {
+                "default": "Hajtson fel a kompra",
+                "name": "Hajtson fel a kompra a(z) {way_name} felé",


According to Wiktionary, it would be “a” or “az” depending on the first letter of way_name. a(z) likely won’t sound right when spoken by a text-to-speech engine. We should add a simple grammar rule that changes it to “a” or “az” based on way_name.

Yes, and @kiskunk and I agreed to try to do this in separate PR. But I could try to include this into already prepared. I just worry that PR may become too huge to be reviewed completely.

@kiskunk, would these regular expressions correctly match all the vowels and consonants that could appear at the beginning of a name?

"article": [ ["^ [aáäåâeéëiíïoóőöuúűüyÿ]", " az "], ["^ [^aáäåâeéëiíïoóőöuúűüyÿ]", " a "] ]

There would also need to be an override file similar to the French one:

osrm-text-instructions/languages/overrides/fr.js

Lines 3 to 9 in ed1a4a9

var replaces = [

[' (de )?\{destination\}', ' {destination:preposition}'], // eslint-disable-line no-useless-escape

[' (le rond-point )?\{rotary_name\}', ' {rotary_name:rotary}'], // eslint-disable-line no-useless-escape

[' fin (de )?(la route )?\{way_name\}', ' fin {way_name:preposition}'], // eslint-disable-line no-useless-escape

[' \{way_name\}', ' {way_name:article}'], // eslint-disable-line no-useless-escape

[' (à )?\{waypoint_name\}', ' {waypoint_name:arrival}'] // eslint-disable-line no-useless-escape

];

@kiskunk, would these regular expressions correctly match all the vowels and consonants that could appear at the beginning of a name?

"article": [ ["^ [aáäåâeéëiíïoóőöuúűüyÿ]", " az "], ["^ [^aáäåâeéëiíïoóőöuúűüyÿ]", " a "] ]

There would also need to be an override file similar to the French one:

osrm-text-instructions/languages/overrides/fr.js

Lines 3 to 9 in ed1a4a9

var replaces = [
[' (de )?{destination}', ' {destination:preposition}'], // eslint-disable-line no-useless-escape
[' (le rond-point )?{rotary_name}', ' {rotary_name:rotary}'], // eslint-disable-line no-useless-escape
[' fin (de )?(la route )?{way_name}', ' fin {way_name:preposition}'], // eslint-disable-line no-useless-escape
[' {way_name}', ' {way_name:article}'], // eslint-disable-line no-useless-escape
[' (à )?{waypoint_name}', ' {waypoint_name:arrival}'] // eslint-disable-line no-useless-escape
];

It would be good for most of the time, but not always, if there is any way to determine that a way_name/destination is a highway or not, it could be helpful, without that the globally accepted "a(z)" format is ok.

So it seems we need add rules for Hungarian grammatical cases where we will recognize status street names and also change a/az articles appropriately. We can treat all unrecognized as highway refs and always use az there (but all foreign street names will be also here 😢) or add special rules to match "typical" highway refs (capital letter with digits or digits only, etc).

Currently I know 11 Hungarian status street names:
https://github.com/yuryleb/garmin-russian-tts-voices/blob/121a9bfe49eba702d5f244cd34ec8b0b7201aabb/src/Pycckuu__Milena%202.10/RP_RSET.TXT#L482-L493
Maybe you could extend this list more?

Also what grammatical cases could be applied for Hungarian messages? For example Russian localization supports 4 cases (accusative, dative, genitive and prepositional).

Wait, so whether the instruction uses “a” or “az” depends on whether it’s a motorway? Or does it depend on some other aspect of the road related to motorways, like whether there’s a ref instead of a name?

alexwyattdev · 2019-03-19T18:29:02Z

Also I already had to write my own logic for correcting a(z) including highway names, since my project needed to proceed further. (Its on android, not js and not regex based)

1ec5 · 2019-03-20T01:42:14Z

Its on android, not js and not regex based

If you’re using the Mapbox Navigation SDK for Android, note that improvements to OSRM Text Instructions are incorporated into the Mapbox Directions API and therefore the navigation SDK as well. Ideally the navigation SDK would take care of details like this so you don’t have to in your application code.

alexwyattdev · 2019-03-20T07:21:01Z

An example of special case dor a az: usually highways in hungary starts with an M and then a number and the pronounciation is "emm" so thats why it needs an az before it in this special case.

yuryleb · 2019-03-20T14:43:58Z

usually highways in hungary starts with an M and then a number and the pronounciation is "emm"

Makes sense 😉

@kiskunk, could you please also answer for my questions above? And also should Hungarian street names be changed together with status names for a grammatical case similar to Russian streets?

alexwyattdev · 2019-03-20T15:40:23Z

usually highways in hungary starts with an M and then a number and the pronounciation is "emm"

Makes sense 😉

@kiskunk, could you please also answer for my questions above? And also should Hungarian street names be changed together with status names for a grammatical case similar to Russian streets?

So here is a complete list of possible street ending names (i mean like in Boulevard Street where "Street" is the ending) it includes those 11 too from your link.

WayNameEnding[] wayNameEndings = {
new WayNameEnding(" árok", "árkon", "árokra"),
new WayNameEnding(" átjáró", "átjárón", "átjáróra"),
new WayNameEnding(" dűlő", "dűlőn", "dűlőre"),
new WayNameEnding(" dűlőút", "dűlőúton", "dűlőútra"),
new WayNameEnding(" erdősor", "erdősoron", "erdősorra"),
new WayNameEnding(" fasor", "fasoron", "fasorra"),
new WayNameEnding(" forduló", "fordulón", "fordulóra"),
new WayNameEnding(" gát", "gáton", "gátra"),
new WayNameEnding(" határsor", "határsoron", "határsorra"),
new WayNameEnding(" határút", "határúton", "határútra"),
new WayNameEnding(" kapu", "kapun", "kapura"),
new WayNameEnding(" körönd", "köröndön", "köröndre"),
new WayNameEnding(" körtér", "körtéren", "körtérre"),
new WayNameEnding(" körút", "körúton", "körútra"),
new WayNameEnding(" köz", "közön", "közre"),
new WayNameEnding(" lakótelep", "lakótelepen", "lakótelepre"),
new WayNameEnding(" lejáró", "lejárón", "lejáróra"),
new WayNameEnding(" lejtő", "lejtőn", "lejtőre"),
new WayNameEnding(" lépcső", "lépcsőn", "lépcsőre"),
new WayNameEnding(" liget", "ligeten", "ligetre"),
new WayNameEnding(" mélyút", "mélyúton", "mélyútra"),
new WayNameEnding(" orom", "ormon", "oromra"),
new WayNameEnding(" ösvény", "ösvényen", "ösvényre"),
new WayNameEnding(" park", "parkon", "parkra"),
new WayNameEnding(" part", "parton", "partra"),
new WayNameEnding(" pincesor", "pincesoron", "pincesorra"),
new WayNameEnding(" rakpart", "rakparton", "rakpartra"),
new WayNameEnding(" sétány", "sétányon", "sétányra"),
new WayNameEnding(" sikátor", "sikátoron", "sikátorra"),
new WayNameEnding(" sor", "soron", "sorra"),
new WayNameEnding(" sugárút", "sugárúton", "sugárútra"),
new WayNameEnding(" tér", "téren", "térre"),
new WayNameEnding(" udvar", "udvaron", "udvarra"),
new WayNameEnding(" út", "úton", "útra"),
new WayNameEnding(" utca", "utcán", "utcára"),
new WayNameEnding(" üdülőpart", "üdülőparton", "üdülőpartra"),
new WayNameEnding(" lánchíd", "lánchídon", "lánchídra"),
new WayNameEnding(" híd", "hídon", "hídra")};

Grammatical cases as far as i could determine it would require only 2 of ours, but i do not know the name of those cases.
the first is the root name, the second is how it changes when you would say "on Boulevard Street", the 3rd is how it would change when you would say "onto Boulevard Street"
its a much harder implementation (if even possible) because its based on vowel harmony for 90%, so its not even for 100%... what i put in the translation on transifex solves this issue by using an additional word like if you would say "turn left onto Boulevard Street section"

I think with using the grammar file for standard street names to balance out a/az AND making a rule for M0, M1 ... M85 ... etc would cover almost all except the non-hungarian street names (there are only a few)

For the grammatical cases and the M0..M1 highway names its another dimension of difficulty (at least when the Mapbox SDK tries to read it out loud), because of how it would say the numbers, the numbers also would require a different suffix. For example M0 would be read like "emm nulla" but since we want to use it in context and a sentence, it would be "emm nullás", and thats not the end because it would still need the "section" word after it (which i think its already there in transifex because its a general translation) or to be better for the ears, the logic from the previous grammar cases, making it into "emm nulláson" or "emm nullásra", to write this logic it requires to have the numbers 0-20,30,40,50,60,70,80,90,100,200,300.. etc to be defined too with that 2 grammar case, maybe its enough to stay below 1000, i don't think that would come up in any hungarian highway names.

1ec5 · 2019-03-21T00:00:02Z

For example M0 would be read like "emm nulla" but since we want to use it in context and a sentence, it would be "emm nullás", and thats not the end because it would still need the "section" word after it (which i think its already there in transifex because its a general translation) or to be better for the ears, the logic from the previous grammar cases, making it into "emm nulláson" or "emm nullásra", to write this logic it requires to have the numbers 0-20,30,40,50,60,70,80,90,100,200,300.. etc to be defined too with that 2 grammar case, maybe its enough to stay below 1000, i don't think that would come up in any hungarian highway names.

An SSML-aware text-to-speech engine might already handle optimizing numbers or alphanumeric words for speech. (The Mapbox Directions API wraps {way_name} etc. in <speak-as interpret-as="address"> for that reason.) I don’t think OSRM Text Instructions is in a great position to implement number formatting for speech all by itself. That would be a valid feature request against the navigation SDK for when it falls back to the Android TTS engine (since the Mapbox Voice API doesn’t support Hungarian).

what i put in the translation on transifex solves this issue by using an additional word like if you would say "turn left onto Boulevard Street section"

That’s reasonable. The only reason I brought up the grammar file was because of “a(z)”, which a text-to-speech engine is unlikely to pronounce correctly under any circumstance, unfortunately. That said, this PR doesn’t have to be the end of Hungarian localization work. If you think optimizing articles and numbers would be enough of a rabbit hole, we can merge this PR and would welcome any additional contributions regarding grammar.

yuryleb · 2019-03-21T06:11:03Z

If we're talking about articles change only, it's not too hard to implement here 😉

BTW how a/az should be changed before numbers in phrases like "Megérkezett a(z) 1. célponthoz, a bal oldalon" - I suppose to a everywhere?

But adding 2 grammatical cases support will be not too hard too if we need to change street status name only. @kiskunk, am I understand properly that "turn right onto the street" instruction with Dohány utca street name should look like:

Forduljon be jobbra a Dohány utcára felé

And we don't need to change the Dohány name?

alexwyattdev · 2019-03-21T07:01:23Z

I think a(z) is ok for now. As for jumbers it would be "megérkezett az 1. célponthoz" but "megérkezett a 2. célponthoz" so its atain an another level of complication of what letter the spoken number would start with.

And for the street name it would be: Forduljon jobbra a Dohány utcára. without the "felé" and yes Dohány would not change

yuryleb · 2019-03-22T06:49:39Z

Ok, please look at first Hungarian grammar rules to handle articles only yet:

Grammar could be extended further to apply grammatical cases to Hungarian street names - I suppose this could be based on analyzing of following magic words after {way_name} & {rotary_name} variables:

felé
irányába
szakaszon

@kiskunk, you told about 2 grammatical cases but here are 3 variants - does some of them use the same grammatical case as another (if I'm right in my presumption at all)?

And BTW you seem to forget to include alagút (tunnel) status name into your wayNameEndings list.

alexwyattdev · 2019-03-22T07:38:50Z

The image looks correct.

My list was from Wikipedia, so i will have to try to update that too with alagút. thanks.

Felé and Irányába are interchange-able, they both represent one of the 2 cases, szakaszon represents the other. I just added the other 2 for a little bit of word diversity, I used felé for way_names, and irányába for destination.

yuryleb · 2019-03-23T17:22:45Z

One more question, @kiskunk: how to proceed foreign names - I suppose it's better to keep these felé/irányába/szakaszon words on their original place in instructions?

alexwyattdev · 2019-03-23T19:03:10Z

yes, thats the best way i can imagine

yuryleb · 2019-03-23T21:31:10Z

languages/translations/hu.json

+            "straight": {
+                "default": "Hajtson egyenesen",
+                "name": "Hajtson egyenesen {way_name:article} felé",
+                "destination": "Hajtson egyenesen {destination} irányba"


@kiskunk, maybe there should be irányába not irányba? And article a(z) is missing here?

yuryleb · 2019-03-23T21:32:33Z

languages/translations/hu.json

+            "straight": {
+                "default": "Hajtson tovább egyenesen",
+                "name": "Hajtson tovább egyenesen {way_name:article} felé",
+                "destination": "Hajtson tovább egyenesen {destination} irányba"


@kiskunk, maybe there should be irányába not irányba? And article a(z) is missing here?

yuryleb · 2019-03-23T21:33:20Z

languages/translations/hu.json

+            "uturn": {
+                "default": "Forduljon vissza az út végén",
+                "name": "Forduljon vissza {way_name:article} végén",
+                "destination": "Forduljon vissza {destination} irányban az út végén"


@kiskunk, maybe article a(z) is missing here?

alexwyattdev · 2019-03-23T22:36:59Z

Yes, I corrected the irányába, and added the missing a(z)

yuryleb · 2019-03-24T20:55:16Z

OK, now I added support of Sublative and Superessive grammatical cases (yes, they're called so 😉), please review how this looks on Hungarian streets:

And on foreign ones:

alexwyattdev · 2019-03-24T22:40:18Z

Looks good to me, great job, thanks.

1ec5

🙇

- Added a Hungarian localization and grammar. [#274](#274) - Added a Japanese localization. [#277](#277) - Added an Arabic localization. [#267](#267) - Added a Slovenian localization. [#264](#264) - Updated Russian arrive instructions. [#278](#278) - Updated French grammar with 'chaussée' status street name and better articles matching. [#268](https://github.com/Project-OSRM/osrm-text-instructions/pull/268)[#279](https://github.com/Project-OSRM/osrm-text-instructions/pull/279)

Add Hungarian localization

e5c5a39

alexwyattdev suggested changes Feb 28, 2019

View reviewed changes

Update from Transifex and change log

48d85c7

yuryleb commented Mar 2, 2019

View reviewed changes

alexwyattdev suggested changes Mar 4, 2019

View reviewed changes

Next update from Transifex

d97a489

yuryleb commented Mar 4, 2019

View reviewed changes

alexwyattdev suggested changes Mar 5, 2019

View reviewed changes

Extra whitespaces fix from Transifex

47850f7

alexwyattdev approved these changes Mar 6, 2019

View reviewed changes

yuryleb mentioned this pull request Mar 19, 2019

Request to add Japanese Localization from Transifex #276

Closed

1ec5 reviewed Mar 19, 2019

View reviewed changes

1ec5 added the translations label Mar 19, 2019

yuryleb added 2 commits March 22, 2019 09:18

Fixed processing grammar rules even for empty name

6477b05

Initial Hungarian grammar rules to insert articles

491de3c

yuryleb commented Mar 23, 2019

View reviewed changes

Support of Hungarian sublative and superessive grammatical cases

b2ca46f

Merge branch 'master' into tx-hu

6a9c2ea

1ec5 approved these changes Mar 26, 2019

View reviewed changes

1ec5 merged commit 9de8ca2 into Project-OSRM:master Mar 26, 2019

yuryleb deleted the tx-hu branch March 26, 2019 20:43

1ec5 mentioned this pull request Mar 26, 2019

Hungarian language pull request #271

Closed

kevinkreiser mentioned this pull request Mar 29, 2019

v0.13.3 #280

Merged

4 tasks

	var replaces = [
	[' (de )?\{destination\}', ' {destination:preposition}'], // eslint-disable-line no-useless-escape
	[' (le rond-point )?\{rotary_name\}', ' {rotary_name:rotary}'], // eslint-disable-line no-useless-escape
	[' fin (de )?(la route )?\{way_name\}', ' fin {way_name:preposition}'], // eslint-disable-line no-useless-escape
	[' \{way_name\}', ' {way_name:article}'], // eslint-disable-line no-useless-escape
	[' (à )?\{waypoint_name\}', ' {waypoint_name:arrival}'] // eslint-disable-line no-useless-escape
	];

Add Hungarian localization #274

Add Hungarian localization #274

Conversation

yuryleb commented Feb 28, 2019 • edited Loading

Issue

Tasklist

alexwyattdev left a comment

Choose a reason for hiding this comment

yuryleb commented Feb 28, 2019

alexwyattdev commented Mar 1, 2019

yuryleb commented Mar 1, 2019

alexwyattdev commented Mar 1, 2019

yuryleb commented Mar 1, 2019

alexwyattdev commented Mar 1, 2019

yuryleb commented Mar 2, 2019 • edited Loading

alexwyattdev commented Mar 2, 2019

yuryleb commented Mar 2, 2019

alexwyattdev commented Mar 2, 2019

yuryleb commented Mar 2, 2019

Choose a reason for hiding this comment

alexwyattdev left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

yuryleb commented Mar 4, 2019

alexwyattdev commented Mar 4, 2019

alexwyattdev left a comment

Choose a reason for hiding this comment

yuryleb commented Mar 6, 2019

alexwyattdev left a comment

Choose a reason for hiding this comment

yuryleb commented Mar 6, 2019

alexwyattdev commented Mar 6, 2019

yuryleb commented Mar 8, 2019

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

yuryleb Mar 19, 2019 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

alexwyattdev commented Mar 19, 2019

1ec5 commented Mar 20, 2019

alexwyattdev commented Mar 20, 2019

yuryleb commented Mar 20, 2019

alexwyattdev commented Mar 20, 2019

1ec5 commented Mar 21, 2019

yuryleb commented Mar 21, 2019 • edited Loading

alexwyattdev commented Mar 21, 2019

yuryleb commented Mar 22, 2019

alexwyattdev commented Mar 22, 2019

yuryleb commented Mar 23, 2019

alexwyattdev commented Mar 23, 2019

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

alexwyattdev commented Mar 23, 2019

yuryleb commented Mar 24, 2019

alexwyattdev commented Mar 24, 2019

1ec5 left a comment

Choose a reason for hiding this comment

yuryleb commented Feb 28, 2019 •

edited

Loading

yuryleb commented Mar 2, 2019 •

edited

Loading

yuryleb Mar 19, 2019 •

edited

Loading

yuryleb commented Mar 21, 2019 •

edited

Loading