Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The translation of the habrahabr article about Wine, Steam API and Nim #76

Open
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

xomachine
Copy link

As it was discussed in IRC before, I've made a translation of the article. It requires a serious proofreading before posting.

The github preview does not show the actual look of the article. It is better to look at it as it will be in site.

@dom96
Copy link
Contributor

dom96 commented Mar 13, 2018

Awesome! Thank you for working on this :D

@dom96
Copy link
Contributor

dom96 commented Mar 13, 2018

I only skimmed it so far because I'm in a lecture, but looks very good.

One thing I might suggest is simplifying the title, thoughts?

@xomachine
Copy link
Author

How about
"Using Nim for steam winelib building"
"Creating Steam API winelib using Nim"

@dom96
Copy link
Contributor

dom96 commented Mar 14, 2018

"Using Nim to forward calls between the Steam API and Wine"?

@xomachine
Copy link
Author

Not quite that this article is about. Actual forwarding is being performed between Windows app (under Wine) and Linux library. Steam API exists in both of sides. So it should probably sound like
"Using Nim to forward Steam calls between the Linux and Wine"
But it complicates title again...

@dom96
Copy link
Contributor

dom96 commented Mar 14, 2018

I think this sounds good, just drop the "the": "Using Nim to forward Steam calls between Linux and Wine"

@dom96
Copy link
Contributor

dom96 commented Mar 20, 2018

I went through it at did my best to make some corrections where I could. One thing I didn't quite understand, maybe you could rephrase these?

As a basis, we can take a native Steam client, and games for Windows will address it just like, for example, to OpenGL or the sound subsystem of GNU/Linux - through the Wine.

Please have a look through my changes and see if you're happy with them :)

dom96 added a commit that referenced this pull request Mar 20, 2018
@xomachine
Copy link
Author

Looks nice!

Well, that was quite hard but I tried:

Let's keep the native Steam client only. Windows games will communicate with it in a way like any other windows application communicates with GNU/Linux subsystems.

@xomachine
Copy link
Author

Is there anything else that I can fix/change/rephrase in this article?
Is it going to be published?

@dom96
Copy link
Contributor

dom96 commented Apr 25, 2018

Sorry, exams and other busy things got in my way.

I think before we can publish this @Araq wants to read over it and correct some grammar so it may be a while yet. I'll ping him.

@dom96 dom96 force-pushed the master branch 2 times, most recently from 9b17d93 to 7bdd2e1 Compare June 4, 2019 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants