wow
parent
eea52bccc9
commit
2c89dacde4
|
@ -14,3 +14,17 @@ The current version is a proof-of-concept, mature enough for me to dare submitti
|
||||||
but I'm prepared to hear various helpful remarks, and to rewrite parts of it as needed.
|
but I'm prepared to hear various helpful remarks, and to rewrite parts of it as needed.
|
||||||
|
|
||||||
Any thoughts on this?
|
Any thoughts on this?
|
||||||
|
|
||||||
|
> Well, I think it's pretty stunning what you've done here. Seems very
|
||||||
|
> complete and well thought out. I have not read the code in great detail
|
||||||
|
> yet.
|
||||||
|
>
|
||||||
|
> Just using po files is an approach I've never seen tried with a wiki. I
|
||||||
|
> suspect it will work better for some wikis than others. For wikis that
|
||||||
|
> just want translations that match the master language as closely as
|
||||||
|
> possible and don't wander off and diverge, it seems perfect. (But what happens
|
||||||
|
> if someone edits the Discussion page of a translated page?)
|
||||||
|
>
|
||||||
|
> Please keep me posted, when you get closer to having all issues solved
|
||||||
|
> and ready for merging I can do a review and hopefully help with the
|
||||||
|
> security items you listed. --[[Joey]]
|
||||||
|
|
Loading…
Reference in New Issue