search

JuliaCN / JuliaZH.jl

Julia语言中文文档
https://docs.juliacn.com
MIT License
512 stars 95 forks source link

using JuliaZH doesn't replace kw_str doc #41

Closed Roger-luo closed 5 years ago

Roger-luo commented 6 years ago

I posted a MWE on discourse: https://discourse.julialang.org/t/cannot-replace-doctoring-in-projects/15805

ViralBShah commented 5 years ago

Probably should go upstream to make translations first class.

Gnimuc commented 5 years ago

It would be great if we could either use or emulate GNU gettext in Julia.

Roger-luo commented 5 years ago

Yeah, but I think this is some issue related to some commit in 0.7, it worked in 0.7 for some period. I couldn't locate the bug however, dunno know why this happens yet.

inkydragon commented 5 years ago

use or emulate GNU gettext in Julia.

Gnimuc commented 5 years ago

I guess the problem is no one would like to invest time to make this happen for now. Emulating gettext in Julia needs to hack into the Julia compiler, the first step is writing a Julep proposal. But the good news is we only need a PO file parser for supporting docstring substitution.

Roger-luo commented 5 years ago

Yeah, agree with @Gnimuc I believe for most people after reading manual, they will be able to use most of the functionality and who is interested in development usually has the ability on reading English. We haven't had a large user group that requires such localization yet.

Other package/functionality can be in higher priority, so people have to work on other things first. Like me, my job queue is totally full for the next 4 month… So I would say we should wait for a while on this, and focus on manual first.

And on the other side, machine translation algorithm is growing fast, my friends are working on something related, they can analysis HTML directly (https://fanyi.caiyunapp.com). so I'm wondering if it's possible to integrate their application or things like Google translate directly. Then even new package developed in Julia will get i18n support.

I just asked their CTO about this. I'll update here if we get any further idea.

But again, I guess this won't influence much on the user experience. So not as urgent as manual part.

Roger-luo commented 5 years ago

And the point for the original issue is that the doc string for keywords is not working after 1.0. it's definitely some kind of bug. Nothing related to gettext in this part.