-
Notifications
You must be signed in to change notification settings - Fork 56
[WIP] Discussion of usage for translated TRPL #28
Conversation
Thanks for the PR! I'll have a look at the actual changes later, and see if I can merge the fixes. As you may have seen, trpl-ebook is pretty inactive right now. Recently, some people started doing some work over at mdBook, though, with the goal to have that application render stuff using LaTeX. mdBook is an actual binary that works like rustbook and is configured by metadata (IIRC), so that might be of interest to you. Have a great evening,
|
Hi!
I would like to start by saying I don't indend this PR to be merged in your repository and rather discuss some issues and potential solutions so maybe we could collaborate on them.
As you might know, we, over at @ruRust, have translated the TRPL in Russian. We also provided ebook versions of the book with Calibre. Unfortunately, the story was less than smooth, so now I'm looking at trpl-ebook to use it in our infrastructure instead. Hope you don't mind!
This PR illustrates the changes that were needed in order to get more-or-less working translation. The first commit is just import of our data and can be ignored. Some of the rest, I believe, are legitimate fixes (d080714 , 2372488 , 337f119). They could be cherry-picked and merged if you agree they are necessary and good ones. I can provide details why did I do them.
Then, there are changes in code due to some resources being hard-coded in sources: 3914c1b , c47bc94#diff-ef03e76469e3c2afd2e0018d57dccce8L1 . These parts could be further factored out to metadata.
Then, I think it makes sense to make
trpl-ebook
a proper binary crate, that could be used as an external program - so that translators pointed it to metadata and content, and it would convert everything. It also happens to me we don't want conversion to some formats (letter) and want conversion to some others (MOBI).I understand issues are better for tracking work, I just want to hear your overall opinion first. I could file proper issues later if we decide they are needed.
So, what I, on behalf of ruRust community, would like to know, is whether you're interested in these changes, will accept new proper PRs, and ready to further discuss the details.
Regards,
Michael