Re: Feedback request | Documentation site reorg, switch to Markdown
On 02/27/2017 08:00 AM, Doug Smythies wrote: Very true, and a good point. Debugging some mistake is very very annoying and time consuming. In terms of warnings and error messages, I have no experience with the proposed Markdown method. Because it's made to look like plain-text, I do have to say that debugging Markdown is one of the simplest things there is. Even GEdit's syntax highlighting is sufficient, although there are plenty of of other live-preview editors out there as well. Find a format that the average person can use to write new material for Ubuntu Server without having to devote an inordinate amount of time learning compared to the time they will spend writing. That definitely describes Markdown. It's the least obtrusive markup system I've seen. -- Nathan Haines Ubuntu - http://www.ubuntu.com/ -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: Feedback request | Documentation site reorg, switch to Markdown
Being part of a team that is now contributing on a weekly basis to docs.ubuntu.com/core, I can confidently mention that what we are doing with these contributions has been working out nicely. We have a use case of needing to contribute high quality documentation that is updated on a regular basis for our commercial IoT customers. To meet this goal, we've basically made documentation a required piece for every merge/pull request for the snaps that we maintain for our commercial customers (obviously there are a few exceptions where this doesn't make sense). We laid things out in a tree structure that integrates nicely with documentation-builder, yet facilitates our team's need to update the documentation rapidly by being able to peer-review the documentation within our own team. For these reviews, we are making sure to follow a common style guide. Also of importance to highlight is that we store the documentation, written in Markdown, right in each snap's git repository alongside of the code. We've created a standard directory structure for this and we aggregate this up to docs.ubuntu.com/core with the use of git-repo. Take a look at the README.md for how simple this is to work with for generating the final docs [1]. I can't emphasize enough how easy this structure is to work with and how well it has scaled for our needs thus far. It might not be the right model for every use case, but it should be a very good fit for the majority of use cases surrounding Ubuntu. Markdown is an absolute pleasure to work with which is a critical point. We developers generally hate writing documentation and so making it as frictionless as possible is a very high ideal - one that I think Markdown facilitates quite nicely. [1] https://github.com/CanonicalLtd/ubuntu-core-docs/blob/master/README.md On Mon, Feb 27, 2017 at 11:00 AM, Doug Smythies wrote: > On 2017.02.22 16:47 Peter Matulis wrote: > > > I should mention to the uninitiated that a single wayward character will > generate > > a bewildering error when a build of HTML is attempted. Considering that > you need > > to go through a long file full of the above stuff, I recall my > "debugging" sessions > > consuming a large amount of my time, not to mention the frustration. > > Very true, and a good point. > Debugging some mistake is very very annoying and time consuming. > In terms of warnings and error messages, I have no experience with the > proposed > Markdown method. > > > Is there ANYONE out there that has written a significant amount of > material for the Server > > Guide and also believes we should stick with XML/Docbook? These are the > people I > > especially want to hear from. > > Either way, I'd still like to hear from Serge Hallyn, Ted Cox, Christian > Ehrhardt, Nish Aravamudan, > Simon Quigley, Ian Nicholson. > > > I believe that XML is technically superior to Markdown and it definitely > has advantages, > > but only when used in certain contexts. A good example is a single > author, or a team of > > dedicated people, writing for a project, like an O'Reilly book, for > instance. However, our > > contributors come and go. Each wants to help but very few will take the > time to understand a > > difficult format unless they expect to do sustained writing. This is > just not our reality. What > > we're trying to solve here is: > > > > Find a format that the average person can use to write new material for > Ubuntu Server without > > having to devote an inordinate amount of time learning compared to the > time they will spend writing. > > > > ... Doug > > > > -- > ubuntu-translators mailing list > ubuntu-translators@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators > -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
RE: Feedback request | Documentation site reorg, switch to Markdown
On 2017.02.22 16:47 Peter Matulis wrote: > I should mention to the uninitiated that a single wayward character will > generate > a bewildering error when a build of HTML is attempted. Considering that you > need > to go through a long file full of the above stuff, I recall my "debugging" > sessions > consuming a large amount of my time, not to mention the frustration. Very true, and a good point. Debugging some mistake is very very annoying and time consuming. In terms of warnings and error messages, I have no experience with the proposed Markdown method. > Is there ANYONE out there that has written a significant amount of material > for the Server > Guide and also believes we should stick with XML/Docbook? These are the > people I > especially want to hear from. Either way, I'd still like to hear from Serge Hallyn, Ted Cox, Christian Ehrhardt, Nish Aravamudan, Simon Quigley, Ian Nicholson. > I believe that XML is technically superior to Markdown and it definitely has > advantages, > but only when used in certain contexts. A good example is a single author, or > a team of > dedicated people, writing for a project, like an O'Reilly book, for instance. > However, our > contributors come and go. Each wants to help but very few will take the time > to understand a > difficult format unless they expect to do sustained writing. This is just not > our reality. What > we're trying to solve here is: > > Find a format that the average person can use to write new material for > Ubuntu Server without > having to devote an inordinate amount of time learning compared to the time > they will spend writing. > ... Doug -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: Japanese team (reviewer) is not working
> This is not Ubuntu, but I know that it is translating overseas using > Google Translate. > Perhaps there are other overseas users who do not know. > Please tell the translators around the world. Shortly, this painful case are (probably) your case only. I'll explain why in few days... -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: Japanese team (reviewer) is not working
Hi Yoshida-san, > Question from > https://lists.ubuntu.com/archives/ubuntu-translators/2017-February/007326.html >> So, in this phase, I have a sense of crisis from this page and your >> translation works. Sorry for this explicit question, but I must say >> this, you don't have enough knowledge about FLOSS cultures and >> licensing? And, please provide your truth in past works(see past >> replies). > > And, please stop your work "with Translation Service" model with your > favorites services (+ "by Translation Service", "by Translation > Service and review by contributor" models also affected). Their > services are not have contract requirements, so they have fatal risk. > No EULA/no contract services are venom for our freedom. Sorry for less > details, I'll provide more background in few days. > > Regards, I do not have much knowledge. Thank you for telling me. This is not Ubuntu, but I know that it is translating overseas using Google Translate. Perhaps there are other overseas users who do not know. Please tell the translators around the world. I apologize in advance if anything will increase your extra work. I'm sorry. I will reflect on and stop handling the translation work. I will contribute in the future with other work corresponding to that. I'm really sorry. And thank you. BALLOON a.k.a. Fu-sen. (Keiichi SHIGA) balloonakafu...@gmail.com https://launchpad.net/~balloon -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: Japanese team (reviewer) is not working
Hi, Question from https://lists.ubuntu.com/archives/ubuntu-translators/2017-February/007326.html > So, in this phase, I have a sense of crisis from this page and your > translation works. Sorry for this explicit question, but I must say > this, you don't have enough knowledge about FLOSS cultures and > licensing? And, please provide your truth in past works(see past > replies). And, please stop your work "with Translation Service" model with your favorites services (+ "by Translation Service", "by Translation Service and review by contributor" models also affected). Their services are not have contract requirements, so they have fatal risk. No EULA/no contract services are venom for our freedom. Sorry for less details, I'll provide more background in few days. Regards, -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: Japanese team (reviewer) is not working
Hi, > And please re-subscribe this mailing list and answer another questions. Thank you. Ikuya-san. I came back here. list moderator: i'm sorry for your extra manual work. If there is a question I had overlooked, Please tell me by posting again. sorry... BALLOON a.k.a. Fu-sen. (Keiichi SHIGA) balloonakafu...@gmail.com https://launchpad.net/~balloon -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: Japanese team (reviewer) is not working
Hi Fu-sen san, Thank you for your explanation. I know it is gettext's behavior. I am sorry for my suspicion. And please re-subscribe this mailing list and answer another questions. Regards, On Mon, 27 Feb 2017 20:29:40 +0900 "BALLOON a.k.a. Fu-sen." wrote: > Hi, Ikuya-san > > I know your great contribution. > Thanks to you, now I can use various software in Japanese. > Thank you very much! :) > > > I will respond to your concerns: > > > > 2) And,what's happen at this tweet? > > > https://twitter.com/balloon_vendor/status/817929412356214784 > > > > ああ、明らかに他もおかしいですね。version→で開くになってしまってますので。何か自動翻訳でおかしく入っている可能性がありそうです。確認して修正します。Ubuntu > > > > Budgie が採用する予定なのでこの連絡はありがたいです。ありがとうございます。 > > I worried about this tweet, too. > > I think 自動翻訳 means 機械翻訳 (machine translation). Is it correct? > > 「何か自動翻訳でおかしく入っている可能性がありそうです。」means you input machine > > translations into Launchpad without any modification. Is it correct? > > > I am dealing with it using Terminix's issue: > https://github.com/gnunn1/terminix/issues/678 > > "That's just how gettext works." > > Perhaps you can understand that details. > > If you need this confirmation and improvement, > I would be happy if you could assist. > That is a tremendous contribution to Ubuntu Budgie. > > > You and I will make up here. Let's cooperate and work in the future! > Sorry until now. And thanks to the wonderful people. > > > BALLOON a.k.a. Fu-sen. (Keiichi SHIGA) > balloonakafu...@gmail.com > https://launchpad.net/~balloon > -- AWASHIRO Ikuya ik...@fruitsbasket.info / ik...@oooug.jp / iku...@gmail.com GPG fingerprint: 1A19 AD66 C53F 2250 3537 1A9D 3A53 2C1D 20AB CC8A -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: Japanese team (reviewer) is not working
Hi Fu-sen san, Due to undelivered mails (maybe), I don't know in detail. On Sat, 25 Feb 2017 19:54:24 +0900 Fumihito YOSHIDA wrote: > 2) And,what's happen at this tweet? > https://twitter.com/balloon_vendor/status/817929412356214784 > > ああ、明らかに他もおかしいですね。version→で開くになってしまってますので。何か自動翻訳でおかしく入っている可能性がありそうです。確認して修正します。Ubuntu > > Budgie が採用する予定なのでこの連絡はありがたいです。ありがとうございます。 I worried about this tweet, too. I think 自動翻訳 means 機械翻訳 (machine translation). Is it correct? 「何か自動翻訳でおかしく入っている可能性がありそうです。」means you input machine translations into Launchpad without any modification. Is it correct? Would you please answer above questions. All your contribution are belong by proprietary. I am sorry for a corny joke. Regards, -- AWASHIRO Ikuya ik...@fruitsbasket.info / ik...@oooug.jp / iku...@gmail.com GPG fingerprint: 1A19 AD66 C53F 2250 3537 1A9D 3A53 2C1D 20AB CC8A -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
