[Ubuntu-manual] [Bug 504058] Re: Currently no uniform method of writing code and directives
I've added some formatting code to handle terminal input/output and
inline code.
The terminal environment can be used for code blocks:
\begin{terminal}
\prompt \userinput{sudo apt-get install banshee}
Password: \userinput{s3krE7}
Installing banshee...
Banshee installed!
\end{terminal}
For inline code, use the \code command:
Type \code{\userinput{banshee}} to start the Banshee music player.
The \prompt command prints a bash user prompt ($), \rootprompt prints a
bash root prompt (#), and \userinput will set special formatting for the
user's input -- currently set to red for easy editing and debugging.
Let me know if there are other requirements.
--
Currently no uniform method of writing code and directives
https://bugs.launchpad.net/bugs/504058
You received this bug notification because you are a member of Ubuntu
Manual Team, which is subscribed to Ubuntu Manual.
Status in Ubuntu Manual: In Progress
Status in Ubuntu Manual main series: In Progress
Bug description:
Not sure if this has been discussed but we need a uniform way of
writing/displaying code and directives that will be consistent throughout the
manual.
- By code I mean anything we are telling a reader to input into a terminal
(i.e. sudo apt-get update)
- By directives I mean anything that directs a user (i.e. click on
system->preferences->appearance etc)
I think we need to decide on how we want these to be displayed in the manual,
so that we can write them correctly into the latex documents as we go. This
should save a heap of time later on.
Things to consider
- do we want code to sit in a 'code block' (similar to a text box), be written
in-line in the paragraph, have a line break before and after, or some other
method of identifying "this should be written into a terminal".
- should we use quotation marks around directives? If so should they be single
or double?
- should there be arrows between directives (such as above example), or
comma's, or something else?
Jamin
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 504058] Re: Currently no uniform method of writing code and directives
** Changed in: ubuntu-manual/main Status: In Progress => Fix Released -- Currently no uniform method of writing code and directives https://bugs.launchpad.net/bugs/504058 You received this bug notification because you are a member of Ubuntu Manual Team, which is subscribed to Ubuntu Manual. Status in Ubuntu Manual: Fix Released Status in Ubuntu Manual main series: Fix Released Bug description: Not sure if this has been discussed but we need a uniform way of writing/displaying code and directives that will be consistent throughout the manual. - By code I mean anything we are telling a reader to input into a terminal (i.e. sudo apt-get update) - By directives I mean anything that directs a user (i.e. click on system->preferences->appearance etc) I think we need to decide on how we want these to be displayed in the manual, so that we can write them correctly into the latex documents as we go. This should save a heap of time later on. Things to consider - do we want code to sit in a 'code block' (similar to a text box), be written in-line in the paragraph, have a line break before and after, or some other method of identifying "this should be written into a terminal". - should we use quotation marks around directives? If so should they be single or double? - should there be arrows between directives (such as above example), or comma's, or something else? Jamin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Introducing Kevin Godby's new feature: chaplink
Hello, Martin.
2010/1/20 Martin Lukeš :
> Thank you Kevin. Great feature.
>
> On behalf of all translators I'd like to ask you one thing.
> Do I have to translate that link, or can I simply keep the original text?
You should leave the entire \chaplink{ch:something} as is. The word
'chapter' will be translated by LaTeX automatically (once that we get
that incorporated), and the chapter title gets pulled from whatever is
in the \chapter{This is the chapter title} command, which should be
translated by the translators.
> Oh and one last thing useful for manual writers.
> As for spaces in chapter's names. Is there any replacing like "dash" for
> "space"?
The labels that are used (the ch:something-something) are generated by
hand. I've made a list of the current chapters and their labels here:
https://wiki.ubuntu.com/ubuntu-manual/StyleGuide#Formatting
Did that answer your question?
Please feel free to contact me with any questions about the LaTeX code
or which parts of the code should and should not be translated. I'll
try to collect the questions and answers in the style guide.
Thanks!
--Kevin
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] IMPORTANT: Feedback from Martin Owens
'allo. On Wed, Jan 20, 2010 at 4:21 AM, Benjamin Humphrey wrote: > Tonight I showed Martin the latest revision over IRC. Attached is the IRC > log of our conversation, where he raises some good points. Please have a > read! Here are the formatting issues I saw mentioned: 1. "Ubuntu Manual" text on title page is blurred. Yeah, gripe to inkscape about it. Right now we're just converting the svg to pdf using inkscape, and that's what it gives us. Converting the text/fonts to paths and then converting may help, but there are other conversion problems going on, too. It seems that inkscape doesn't support transparency in PDFs too well at the moment. 2. Table of contents is empty. I'm guessing this was due to a failed compilation. I'm going to try to get the LaTeX output colorized again (like the old Makefile did) so the errors are more obvious. 3. Contact details should be with the copyright details and contain PDF links. Well, yeah, they will be when I get the copyright page put in. Also, they're already links, so I'm not sure what the complaint refers to there. 4. Page break issues (i.e., 'Canonical' should move to the next page). Handling special cases of page breaks will be the *very* last thing that gets done -- after all the text is written, after I've finished the document style, etc. Doing it before then just means you'll spend the remainder of your days moving manual page breaks around and that's just silly. 5. Copyright info. Yep, it's coming. I think that's all the formatting-related comments. So far, it's nothing new or that we (or at least I) didn't already know about. --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] Prerequisites to compiling the manual
Hello, all. I recently added a new required LaTeX package to compile the manual. Unfortunately, it's not packaged in any of the Ubuntu TeX packages (they're still using the old TeXLive 2007 stuff -- 2009 just came out). But, to make the installation as easy as possible, I've included a copy of the required package in the pkgs/ directory along with an install-pkgs.sh script. I'll keep the script up-to-date if we require more packages in the future. To run the script: cd pkgs ./install-pkgs.sh If one of the required Ubuntu packages is not yet installed, it may ask for your sudo password so that it can run apt-get. Otherwise, it'll automatically install all the required packages. I've only tested this script on a couple of my machines, so there may be bugs in it. If you find bugs or have problems running the script, you can email me the .log file and any error messages and I'll get them fixed. Thanks! --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Prerequisites to compiling the manual
On Fri, Jan 22, 2010 at 7:30 AM, Luke-Jennings wrote: > It took me a moment to work it out, but if you update your copy of > ubuntu-manual by following the directions at > https://wiki.ubuntu.com/ubuntu-manual/Help#Updating%20your%20local% > 20branch . Then within your ubuntu-manual folder there will be a folder > called pkgs within that is the script. Ah, yeah. Sorry about that; I should've been more clear. The script is in the bzr repository. --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 513257] Re: Text formatting for links
** Changed in: ubuntu-manual Assignee: (unassigned) => Kevin Godby (godbyk) ** Changed in: ubuntu-manual Status: New => In Progress ** Changed in: ubuntu-manual Importance: Undecided => Medium -- Text formatting for links https://bugs.launchpad.net/bugs/513257 You received this bug notification because you are a member of Ubuntu Manual Team, which is subscribed to Ubuntu Manual. Status in Ubuntu Manual: In Progress Bug description: When using \chaplink there is no visual difference in the text between normal text and the link. It is not obvious that link is click-able. The same is true when using \href. Some formatting should be applied to make a distinction between normal text and links. The text colour could be changed to one of the reds used in the titles. ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] Compiling translated PDFs
Good news, everyone! I've got a lot of the translation stuff automated now. Not-so-good news: If you want to compile translated documents, you'll have to jump through some hoops at first. First, for those of you who are just writing plain, boring English, nothing has changed for you. You can continue to run 'make' and everything should be fine. (If it's not, run the pkgs/install-pkgs.sh script and try again.) For those of you who would like to compile the PDF in your favorite language/dialect, you're going to have to install the latest version of TeX Live (2009). Unfortunately, this is not in the Ubuntu repositories. To install the latest TeX Live: 1. Uninstall all the Ubuntu TeX Live packages: sudo apt-get remove texlive-* 2. Download the TeX Live 2009 install script: http://mirror.ctan.org/systems/texlive/tlnet/install-tl-unx.tar.gz 3. Unpack the tarball: tar -zxvf install-tl-unx.tar.gz 4. Change to the newly-unpacked directory: cd install-tl-* 5. Run the script: ./install-tl 6. Select where you'd like to install everything, and any other options you prefer. (If you want to install someplace that you don't have permissions, you'll need to cancel and re-run the script with 'sudo'.) 7. Run the install-pkgs.sh script that's in the ubuntu-manual/pkgs/ dir to make sure you have all the required packages. 8. If everything checks out okay, you should be able to run: make ubuntu-manual-LANG.pdf where LANG is the language code (see the po/ dir for a list of supported languages). Note that not all languages are supported yet (especially those requiring non-Latin scripts). If you have any questions or run into any problems, feel free to contact me. I'm usually in IRC as godbyk and can, of course, be contacted via email. Cheers! --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] Kevin's status report
Hello, all. Since I won't be able to attend the meeting this weekend, I wanted to write up a quick status report of what I've been up to. I've been spending most of my time this week working on incorporating the translations back into our manual compiling process. I've updated the Makefile so that you can compile the translations:"make ubuntu-manual-LANG.pdf", where LANG is the language code [see the po/ dir for a list of possibilities], will compile that language's manual with whatever translations are available. A few things to note regarding the translations: Since our manual is being translated into so many varied languages (using varied scripts/alphabets), I've switched to using XeLaTeX instead of pdfLaTeX due to its better handling of Unicode. Additionally, XeLaTeX gives us access to a *much* wider range of typefaces, which will help a great deal since we're supporting so many scripts. The babel package is not compatible with XeLaTeX, so we're using its successor: polyglossia. Unfortunately, polyglossia is not included with the TeX Live 2007 packages that Ubuntu provides. We can't install the polyglossia package on its own because it requires a newer version of XeLaTeX than what the Ubuntu packages provide. So if you want to compile a translated document, you will need to install TeX Live 2009 directly. (See a previous email for an introduction on doing this.) If you only wish to compile the primary American English version, you may continue to do so without having to upgrade to TeX Live 2009 (though you will have to install the texlive-xetex Ubuntu package to make everything happy). I'm currently compiling each language's version of the manual and working with the translators to fill in a few holes in the polyglossia language coverage. I've emailed some translators for help in filling in this holes. My next step is to find nice typefaces for each of the languages we're supporting. This hinges in part on working with the design team to develop a tone and style of design for the manual so that it remains consistent across all the languages. After getting the typefaces lined up, I'll revisit the interior design, clean it up and make it consist with the design direction decided upon by the design team. tl;dr: I've been working on compiling the translations. If you want to compile the translations, you need to install TeX Live 2009. Next I'll be getting typefaces for each language. Then, working with the design team, I'll clean up the whole design of the manual. As always, if you have any questions, comments, suggestions, or criticisms, feel free to email me at or contact me on IRC in #ubuntu-manual (godbyk). Thanks! --Kevin P.S. I've posted a few of the translated manuals online at http://kevin.godby.org/private/ubuntu-manual/ if you want to take a look. ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] The Title
I agree with Thorsten's and Wendy's assessments: I prefer "Getting Started with Ubuntu 10.04." "The Ubuntu Manual" sounds comprehensive, detailed, and technical. I could see the name attracting a lot of non-beginner users who would then be disappointed at what they found. The name also invites scope creep, an urge to expand beyond our target audience. "Getting Started" clearly defines the type of material the reader should expect to find contained with book. The scope is better contained: we will only include material required to get started with Ubuntu. Finally, the language is friendlier toward our target audience. --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] Screenshot placeholder command
Hello, all.
One of the main goals for the beta release is to have the screenshots
in place. In order to facilitate this, I've added a new command that
we can put in as a placeholder until we get real screenshots:
\screenshotTODO{Description of the desired screenshot}
When you run 'make' to compile the PDF, the \screenshotTODO command
will insert a MISSING SCREENSHOT notice into the PDF and also add it
to the screenshots.log file. The screenshots.log file will end up
with a list of missing screenshots along with their description, the
chapter, and page they appear on. (The page number is approximate.)
Once we have a few screenshots to work with, I'll make a \screenshot
command to insert them into the document.
--Kevin
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Meeting last Saturday
'allo. On Tue, Feb 16, 2010 at 1:03 PM, Josh Holland wrote: > Can everyone who is giving a session *please, please, please* check over > the wiki page. I just added in a load of times for the Tuesday morning, > and I have no idea whether they're workable or not. It's pretty > important to get this sorted out ASAP. My time slots look okay, but I'm flexible on the Tuesday slot, so if anyone wants to trade, that's fine. Also, can we have everyone write a short summary of what they're going to cover in their sessions? I don't want to step on anyone's toes or cover a lot of the same material. Thanks! --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 522900] Re: Compiling in German gives the following error
I edited the po file directly and it compiles fine now.
** Changed in: ubuntu-manual
Status: New => Fix Committed
--
Compiling in German gives the following error
https://bugs.launchpad.net/bugs/522900
You received this bug notification because you are a member of Ubuntu
Manual Team, which is subscribed to Ubuntu Manual.
Status in Ubuntu Manual: Fix Committed
Bug description:
Compiles fine up to here. The last error is easy to fix but I have no clue how
to fix it in german, it should read \textbf not \texbf.
Package Fancyhdr Warning: \fancyhead's `E' option without twoside option is use
less on input line 280.
(/usr/share/texmf-texlive/tex/latex/titlesec/block.tss))
LaTeX Warning: Unused global option(s):
[lang=de,german].
No file ubuntu-manual-de.aux.
(/usr/share/texmf/tex/latex/tipa/t3cmr.fd)
*geometry detected driver: pdftex*
ABD: EveryShipout initializing macros
(/usr/share/texmf-texlive/tex/latex/hyperref/nameref.sty
(/usr/share/texmf-texlive/tex/latex/oberdiek/refcount.sty))
Package hyperref Warning: Rerun to get /PageLabels entry.
[1]
(/home/luke-jennings/texmf/tex/latex/ccicons/uccicons.fd)
LaTeX Warning: Reference `ch:license' on page i undefined on input line 31.
[1] [2]
Overfull \hbox (20.44525pt too wide) in paragraph at lines 84--88
\EU1/GentiumBookBasic(0)/m/n/10 Dieses Handbuch soll kein umfassendes Ubuntu-Un
terrichtsbuch sein. Es stellt mehr eine Schnellstart-
LaTeX Warning: Hyper reference `ch:learning-more' on page iii undefined on inpu
t line 95.
LaTeX Warning: Reference `ch:learning-more' on page iii undefined on input line
95.
LaTeX Warning: Hyper reference `ch:learning-more' on page iii undefined on inpu
t line 95.
LaTeX Warning: Reference `ch:learning-more' on page iii undefined on input line
95.
[3] [4]
LaTeX Warning: Hyper reference `ch:around-your-desktop' on page v undefined on
input line 205.
LaTeX Warning: Reference `ch:around-your-desktop' on page v undefined on input
line 205.
LaTeX Warning: Hyper reference `ch:around-your-desktop' on page v undefined on
input line 205.
LaTeX Warning: Reference `ch:around-your-desktop' on page v undefined on input
line 205.
[5]
LaTeX Warning: Hyper reference `ch:installation' on page vi undefined on input
line 240.
LaTeX Warning: Reference `ch:installation' on page vi undefined on input line 2
40.
LaTeX Warning: Hyper reference `ch:installation' on page vi undefined on input
line 240.
LaTeX Warning: Reference `ch:installation' on page vi undefined on input line 2
40.
Overfull \hbox (15.50873pt too wide) in paragraph at lines 242--251
\EU1/GentiumBookBasic(0)/m/sc/10 Wenn Sie gerne ältere Spiele spielen, können
Sie bestimmte beliebte Spiele unter einem Windows-
[6] [1]
Kapitel 1.
Overfull \hbox (27.73041pt too wide) in paragraph at lines 316--324
\EU1/GentiumBookBasic(0)/m/sc/10 Arbeitsspeicher Ihres Rechners, wird sich dabe
i aber etwas zäh anfühlen (da die CD-Lesegeschwindigkeit
[2] [3] [4] [5] [6] [7]
Kapitel 2.
[8] [9]
LaTeX Warning: Hyper reference `ch:default-applications' on page 10 undefined o
n input line 686.
LaTeX Warning: Reference `ch:default-applications' on page 10 undefined on inpu
t line 686.
LaTeX Warning: Hyper reference `ch:default-applications' on page 10 undefined o
n input line 686.
LaTeX Warning: Reference `ch:default-applications' on page 10 undefined on inpu
t line 686.
[10]
LaTeX Warning: Hyper reference `ch:software-and-packaging' on page 11 undefined
on input line 720.
LaTeX Warning: Reference `ch:software-and-packaging' on page 11 undefined on in
put line 720.
LaTeX Warning: Hyper reference `ch:software-and-packaging' on page 11 undefined
on input line 720.
LaTeX Warning: Reference `ch:software-and-packaging' on page 11 undefined on in
put line 720.
LaTeX Warning: Hyper reference `ch:preferences-and-hardware' on page 11 undefin
ed on input line 741.
LaTeX Warning: Reference `ch:preferences-and-hardware' on page 11 undefined on
input line 741.
LaTeX Warning: Hyper reference `ch:preferences-and-hardware' on page 11 undefin
ed on input line 741.
LaTeX Warning: Reference `ch:preferences-and-hardware' on page 11 undefined on
input line 741.
Overfull \hbox (0.831pt too wide) in paragraph at lines 732--742
\EU1/GentiumBookBasic(0)/m/sc/10 The system menu, located on the top panel, con
tains two important sub-menus. Those sub-menus,
[11] [12] [13] [14] [15] [16] [17]
Kapitel 3.
! Undefined control sequence.
l.1021 einen \textbf{WLAN-Router} oder \texbf
{Accesspoint} gekauft und einge...
?
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 523578] [NEW] Arabic translation fails to compile
Public bug reported: When I run "make ubuntu-manual-ar.pdf", the compilation fails: ! Incomplete \iffalse; all text was ignored after line 111. \fi l.111 ** Affects: ubuntu-manual Importance: Undecided Assignee: Kevin Godby (godbyk) Status: New -- Arabic translation fails to compile https://bugs.launchpad.net/bugs/523578 You received this bug notification because you are a member of Ubuntu Manual Team, which is subscribed to Ubuntu Manual. Status in Ubuntu Manual: New Bug description: When I run "make ubuntu-manual-ar.pdf", the compilation fails: ! Incomplete \iffalse; all text was ignored after line 111. \fi l.111 ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 523578] Re: Arabic translation fails to compile
** Attachment added: "ubuntu-manual-ar.log" http://launchpadlibrarian.net/39337853/ubuntu-manual-ar.log -- Arabic translation fails to compile https://bugs.launchpad.net/bugs/523578 You received this bug notification because you are a member of Ubuntu Manual Team, which is subscribed to Ubuntu Manual. Status in Ubuntu Manual: New Bug description: When I run "make ubuntu-manual-ar.pdf", the compilation fails: ! Incomplete \iffalse; all text was ignored after line 111. \fi l.111 ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] Bengali translation
Hello. If anyone on this list is helping with the Bengali translation, could you send me an email please? I have a few questions that I need answered so that the Bengali translation will compile. Thanks! --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Bengali translation
Hello. On Sat, Feb 20, 2010 at 8:01 AM, Nasir Khan Saikat wrote: > Kevin , > I am working as a Bengali translator and i know some people who are working > in this project. Most of them are enlisted here. So i think you can ask your > question here. Fair enough; here goes: First, I wanted to thank you for helping translate the Ubuntu Manual into Bengali. I'm working on the LaTeX code that's used to compile the manual. Unfortunately, the language package we use doesn't include an Bengali module. Fortunately, I can create one fairly easily with your help. The language modules contain the translations of a few simple words, handle the printing of dates, and a few other minor typographic details. Could you translate the following words to Bengali for me? 1. "Preface" -- the name of the introductory chapter of a book. 2. "References" -- the heading of a list of references or a bibliography at the end of a book. 3. "Abstract" -- the heading of an abstract or executive summary of a document. 4. "Bibliography" -- the heading of a list of references or a bibliography at the end of a research article. 5. "Chapter" -- used in the heading of a chapter (for example, "Chapter 1. In the Beginning") or in reference to a chapter (for example, "see Chapter 1 for more information"). 6. "Appendix" -- similar to Chapter, but for appendices. 7. "Contents" -- the heading of the table of contents at the beginning of a book. 8. "List of Figures" -- the heading of the list of figures at the beginning of a book. 9. "List of Tables" -- the heading of the list of tables at the beginning of a book. 10. "Index" -- the heading of the index at the back of a book. 11. "Figure" -- used in the captions figures/images (e.g., "Figure 2: An apple"). 12. "Table" -- used in the captions of tables (e.g., "Table 3: Lemonade sales"). 13. "Part" -- the heading of a section of the book (e.g., "Part IV: Linux Conquers the World"). 14. "encl" -- abbreviation of "enclosure" or "enclosures"; used at the bottom of business letters to indicate that additional pages were sent with the letter. 15. "cc" -- abbreviation of "carbon copy"; used in letters and memos to indicate additional recipients. 16. "To" -- used in letters and memos to indicate the primary recipient. 17. "Page" -- used in reference to a specific page of a book (e.g., "See page 37 for more details."). 18. "see" -- used in the index of a book to redirect the reader to a different index entry (e.g., "apples, see fruit"). 19. "see also" -- used in the index of a book to direct the reader to additional relevant entries (e.g., "apples, see also oranges"). 20. "Proof" -- introduces a mathematics proof. 21. "Glossary" -- the heading of a glossary (a list of words and their definitions) at the end of a book. I also need to know the format of the date that you prefer. In this case, I mean the 'long date' (e.g., "January 29, 2010"). What is the order of the day, month, and year? What punctuation is used? (If you use a non-Gregorian calendar, please let me know which calendar is used.) Also, I need a translation of each of the months: 1. January 2. February 3. March 4. April 5. May 6. June 7. July 8. August 9. September 10. October 11. November 12. December Are there any typographic peculiarities that you can think of? For instance, is there a space before a semicolon (;) or colon (:)? Does this language use a numbering system other than Arabic (i.e., other than 1, 2, 3, etc.)? I would like to contribute your translations back to the LaTeX language package (with credit to you, of course) so that others may benefit from them. The language modules are licensed under the LaTeX Project Public License (LPPL): http://www.latex-project.org/lppl.txt. May I have your permission to contribute your translations back to the LaTeX project under the LPPL? Finally, what typefaces do you recommend for setting the Ubuntu Manual in Bengali? If you have any questions, require more context or background on the words to be translated, or think I should ask someone else for help with this translation, please let me know. Thanks again for all your help! --Kevin Godby ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Slides for 48 hours
Hey, Josh. On Mon, Feb 22, 2010 at 2:07 AM, Josh Holland wrote: > Hi all, > > If you could all provide a link to a PDF of your slides, I can add them to > the iCal ready for this afternoon and tomorrow morning. I've uploaded the slides from my talk, Benjamin's talks, and Ilya's talk to my web site here: http://kevin.godby.org/ubuntu-manual/talks/ I've also linked those slides (and the handout for my talk) on the wiki: https://wiki.ubuntu.com/ubuntu-manual/48hours If you have any slides or handouts for your talk that you'd like me to host, just email them to me and I'll upload them to the same place. Thanks! --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Fonts to be used
Hello, Fabian. On Mon, Feb 22, 2010 at 7:59 AM, Fabian Rodriguez wrote: > Thorsten Wilms wrote: >> On Wed, 2010-02-17 at 22:14 +0100, Thorsten Wilms wrote: >> >>> https://wiki.ubuntu.com/ubuntu-manual/Artwork?action=AttachFile&do=view&target=font_test_sans_converted.pdf >>> https://wiki.ubuntu.com/ubuntu-manual/Artwork?action=AttachFile&do=view&target=font_test_serif_converted.pdf >> >> Kevin Godby and I went through the fonts. We looked at individual letter >> forms, kerning, glyph coverage and style (not too stiff, but not funky, >> either). We settled on Biolinum (sans 4) and Libertine (serif 5). 2nd >> choices might have been Charis SIL and Gillius ADF No2. > > What specific licenses cover such fonts ? It will be important when > releasing the manual for free distribution to have freely-licensed fonts > and make this licensing clear, while providing direct links to the > appropriate files/packages so the manual toolchain remains free too. The fonts we chose are dual-licensed under GPL (with the font exception) and the OFL. The website for the fonts is: http://linuxlibertine.sourceforge.net/ --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 525799] Re: where is siunitx.sty ?
The siunitx package is only included in TeX Live 2009, so you'll have to
install that.
I've written some installation instructions in the last chapter of this
PDF document:
http://kevin.godby.org/ubuntu-manual/talks/latex-handout.pdf
--
where is siunitx.sty ?
https://bugs.launchpad.net/bugs/525799
You received this bug notification because you are a member of Ubuntu
Manual Team, which is subscribed to Ubuntu Manual.
Status in Ubuntu Manual: New
Bug description:
~/SVN/Bazaar/ubuntu-manual/pkgs$ ./install-pkgs.sh
Checking xcolor TeX package...installed!
Checking beramono TeX package...installed!
Checking mathpazo TeX package...installed!
Checking book TeX package...installed!
Checking titlesec TeX package...installed!
Checking microtype TeX package...installed!
Checking ifxetex TeX package...installed!
Checking inkscape Ubuntu package...installed.
Checking ttf-sil-gentium Ubuntu package...installed.
Checking ttf-sil-gentium-basic Ubuntu package...installed.
Checking ttf-dejavu Ubuntu package...installed.
Checking ttf-dejavu-core Ubuntu package...installed.
Checking ttf-dejavu-extra Ubuntu package...installed.
Checking installed Ubuntu packages...
Required Ubuntu packages are already installed.
Checking ccicons TeX package...installed!
Done! You should now be able to compile the Ubuntu manual!
but :
~/SVN/Bazaar/ubuntu-manual$ make
bzr version-info --custom --template="Revision number: {revno}\qquad Revision
date: {date}\n\n" > revision.tex
pdflatex main
This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)
%&-line parsing enabled.
entering extended mode
(./main.tex
LaTeX2e <2005/12/01>
Babel and hyphenation patterns for english, usenglishmax, dumylang, noh
yphenation, basque, french, loaded.
(./ubuntu-manual.cls
Document Class: ubuntu-manual 2010/01/12 v0.0.9 Ubuntu manual document class
(/usr/share/texmf-texlive/tex/latex/xkeyval/xkeyval.sty
.
.
.
*hyperref using default driver hpdftex*
(/usr/share/texmf-texlive/tex/latex/hyperref/hpdftex.def)
! LaTeX Error: File `siunitx.sty' not found.
And can't find this file anywhere in ubuntu distrib...
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 525799] Re: where is siunitx.sty ?
** Changed in: ubuntu-manual
Assignee: (unassigned) => Kevin Godby (godbyk)
--
where is siunitx.sty ?
https://bugs.launchpad.net/bugs/525799
You received this bug notification because you are a member of Ubuntu
Manual Team, which is subscribed to Ubuntu Manual.
Status in Ubuntu Manual: New
Bug description:
~/SVN/Bazaar/ubuntu-manual/pkgs$ ./install-pkgs.sh
Checking xcolor TeX package...installed!
Checking beramono TeX package...installed!
Checking mathpazo TeX package...installed!
Checking book TeX package...installed!
Checking titlesec TeX package...installed!
Checking microtype TeX package...installed!
Checking ifxetex TeX package...installed!
Checking inkscape Ubuntu package...installed.
Checking ttf-sil-gentium Ubuntu package...installed.
Checking ttf-sil-gentium-basic Ubuntu package...installed.
Checking ttf-dejavu Ubuntu package...installed.
Checking ttf-dejavu-core Ubuntu package...installed.
Checking ttf-dejavu-extra Ubuntu package...installed.
Checking installed Ubuntu packages...
Required Ubuntu packages are already installed.
Checking ccicons TeX package...installed!
Done! You should now be able to compile the Ubuntu manual!
but :
~/SVN/Bazaar/ubuntu-manual$ make
bzr version-info --custom --template="Revision number: {revno}\qquad Revision
date: {date}\n\n" > revision.tex
pdflatex main
This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)
%&-line parsing enabled.
entering extended mode
(./main.tex
LaTeX2e <2005/12/01>
Babel and hyphenation patterns for english, usenglishmax, dumylang, noh
yphenation, basque, french, loaded.
(./ubuntu-manual.cls
Document Class: ubuntu-manual 2010/01/12 v0.0.9 Ubuntu manual document class
(/usr/share/texmf-texlive/tex/latex/xkeyval/xkeyval.sty
.
.
.
*hyperref using default driver hpdftex*
(/usr/share/texmf-texlive/tex/latex/hyperref/hpdftex.def)
! LaTeX Error: File `siunitx.sty' not found.
And can't find this file anywhere in ubuntu distrib...
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 525799] Re: where is siunitx.sty ?
Yes, it's required. The polyglossia package requires a later version of
xelatex than what comes with TeX Live 2007. (I tried your method first
-- downloading the individual packages that we needed. Unfortunately,
the xelatex version requirement got in the way.)
The tipa package is currently being used only because someone copied the
pronunciation of GNOME (or somesuch) from Wikipedia into the manual.
Once we switch the default English version of the document over to
compile with xelatex, we'll get the IPA characters for free from our
fonts. (The tipa package is not required by xelatex, only latex.) So
the tipa requirement will be going away soon.
--
where is siunitx.sty ?
https://bugs.launchpad.net/bugs/525799
You received this bug notification because you are a member of Ubuntu
Manual Team, which is subscribed to Ubuntu Manual.
Status in Ubuntu Manual: New
Bug description:
~/SVN/Bazaar/ubuntu-manual/pkgs$ ./install-pkgs.sh
Checking xcolor TeX package...installed!
Checking beramono TeX package...installed!
Checking mathpazo TeX package...installed!
Checking book TeX package...installed!
Checking titlesec TeX package...installed!
Checking microtype TeX package...installed!
Checking ifxetex TeX package...installed!
Checking inkscape Ubuntu package...installed.
Checking ttf-sil-gentium Ubuntu package...installed.
Checking ttf-sil-gentium-basic Ubuntu package...installed.
Checking ttf-dejavu Ubuntu package...installed.
Checking ttf-dejavu-core Ubuntu package...installed.
Checking ttf-dejavu-extra Ubuntu package...installed.
Checking installed Ubuntu packages...
Required Ubuntu packages are already installed.
Checking ccicons TeX package...installed!
Done! You should now be able to compile the Ubuntu manual!
but :
~/SVN/Bazaar/ubuntu-manual$ make
bzr version-info --custom --template="Revision number: {revno}\qquad Revision
date: {date}\n\n" > revision.tex
pdflatex main
This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)
%&-line parsing enabled.
entering extended mode
(./main.tex
LaTeX2e <2005/12/01>
Babel and hyphenation patterns for english, usenglishmax, dumylang, noh
yphenation, basque, french, loaded.
(./ubuntu-manual.cls
Document Class: ubuntu-manual 2010/01/12 v0.0.9 Ubuntu manual document class
(/usr/share/texmf-texlive/tex/latex/xkeyval/xkeyval.sty
.
.
.
*hyperref using default driver hpdftex*
(/usr/share/texmf-texlive/tex/latex/hyperref/hpdftex.def)
! LaTeX Error: File `siunitx.sty' not found.
And can't find this file anywhere in ubuntu distrib...
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 525799] Re: where is siunitx.sty ?
I've updated the install-pkgs.sh script (located in the ubuntu-
manual/pkgs/ directory). It will check to see that you have the proper
version of TeX Live installed and also install any missing packages
(both TeX and Ubuntu) and fonts.
Please let me know if you run into any problems with the script. (I
haven't tested it thoroughly yet.)
--
where is siunitx.sty ?
https://bugs.launchpad.net/bugs/525799
You received this bug notification because you are a member of Ubuntu
Manual Team, which is subscribed to Ubuntu Manual.
Status in Ubuntu Manual: In Progress
Bug description:
~/SVN/Bazaar/ubuntu-manual/pkgs$ ./install-pkgs.sh
Checking xcolor TeX package...installed!
Checking beramono TeX package...installed!
Checking mathpazo TeX package...installed!
Checking book TeX package...installed!
Checking titlesec TeX package...installed!
Checking microtype TeX package...installed!
Checking ifxetex TeX package...installed!
Checking inkscape Ubuntu package...installed.
Checking ttf-sil-gentium Ubuntu package...installed.
Checking ttf-sil-gentium-basic Ubuntu package...installed.
Checking ttf-dejavu Ubuntu package...installed.
Checking ttf-dejavu-core Ubuntu package...installed.
Checking ttf-dejavu-extra Ubuntu package...installed.
Checking installed Ubuntu packages...
Required Ubuntu packages are already installed.
Checking ccicons TeX package...installed!
Done! You should now be able to compile the Ubuntu manual!
but :
~/SVN/Bazaar/ubuntu-manual$ make
bzr version-info --custom --template="Revision number: {revno}\qquad Revision
date: {date}\n\n" > revision.tex
pdflatex main
This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)
%&-line parsing enabled.
entering extended mode
(./main.tex
LaTeX2e <2005/12/01>
Babel and hyphenation patterns for english, usenglishmax, dumylang, noh
yphenation, basque, french, loaded.
(./ubuntu-manual.cls
Document Class: ubuntu-manual 2010/01/12 v0.0.9 Ubuntu manual document class
(/usr/share/texmf-texlive/tex/latex/xkeyval/xkeyval.sty
.
.
.
*hyperref using default driver hpdftex*
(/usr/share/texmf-texlive/tex/latex/hyperref/hpdftex.def)
! LaTeX Error: File `siunitx.sty' not found.
And can't find this file anywhere in ubuntu distrib...
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 522900] Re: Compiling in German gives the following error
** Changed in: ubuntu-manual
Status: Fix Committed => Fix Released
--
Compiling in German gives the following error
https://bugs.launchpad.net/bugs/522900
You received this bug notification because you are a member of Ubuntu
Manual Team, which is subscribed to Ubuntu Manual.
Status in Ubuntu Manual: Fix Released
Bug description:
Compiles fine up to here. The last error is easy to fix but I have no clue how
to fix it in german, it should read \textbf not \texbf.
Package Fancyhdr Warning: \fancyhead's `E' option without twoside option is use
less on input line 280.
(/usr/share/texmf-texlive/tex/latex/titlesec/block.tss))
LaTeX Warning: Unused global option(s):
[lang=de,german].
No file ubuntu-manual-de.aux.
(/usr/share/texmf/tex/latex/tipa/t3cmr.fd)
*geometry detected driver: pdftex*
ABD: EveryShipout initializing macros
(/usr/share/texmf-texlive/tex/latex/hyperref/nameref.sty
(/usr/share/texmf-texlive/tex/latex/oberdiek/refcount.sty))
Package hyperref Warning: Rerun to get /PageLabels entry.
[1]
(/home/luke-jennings/texmf/tex/latex/ccicons/uccicons.fd)
LaTeX Warning: Reference `ch:license' on page i undefined on input line 31.
[1] [2]
Overfull \hbox (20.44525pt too wide) in paragraph at lines 84--88
\EU1/GentiumBookBasic(0)/m/n/10 Dieses Handbuch soll kein umfassendes Ubuntu-Un
terrichtsbuch sein. Es stellt mehr eine Schnellstart-
LaTeX Warning: Hyper reference `ch:learning-more' on page iii undefined on inpu
t line 95.
LaTeX Warning: Reference `ch:learning-more' on page iii undefined on input line
95.
LaTeX Warning: Hyper reference `ch:learning-more' on page iii undefined on inpu
t line 95.
LaTeX Warning: Reference `ch:learning-more' on page iii undefined on input line
95.
[3] [4]
LaTeX Warning: Hyper reference `ch:around-your-desktop' on page v undefined on
input line 205.
LaTeX Warning: Reference `ch:around-your-desktop' on page v undefined on input
line 205.
LaTeX Warning: Hyper reference `ch:around-your-desktop' on page v undefined on
input line 205.
LaTeX Warning: Reference `ch:around-your-desktop' on page v undefined on input
line 205.
[5]
LaTeX Warning: Hyper reference `ch:installation' on page vi undefined on input
line 240.
LaTeX Warning: Reference `ch:installation' on page vi undefined on input line 2
40.
LaTeX Warning: Hyper reference `ch:installation' on page vi undefined on input
line 240.
LaTeX Warning: Reference `ch:installation' on page vi undefined on input line 2
40.
Overfull \hbox (15.50873pt too wide) in paragraph at lines 242--251
\EU1/GentiumBookBasic(0)/m/sc/10 Wenn Sie gerne ältere Spiele spielen, können
Sie bestimmte beliebte Spiele unter einem Windows-
[6] [1]
Kapitel 1.
Overfull \hbox (27.73041pt too wide) in paragraph at lines 316--324
\EU1/GentiumBookBasic(0)/m/sc/10 Arbeitsspeicher Ihres Rechners, wird sich dabe
i aber etwas zäh anfühlen (da die CD-Lesegeschwindigkeit
[2] [3] [4] [5] [6] [7]
Kapitel 2.
[8] [9]
LaTeX Warning: Hyper reference `ch:default-applications' on page 10 undefined o
n input line 686.
LaTeX Warning: Reference `ch:default-applications' on page 10 undefined on inpu
t line 686.
LaTeX Warning: Hyper reference `ch:default-applications' on page 10 undefined o
n input line 686.
LaTeX Warning: Reference `ch:default-applications' on page 10 undefined on inpu
t line 686.
[10]
LaTeX Warning: Hyper reference `ch:software-and-packaging' on page 11 undefined
on input line 720.
LaTeX Warning: Reference `ch:software-and-packaging' on page 11 undefined on in
put line 720.
LaTeX Warning: Hyper reference `ch:software-and-packaging' on page 11 undefined
on input line 720.
LaTeX Warning: Reference `ch:software-and-packaging' on page 11 undefined on in
put line 720.
LaTeX Warning: Hyper reference `ch:preferences-and-hardware' on page 11 undefin
ed on input line 741.
LaTeX Warning: Reference `ch:preferences-and-hardware' on page 11 undefined on
input line 741.
LaTeX Warning: Hyper reference `ch:preferences-and-hardware' on page 11 undefin
ed on input line 741.
LaTeX Warning: Reference `ch:preferences-and-hardware' on page 11 undefined on
input line 741.
Overfull \hbox (0.831pt too wide) in paragraph at lines 732--742
\EU1/GentiumBookBasic(0)/m/sc/10 The system menu, located on the top panel, con
tains two important sub-menus. Those sub-menus,
[11] [12] [13] [14] [15] [16] [17]
Kapitel 3.
! Undefined control sequence.
l.1021 einen \textbf{WLAN-Router} oder \texbf
{Accesspoint} gekauft und einge...
?
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 522356] Re: LaTex-Formatting-Bug
** Changed in: ubuntu-manual
Status: Fix Committed => Fix Released
--
LaTex-Formatting-Bug
https://bugs.launchpad.net/bugs/522356
You received this bug notification because you are a member of Ubuntu
Manual Team, which is subscribed to Ubuntu Manual.
Status in Ubuntu Manual: Fix Released
Bug description:
There's a formatting-mistake in the Alpha-Release of the Manual (I think so).
While I were translating the chapter about configuring a wireless network, I
found here
(https://translations.launchpad.net/ubuntu-manual/main/+pots/ubuntu-manual/de/220/+translate)
the phrase {IPv4 Settings}, while I think it should be \textbf{IPv4 Setting}.
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] New code
Hey, everyone . I've recently been working on some new code to help simplify things a bit. First, I've updated the install-pkgs.sh script. It now tries to detect which version of LaTeX you have installed and will either tell you to upgrade (if the version is too old), or check to make sure you have all the required packages to compile the manual (if your version is up to date). I haven't tested it extensively yet, so let me know if you have any problems with it. You can find the script in the pkgs/ subdirectory. Second, I've updated the Makefile so that it tries to detect your current language and compile the appropriate translation for you. Run 'make mylang' to test it out. I haven't tested this extensively yet, either, so again, let me know if you run into problems. I've also added a 'Make Translated PDF' button to the Ground Control config files. This will appear if you have Ground Control installed and open up the ubuntu-manual directory in Nautlius. This new button will compile the right PDF and display it using Evince. Once again, let me know if you encounter problems with these scripts or if you have any other ideas on how I can make it easier for your to do your work. Thanks! --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] New code
Hey, Martin. 2010/2/24 Martin Lukeš : > Great work! I could finally compile "my" manual. ;) > > My feedback: > Text on https://wiki.ubuntu.com/ubuntu-manual/Prerequisites is a little bit > fuzzy I think. Maybe its me but part 6 and 7 took me at least ten minutes to > understand. ;) Not to mention that part >> >> I highly recommend enabling the "create symlinks to standard directories" >> option. > > I read AFTER I installed TexLive and ran install-pkgs.sh script. Good point! I'll write some more detail about which options should be selected during the TeX Live installation. > As for "Make Translated PDF" button: > I find it very useful. Perhaps it should be slightly more automated. I mean > when it want me to press Enter key about twenty-times. (I was confused about > what to do when it first asked me, so I instinctively press Enter key. :D ) > I think that just detail is that it does not open in Evince. It doesn't > opened at all. ;) > BTW, log file is attached if it helps. It looks like you're missing some required TeX packages. While the install-pkgs.sh script installs the packages we directly depend on, it doesn't install the packages that those packages depend on! I've fixed this in the latest version. Please re-run the install-pkgs.sh script and see if it installs the missing packages. Once you have the missing packages installed, it should run without you having to press Enter, and it'll load the PDF at the end. --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] New code
Hey, Ben. On Wed, Feb 24, 2010 at 8:28 PM, Ben <6180339g...@gmail.com> wrote: > Hi, > > I installed TexLive 2009 and ran your script, but I'm getting this error > about 'xmpincl.sty' not being findable. I was able to find a copy of it > online, but I still got an error (attached). Whoops, I forgot that package. (We're not actually using it yet, but it's still required to compile the doc, at the moment.) I've updated install-pkgs.sh (again), so please pull down the latest version and run the install-pkgs.sh script again. Then you can try to compile the PDF. Let me know if you have any further problems. Thanks! --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] New code
'allo. On Wed, Feb 24, 2010 at 9:01 PM, Ben <6180339g...@gmail.com> wrote: > I was wondering a bit about that ... I checked, but couldn't find the > 'xmpincl' bit in any Ubuntu packages other than a generic texlive one, which > was probably the old version. > It appears that Launchpad didn't pick up your change, so I edited the script > as you suggested and tried it again, but it still didn't work. However, I'm > wondering if that's something with my TexLive install (I tried a couple > different installs with some ^C in between :) ), so I'm reinstalling > following your updated wiki instructions and will try again shortly. Oh, man, I'm having a horrible day. I should just step away from the computer. :-) I committed, but didn't push the changes. I just pushed, so it should appear in the branch soon. --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] New code
On Wed, Feb 24, 2010 at 9:28 PM, Ben <6180339g...@gmail.com> wrote: > That's OK ... I know the feeling :) > Unfortunately, I still got an error (re above: I typed "area" instead of > "error" ... :) ), but I haven't finished that reinstall - the download > keeps giving up halfway through for me, so I have to restart several times. > Oh well. > Due to sleep/school/work, I won't be back for about 20 hours or thereabouts, > but I'll update you then. Yeah, it looks like tlmgr is complaining: Fundamental package texlive.infra not present, uh oh, goodbye Serious error, texlive.infra not found at /usr/local/bin/tlmgr line 4145. When you finish reinstalling TeX Live, try the script again and see what happens. --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] New code
Hello, Martin. 2010/2/25 Martin Lukeš : > I don't know if I'm not late. ;) > I ran new install-pkgs.sh and it installed some packages, but "Make > Translated PDF" still wants three-times press Enter and Evince still doesn't > open. > But as it was before - compiled .pdf seems fine with no errors. > And again .log files are attached. Thanks for reporting this bug. You were missing some fonts (for the dingbats). I've added those fonts to the prerequisites list in the install-pkgs.sh script now, so you should run the latest version and see if that fixes everything. Thanks! --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] New code
Hello, Jamin. 2010/2/25 Jamin Day : > I'm also having issues compiling the pdf through Ground Control. > I followed the instructions on the wiki to remove all previous texlive > packages and install texlive 2009. I'm using English only so didn't install > any language or documentation packs. Then running ./install-pkgs.sh in the > pkgs folder tells me that everything is installed and I should be able to > compile. > However when I press 'Make PDF' in Ground Control, I have to press enter > numerous times then nothing happens - no evince and no pdf appears in the > folder either. > I've attached main.log for reference - not sure if there's any other logs > that would be helpful. Thanks for reporting this bug. You were missing some fonts. I've added those fonts to the prerequisites list in the install-pkgs.sh script now, so you should run the latest version and see if that fixes everything. Thanks! --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] New code
Hello, Ben. On Thu, Feb 25, 2010 at 8:07 PM, Ben <6180339g...@gmail.com> wrote: > Well, I tried reinstalling and re-running your script. Both processes were > happy until I attempted a 'make show', when it complained about beramono and > libertine (I think ... logs attached). Thanks for reporting this bug. You were missing some fonts. I've added those fonts to the prerequisites list in the install-pkgs.sh script now, so you should run the latest version and see if that fixes everything. Thanks! --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Getting going and hit a speed bump, LaTex 2009 install and install_pkgs.sh
Hello, Maia. On Thu, Feb 25, 2010 at 2:34 PM, maia grotepass wrote: > I am trying to get the environment sorted to work on this project and I am > having a few problems. I have a relatively clean Karmic install and I > didn't have any Tex version installed. I followed the instructions on the > Help page on the wiki and Prerequisites page. I installed groundcontrol and > got the files for the project. I tried running the install_pkgs.sh and it > said it didn't see an TexLive installation. I did not uninstall TexLive > because I hadn't installed it before. I then installed TexLive2009 as per > the instructions. I added the path to the TexLive bins as per the TexLive > web page, opened a new terminal window, checked the path was setup and reran > install_pkgs.sh. It still says the following. No version of TeX Live was > detected. The log file says the same. > I then tried to read the script to see what it was looking for and I see it > does a dpkg-query to find the texlive-base version. I then checked my > packages and as expected I do not have texlive-base because I never > installed it using synaptic/apt, I installed texlive2009 from the script. > Make PDF button works after a fashion except it says it substitutes defaults > for the places where it is missing things. This proves that at least I have > the tools installed ok to make the PDF. > What am I missing? If I had a tail I'd chase it a little longer and then > possibly wander off. > Let me know if/which logfiles would help. > Maia Could you try the latest install-pkgs.sh script? (It looks like you had a different problem than the others, so I'm not expecting it to work, but one never knows.) If it fails again, send me the install-pkgs.log file and also the log file for the manual (either main.log if you're compiling the English version, or the ubuntu-manual-XX.log if you're compiling for another language). Thanks! --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] New code
Hey, Ben. On Thu, Feb 25, 2010 at 10:24 PM, Ben <6180339g...@gmail.com> wrote: > Hopefully I haven't gotten too annoying ... :) Nah, we're just working out all the kinks in the script. > FYI, I had to manually install ccicons, following the readme ... and it > still didn't work. It's finding the ccicons files, but it's also finding the old font mapping file (pre-2009). So we'll need to remove that. Have you installed anything in ~/texmf yourself? If not, you can safely remove that entire directory tree. Before I made everyone upgrade to TL2009, I had them install the ccicons package to ~/texmf (using an older incarnation of the install-pkgs.sh script). Some of these old files are interfering with the TL2009 stuff. After you've removed the ~/texmf directory, rerun the install-pkgs.sh script (just to doublecheck that everything's okay) and then run 'make' again and see what happens. --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Feedback for 48 hours
On Thu, Feb 25, 2010 at 3:56 PM, Benjamin Humphrey wrote:
> Hi guys,
> So as most of you should know, not only was 48 hours a chance for us to
> actually get some stuff done and teach new people about the manual project,
> but it was also a chance to test out some new stuff, like ClassBot, Lernid,
> Ground Control etc.
> I've told the heads of these projects that I'd get some feedback from our
> team, both the teachers and the students, and then email a summary to them.
> So, if anyone has any bugs, feature requests, questions or anything to do
> with Lernid, ClassBot or Ground Control, please reply to this thread with
> your feedback and I'll make sure it gets to the right place!
Random tidbits that come to mind:
1. Upon starting Lernid, the IRC and slide panes were collapsed. All
the panes should start opened a bit (or make it simple and let them
each have a quarter of the screen initially).
2. The Edit > Preferences menu option does nothing.
3. When regard to the [SLIDE 1] commands provided by the instructor:
It'd be nice if there were a [SLIDE NEXT] and [SLIDE PREVIOUS] so I
don't have to keep track of which slide number I'm on.
4. I agree with Josh about the question queue. I had set up an alert
in xchat to ding when someone said QUESTION in the -chat room. But
even better would be if the bot parsed those for me and presented them
in a private chat to me as they came in.
5. Along with setting the channel topic and giving voice to the
instructor, it may be helpful for it to say [SLIDE 1] automatically to
start the slide presentation. This would've saved us a bit of grief.
6. It looked like my slides in Lernid were blurry, but others' looked
fine. Not sure why that was. (I generated mine with XeLaTeX and the
others came from OOo, I think. But beyond that, I don't know what the
differences are.)
7. Might be nice for the classbot to give voice to the upcoming
speaker about 5 minutes before their session is scheduled to start.
Just to ease the transition and reduce anxiety ("Will this thing
work?").
8. Could be handy if the bot privately messaged me when my time is
almost up, too, so I can make sure to wrap things up on time.
Probably a bit of feature creep, but I don't think it'd be too
obtrusive.
9. There was some confusion in -chat as to whether one's question had
been recognized. Perhaps there could be some feedback on that.
10. If I remember correctly, the text color in Lernid was light grey
on white. I'm not sure if this is due to my theme or what, but the low
contrast made it difficult to read.
That's all that comes to mind at the moment.
--Kevin
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Edition?
Here's some background on how the publishing history information typically works in books. The publishing history is included on the copyright page of the book. The following information is taken from the Chicago Manual of Style: ``Publishing History. The publishing history of a book, which usually follows the copyright notice, begins with the date (year) of original publication. If a book is reprinted, the number and date of the current impression are usually indicated. Corrections are sometimes made in new impressions, but if significant revisions are made, the result may be a new edition. The number and date of the new edition become part of the publishing history. The copyright dates of all editions may be accumulated in the copyright notice, but usually only the original edition and latest editions are reflected in the publishing history. ``Edition versus impression. `Edition,' as opposed to 'impression,' is used in at least two senses. (1) A new edition may be defined as one in which a substantial change has been made in one or more of the essential elements of the work (e.g., text, notes, appendixes, or illustrations). As a rule of thumb, at least 20 percent of a new edition should consist of new or revised material. A work that is republished with a new preface or afterward but is otherwise unchanged except for corrections of typographical errors is better described as a new impression or a reissue; the title page may include such words as `With a New Preface.' (2) `Edition' may be used to designate a reissue in a new format---for example, a paperback, deluxe, or illustrated version---or under the imprint of a different publisher. ``Edition number. A new edition is best designated on the title page by its number: Second Edition, Third Edition, and so forth. Such phrases as `revised and expanded' are redundant on the title page, since the nature and extent of the revision are normally described in the prefatory material or on the cover. ``Impression. The impression is usually identified by a line of numerals running below the publishing history. For example: 07 06 05 040 03 02 01 991 2 3 4 5 The first group of numerals, reading from right to left, represents the last two digits of succeeding years starting with the date of original publication. The second set, following a space of an em or more and reading from left to right, represents the numbers of possible new impressions. The lowest number in each group indicates the present impression and date. In the above example, therefore, the impression is identified as the first, and the year of printing as 1999. The following example indicates a sixth printing in 1998. 04 03 02 01 00 99 98 6 7 8 9 This method involves minimal resetting in each new impression, since the typesetter merely deletes the lowest number. Indicating a new impression not only reflects the sales record of a book but also signals that corrections may have been made.'' --- Whew! Okay, so the basic concept are that there are two levels of revisions of a book: editions and impressions. An impression is just for fixing minor typos while a new edition indicates more substantial changes. I would say that Getting Started with Ubuntu 10.04 is the first book in a series of books. The series would contain the following books: Getting Started with Ubuntu 10.04 Getting Started with Ubuntu 10.10 Getting Started with Ubuntu 11.04 Getting Started with Ubuntu 11.10 etc. When we release Getting Started with Ubuntu 10.04 in April, that will be the first edition (and first impression/printing) of the book. We don't need to indicate this on the title page. Ideally, we won't need multiple editions or impressions. However, since we'll probably find typos after April or programs have changed a bit, we'll want to keep the manual up to date, and that will require new impressions. I think that information about new impressions can be safely relegated to the copyright page -- a notice shouldn't be placed on the front cover. If we make major revisions to the manual -- add a new chapter, for instance -- then that may qualify as a new edition. If this occurs, then we should place a 'Second Edition' notice on the cover of the manual. Now as to how this information should be presented on the copyright page: The reason they used the line of numbers (explained above) is because they used to generate metal plates for printing the books. When a new impression was created, it was easy to scratch off the year and impression from the existing copyright page plate and reuse it without making an entirely new plate. Since we're all electronic here, we don't have that problem. Further, very few people know what that line of numbers means anyway. Therefore, I would recommend that we use a versioning system similar to what's used for software, e.g., Version 1.1 for the first impression of the first edition. (The year is less important, given the timeliness of our m
[Ubuntu-manual] [Bug 525799] Re: where is siunitx.sty ?
** Changed in: ubuntu-manual
Status: In Progress => Fix Released
--
where is siunitx.sty ?
https://bugs.launchpad.net/bugs/525799
You received this bug notification because you are a member of Ubuntu
Manual Team, which is subscribed to Ubuntu Manual.
Status in Ubuntu Manual: Fix Released
Bug description:
~/SVN/Bazaar/ubuntu-manual/pkgs$ ./install-pkgs.sh
Checking xcolor TeX package...installed!
Checking beramono TeX package...installed!
Checking mathpazo TeX package...installed!
Checking book TeX package...installed!
Checking titlesec TeX package...installed!
Checking microtype TeX package...installed!
Checking ifxetex TeX package...installed!
Checking inkscape Ubuntu package...installed.
Checking ttf-sil-gentium Ubuntu package...installed.
Checking ttf-sil-gentium-basic Ubuntu package...installed.
Checking ttf-dejavu Ubuntu package...installed.
Checking ttf-dejavu-core Ubuntu package...installed.
Checking ttf-dejavu-extra Ubuntu package...installed.
Checking installed Ubuntu packages...
Required Ubuntu packages are already installed.
Checking ccicons TeX package...installed!
Done! You should now be able to compile the Ubuntu manual!
but :
~/SVN/Bazaar/ubuntu-manual$ make
bzr version-info --custom --template="Revision number: {revno}\qquad Revision
date: {date}\n\n" > revision.tex
pdflatex main
This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)
%&-line parsing enabled.
entering extended mode
(./main.tex
LaTeX2e <2005/12/01>
Babel and hyphenation patterns for english, usenglishmax, dumylang, noh
yphenation, basque, french, loaded.
(./ubuntu-manual.cls
Document Class: ubuntu-manual 2010/01/12 v0.0.9 Ubuntu manual document class
(/usr/share/texmf-texlive/tex/latex/xkeyval/xkeyval.sty
.
.
.
*hyperref using default driver hpdftex*
(/usr/share/texmf-texlive/tex/latex/hyperref/hpdftex.def)
! LaTeX Error: File `siunitx.sty' not found.
And can't find this file anywhere in ubuntu distrib...
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] License
Hello, Daniel. On Wed, Mar 3, 2010 at 9:32 AM, Daniel Schury wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hey everybody, > > would it be possible, to use a local copy of the license in the branch > instead of using launchpad for translation? Because the license already > _is_ translated in many languages and this translation should be used. > And it's easier than just copying the strings part by part into launchpad. Yes, for the cases where the license is already translated, we should use their translation. Unfortunately, there are a number of languages we're translating the manual into where the CC license hasn't yet been translated. So if the language you're translating into already has an appropriately translated license on the CC site, then you don't have to worry about translating the license. If you do need to translate the license, create a new license-LANGCODE.tex file and put the translation in there. I'll add LaTeX code elsewhere to pull in the language-appropriate license (or fall back on English otherwise). Thanks! --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] License
On Wed, Mar 3, 2010 at 9:50 AM, Daniel Schury wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > >> So if the language you're translating into already has an >> appropriately translated license on the CC site, then you don't have >> to worry about translating the license. >> >> If you do need to translate the license, create a new >> license-LANGCODE.tex file and put the translation in there. I'll add >> LaTeX code elsewhere to pull in the language-appropriate license (or >> fall back on English otherwise). > > So I just create the file license-de.tex in the main path und copy the > license into it, without any formatting, that's right? Create a license-de.tex file in the backmatter/ directory. And if you know how, you can format the license for LaTeX. (See the existing license.tex file for an example.) If you have any questions about the formatting, feel free to contact me. Thanks! --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] License
On Wed, Mar 3, 2010 at 10:17 AM, Daniel Schury wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Alright. Little LaTex-Question: the license uses enumeration this way:
> 1.a.i But the manual uses only \begin{enumeration} for the first and
> second layer, not the third. Wouldn't it be easier, to do so for the
> third too?
Yeah, I'd use the enumeration environment for each of 'em. I didn't
LaTeXify the first license (and haven't really looked at the code for
it). They may have done that if the third level uses a different
numbering type than they wanted. But don't fret if that's the case;
I'll just fix it so it works out in the end.
You can also use \label{item:short-description} after an \item. Then
later, reference that item with \ref{item:short-description}. It'll
be nicely hyperlinked.
--Kevin
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] License
On Wed, Mar 3, 2010 at 11:16 AM, Daniel Schury wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Do you see that something is labeled? Or: If I want to set a ref to 2.b,
> but not 2.a, would there be an optical difference between the both, so
> that I would have to label every enumeration?
Here's a quick example:
\begin{enumerate}
\item \label{item:apples} Apples
\begin{enumerate}
\item \label{item:braeburn} Braeburn
\item \label{item:macintosh} Macintosh
\item \label{item:red-delicious} Red Delicious
\end{enumerate}
\item \label{item:grapes} Grapes
\end{enumerate}
Elsewhere in text (or even in one of the enumeration environments), you can say:
I like apples (see \ref{item:apples}, especially \ref{item:braeburn}.
And it will print as:
I like apples (see 1), especially 1(a).
or similar.
You only have to \label the items you wish to reference in the text.
--Kevin
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] License
2010/3/3 Martin Lukeš : > Hi Kevin > I pushed Czech translation from > http://creativecommons.org/licenses/by-sa/3.0/cz/legalcode and I put it to > backmatter/ directory under name license-cs.tex > I also tried to do a bit of a LaTeX formating on it and as far as I could > see (thanks to "Make translated PDF" - great button) it looks fine. Great -- thanks! > If I may have a question... > Do you plan to edit "Make translated PDF" button so it will automatically > select appropriate license file? If not present, then it would use original > (English) file. Yes. As soon as Launchpad lets me push this code, it'll use the proper license file and fall back on English if it doesn't have a particular translation. > And second, but I don't know if it isn't more question for Josh. As if there > will be an extra .tex file for translated license then Roseta probably > shouldn't ask for its translation again. If this is doable of course. ;) I *think* that the way I've done it may hide the license text from the translation software so it won't know anything about it. I'm going to add a note to translators in the license.tex file. We'll see how it works soon. :-) --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] License
On Wed, Mar 3, 2010 at 10:23 PM, Ilya Haykinson wrote: > I recommend that we _never_ translate this license, since it's a binding > legal document and it is very easy to make a mistake in translation that > alters the entire meaning. If need be, I can email Lawrence Lessig and ask > for help in approving a translation, but instead I would prefer that we do > the following: > > - if a localized license is available, use it > - otherwise, use the US English version > > This should yield the most legally sound approach for now, and does not bind > us to any legal approval cycle in CC, or expose us to unnecessary risk of > creating a license that's too restrictive, too liberal, contradictory, or > just plain unenforceable. I don't mind having a translated license, but I do think there should be a notice at the top stating that it's an unofficial translation and that the binding license is the one located at . I think increasing the translations of the license is a good thing and we should try to work with CC on that if we have time. I think the biggest problem isn't the translation itself, but that they have to investigate the laws of each individual country and address the specifics there. --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] Glossary
Hello, all.
I've just added a glossary to the manual. You'll need to run the
pkgs/install-pkgs.sh script to make sure you have all the required
packages installed.
If you want to add entries to the glossary, add them in the
frontmatter/glossary-entries.tex file.
A glossary entry looks like this:
\newglossaryentry{label}{name={entry-name}, description={the
definition or description}}
The label should only contain Latin characters---that is, letters a-z
and an occasional hyphen (-). The name is the head word or the term
being defined. If the name starts with a non-Latin letter (that is, a
letter with an accent or from another script/language), put it in
braces ({}) by itself:
\newglossaryentry{elite}{name={é}lite, description={select group of people}}
If you leave out the braces, the glossary program will freak out and
things will break. (Scary, no?)
The description is the description or definition of the term.
For the translators, you can edit the name and description parts. If
you edit the label, you'll need to be sure to update it throughout the
document (otherwise the links won't work right).
Now, in the manual itself, when you want to link to a glossary entry,
you have a few commands at your disposal:
\gls{label} % inserts the name associated with and links it
to the glossary
\glspl{label} % inserts the plural name associated with the
and links it to the glossary
\Gls{label} % inserts the capitalized name associated with
and links it to the glossary. useful for the beginning of sentences
\Glspl{label} % take a wild guess
Examples:
\gls{elite} % élite
\glspl{elite} % élites
\Gls{elite} % Élite
\Glspl{elite} % Élite
If you have any questions, feel free to contact me. You can also read
the full docs on the glossary stuff by typing 'texdoc glossaries' at
the prompt.
--Kevin
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] Glossary and Index
Greetings! Since we have the glossary and index set up now, it would be a good idea if we had an editor or two to stick in charge of them. Instead of having everyone indexing their own chapters, I think it'd be better if we had one or two people dedicated to all of the indexing work. This will help keep things consistent. If anyone is interested in indexing the manual or writing glossary entries, please let me know and I'll help you get started. Thanks! --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Glossary
Hello, Daniel.
On Sun, Mar 7, 2010 at 4:12 PM, Daniel Schury wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Question about the plural Forms: Does it only add a "s" at the end?
By default it will append \glspluralsuffix to the value of the name
field. \glspluralsuffix defaults to 's' for English. If your language
forms most plurals by appending a different string, let me know and I
can add that definition to the language-specific code. If your
language uses a different mechanism for plurals, you can use the
plural field:
\newglossaryentry{goose}{name={goose},plural={geese},description={a
bird that supplies quills for writing}}
\gls{goose}% types 'goose'
\glspl{goose}% types 'geese'
--Kevin
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] "Translate" links?
'allo. On Sun, Mar 7, 2010 at 4:18 PM, Daniel Schury wrote: > I've got a question: Am I as a translator allowed, to change links from > original pages to appropiate pages in the translation-language? I don't know what the official word is on this, but it makes sense to me. The goal is that someone should pick up the manual and have the smoothest introduction to Ubuntu as possible, and that means having information in their language. But that's just my opinion. --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] Translators: A note about the \SI command
Hello.
Just a quick notes to the translators about the \SI command. If your
language doesn't use the standard English-language SI unit names, then
remove the \SI command and replace it with plain text in your
language.
For example, \SI{3}{\giga\byte} would print "3 GB" in English. Free
free to translate this to whatever you like in your own language and
just leave out the \SI command (and syntax).
The purpose of the \SI command is to adjust the spacing between the
numbers and units. If you want to prevent a line break between the
numbers and units in your language use the tilde (~) instead of a
space. So "3~GB" would ensure that the GB stays with the 3 on the
same line (or moves both together to the next line).
I'm sorry I didn't make a note about this earlier. The \SI command
appears to be ignorant of other languages.
Thanks!
--Kevin
P.S. Also, please be careful not to translate the \then command. When
you see something like \menu{System\then About Ubuntu}, you may
translate "System" and "About Ubuntu", but leave \menu and \then
untranslated.
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Bizarre Bazaar Error
Hello, Bryan. On Sun, Mar 7, 2010 at 7:29 PM, Bryan Behrenshausen wrote: > Hi all, > > I'm trying to push my recent commits to Launchpad and am receiving this error: > > br...@bryan-aspire:~/Projects/ubuntu-manual$ bzr push lp:ubuntu-manual > bzr: ERROR: These branches have diverged. See "bzr help > diverged-branches" for more information. > > > What should I do? That means that someone (in this case me) has uploaded stuff to bzr between the time you committed your code and when you tried to push your code. If you run 'bzr merge', it will merge your code and my code. If there are no warnings about conflicts, you can run 'bzr commit' (to commit the merged code -- for the message, just note that you're merging with main branch), and then 'bzr push' should work. Let me know if you continue to have problems with it. --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] Ubuntu Manual on Ohloh
'allo. I added our project to Ohloh: https://www.ohloh.net/p/ubuntu-manual/ If you're a contributor to the project and have an Ohloh account (they're free), feel free to claim your name. You can also see interesting stats on the site such as how many commits each person has made, what computer languages we're writing in, and how many lines of code we've written. Enjoy! --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] Notes for translators
Hello. I've updated my LaTeX handout to include notes for translators (chapter 4) including what should and should not be translated. http://kevin.godby.org/ubuntu-manual/talks/latex.handout.pdf Please let me know if there are any questions, if I've missed anything, or if something could be made more clear. Thanks! --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Notes for translators
> On Wed, Mar 10, 2010 at 6:29 PM, Yann Ubuntu wrote: > Hi Kevin, your page gives a "404 - Page Not Found" error. Whoops! That's what I get for typing it by hand. Here's the correct link: http://kevin.godby.org/ubuntu-manual/talks/latex-handout.pdf --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 523578] Re: Arabic translation fails to compile
Fixed in the latest version of polyglossia. ** Changed in: ubuntu-manual Status: Confirmed => Fix Released -- Arabic translation fails to compile https://bugs.launchpad.net/bugs/523578 You received this bug notification because you are a member of Ubuntu Manual Team, which is subscribed to Ubuntu Manual. Status in Ubuntu Manual: Fix Released Bug description: When I run "make ubuntu-manual-ar.pdf", the compilation fails: ! Incomplete \iffalse; all text was ignored after line 111. \fi l.111 ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Wikipedia page!
On Sun, Mar 14, 2010 at 12:05 AM, Vishnoo wrote: > Hi , > I just want to mention that the team starting our own wikipedia page is > _not_ a good idea. > > The editors in the page are mostly only from our team , and it seems > like we are just doing it for our own ego boost. > > IMHO , wikipedia should be started by someone else in the world since we > are popular enough to deserve one, not because _we_ think we are > popular. > > If every team in Ubuntu which had large number of members , started a > wiki , it would become silly. > > Not trying to get into a debate , but Wikipedia should be useful for > others trying to find info , and not by the teams themselves to boost > their ego. In addition to what Vish said, Wikipedia considers it 'original research' if you're reporting on your own activities/projects/self, and that's not permitted. --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] Adding screenshots to the manual
Hello, all.
I took some of the screenshots that ubuntujenkins gave me (at 1024 x
768) and added them to the manual with the new \screenshot command.
You can take a look at the result:
http://kevin.godby.org/private/ubuntu-manual/ubuntu-manual.pdf
(See pages 24, 70, 76, 80, 88, and 94.)
I've got a few things to tidy up still, but it gives you the basic
idea of how they'll look.
Here's a bit about how to use the new \screenshot command.
\screenshot{screenshot-file.png}{ss:screenshot-label}{This is the
caption text for the screenshot.}
The first argument is the name of the screenshot graphic file (in PNG format).
The second argument is the label. The label should be prefixed with
"ss:" (for screenshot). This is used in cross-referencing. For
instance, "See screenshot \ref{ss:screenshot-label} for an example
screenshot." would produce: "See screenshot 2.3 for an example
screenshot." if it's the third screenshot in the second chapter. If we
end up cross-referencing screenshots a lot, I can make a
\screenshotlink command similar to the \chaplink command.
Finally, the third argument is the text that goes in the caption. The
caption should not just describe the screenshot itself, but tell the
user something about what they can do with the application depicted.
For instance, "The F-Spot main window." is a rather boring caption. A
slightly better caption would be: "F-Spot let's you store, tag, and
edit your photos." The screenshots will be eye-catching, so the
captions should invite the reader to learn more about the application
show.
For those who like to know how things work, here are some of the
behind-the-scenes details on the \screenshot command.
All of the screenshots are stored in the screenshots/LANG/ directory
(where LANG is the language code for your translation). LaTeX doesn't
really care about the resolution, but all the screenshots should be
taken at the same resolution so that they're scaled equally. The
screenshots in the example PDF linked above were taken at 1024 x 768.
The files can be named anything, but should not contain spaces or
funky characters.
To make sure that all of the screenshots are scaled equally, instead
of being stretched to fit the text width, we need to know what the
widest screenshot is. We use the \setmaxscreenshot command to point
to the filename of the widest screenshot (which would be 1024 pixels
wide, in this instance). The \setmaxscreenshot command takes that
screenshot and figures out what scaling factor must be used to get it
to fit onto the page (allowing the image to take up the main text
block width and the sidenote area width). This scaling factor is
stored and applied to all of the screenshots throughout the manual.
When the \screenshot command is called, LaTeX looks at the width of
the screenshot and scales it using the scaling factor. If the scaled
width is less than the main text block width, then we'll put the
screenshot in the text block area and put its caption alongside it in
the sidenote area. If the scaled width is greater than the text block
width, then we'll let the screenshot use the full text block width
plus the sidenote area width and put the caption below the screenshot.
--Kevin
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Spaces in keystrokes
For the keystrokes, use + as the separator and do not use spaces. Also, the key names should be capitalized. So it should be: Alt+Tab, Ctrl+N, Ctrl+Alt+Del, Enter, Shift, Esc, Backspace, Home, Ins, PgUp, PgDn, F1, etc. --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 550344] Re: Make appendix links use entire name as the link text
Good call. I've fixed this in r628. ** Changed in: ubuntu-manual Status: New => Fix Released -- Make appendix links use entire name as the link text https://bugs.launchpad.net/bugs/550344 You received this bug notification because you are a member of Ubuntu Manual Team, which is subscribed to Ubuntu Manual. Status in Ubuntu Manual: Fix Released Bug description: Currently, on page 3, the license is linked to in the sentence "To view a copy of this license, see Appendix A". However, only "A" is linked. I recommend changing so that the entire phrase "Appendix A" is a link, to make the clickable link target larger (see Fitt's Law) ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 544777] Re: No nomenclature at the start of the manual
** Changed in: ubuntu-manual Status: In Progress => Fix Released -- No nomenclature at the start of the manual https://bugs.launchpad.net/bugs/544777 You received this bug notification because you are a member of Ubuntu Manual Team, which is subscribed to Ubuntu Manual. Status in Ubuntu Manual: Fix Released Bug description: We need a way to show the reader what different types of formatting mean, ie, a "key." I suggest the best place for this is at the end of the prologue. ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] License
Excellent job, Ilya! Thanks for your help sorting this out. Are these the licenses we should be using (if there isn't a translation offered on the main license page)? http://creativecommons.org/international/ --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] License
Hey, Martin. >> Regarding bugs in the manual -- it's CC's policy that the published >> version is not changed (even for punctuation or factual errors). So the 1(f) >> reference that is clearly meant to be 1(h) will stay in the manual. They >> have a wiki where bugs are tracked -- if I get a link to that, I will make >> sure that this bug is reported there. > > Does this mean: Not even by releasing another edition of the same Manual > version? I assumed that Ilya meant "Regarding bugs in the license" not "manual". --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] which screenshots are needed
Hello, Dan. On Sun, Apr 4, 2010 at 6:28 PM, Dan 'Da Man' wrote: > Where can we check to see which screenshots in which language need to > be uploaded? You can check this site for a preliminary count: http://screenshots.ubuntu-manual.org/ Note that the screenshots haven't been proofread yet (checked for consistency and correctness), so some may need to be retaken. If you run Quickshot, it will download the list of screenshots still needed for the current language. --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] which screenshots are needed
Hello, Anup. On Sun, Apr 4, 2010 at 6:57 PM, Anup wrote: > how can i upload screen shots? You can upload screenshots using the Quckshot application: http://ubuntu-manual.org/quickshot --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] New style guide
Hello, everyone. I've started work on our new style guide. (I started with the LaTeX handout I created a while back and will be adding things to it as we go along.) I thought I'd mention it now as it contains a chapter that shows all the LaTeX commands we use and which parts should be (and should NOT be) translated. You can download a copy of the style guide from http://files.ubuntu-manual.org/style-guide.pdf. I will keep that URL updated as new content is added. If you have any questions, find any bugs, or would like to help with the style guide, please let me know. --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] Fwd: Follow up to Default Search Provider Changes for 10.04
It looks like the default search provider will be Google for 10.04 and not Yahoo as previously mentioned. What should we do RE: string freeze on this issue? --Kevin -- Forwarded message -- From: Rick Spencer Date: Wed, Apr 7, 2010 at 3:31 PM Subject: Follow up to Default Search Provider Changes for 10.04 To: ubuntu-devel , Ubuntu Desktop Discussion Each release we determine the best default web browser and the best default search engine for Ubuntu. When choosing the best default search provider, we consider factors such as user experience, user preferences, and costs and benefits for Ubuntu and the browsers and other projects that make up Ubuntu. Up until Ubuntu 9.10 these defaults have always been Firefox and Google. Earlier in the 10.04 cycle I announced that we would be changing the default search provider to Yahoo!, and we implemented that change for several milestones. However, for the final release, we will use Google as the default provider. I have asked the Ubuntu Desktop team to change the default back to Google as soon as reasonably possible, but certainly by final freeze on April 15th. It was not our intention to "flap" between providers, but the underlying circumstances can change unpredictably. In this case, choosing Google will be familiar to everybody upgrading from 9.10 to 10.04 and the change will only be visible to those who have been part of the development cycle for 10.04. Cheers, Rick -- ubuntu-desktop mailing list ubuntu-desk...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Fwd: Follow up to Default Search Provider Changes for 10.04
I've updated the lucid-1e branch to reflect the new default search engine. I've also updated the window controls order, as well. A new pot file will be generated soon. --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Trying to compile the manual locally.
Hello, Fran.
On Thu, Apr 8, 2010 at 2:33 AM, Fran Dieguez wrote:
> Hi all,
>
> For testing purposes I'm compiling the manual locally on my computer.
> I have exported the po file from launchpad and the compilation is mostly
> done but while compiling the references says:
>
> "Latex Warning: There were undefined references.
>
> Latex Warning: Label(s) may have changed. Rerun to get cross-references
> right."
>
> and outputs a bunch of errors like
>
> "Reference `blablabla' on page XXX undefined on input line "
>
> I reviewed all the references of chapter/section/... and are correct, all
> of them are untranslated and with the original format.
When I try to compile the Galician manual (with the latest po file),
it fails because \acronym has been misspelled as \acrony at one point:
"... Windows 8 como Mac \acrony{OS~X} no seu computador."
Another error is farther along. In the section talking about
OpenOffice.org, you have a couple \r's in there that should be
removed. There is also an extra closing brace } after the URL. It
looks as if the paragraph may have been copied and pasted partially.
The \menu command is misspelled as \meu.
The \window command is misspelled as \windo. (For the Seleccionar
ficheiros window.)
After fixing these errors, the references check out okay.
The reason LaTeX complains about the missing references is because the
first time it compiles the .tex file, it generates an .aux file that
contains the list of \labels. During this first run, the
cross-references are still unresolved. (They'll appear as ?? in the
PDF.) Only during the second and later runs does LaTeX read the
labels from the .aux file and replace the missing references (??) with
page numbers, names, figure numbers, etc. Since your document was
failing to complete the first run, the references were still
undefined.
> For other hand, at the title page the string "The Ubuntu Manual Team"
> translated to galician is too width and it gets out of the page. I'm
> thinking in putting a breakline character in latex codification to split the
> line. Is there some better solution?
We're going to be dealing with the title pages manually, so we can
tweak the design for each translation. The only thing we'll need from
the translations is the \title and \author command arguments to be
translated. We'll deal with any line-breaking and font scaling issues
on a case-by-case basis.
--Kevin
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] New style guide
Hey, Martin.
2010/4/7 Martin Lukeš :
> I couldn't find command
> \ignorespaces
> anywhere.
>
> It is used in Prologue:
>>
>> \mbox{}\marginnote{To learn more about Linux distributions, see
>> \chaplink{ch:learning-more}.}\ignorespacesThese early \acronym{GUI}s were
>> difficult to configure
I'll add this to the style guide. It doesn't need to be translated.
In fact, I think I removed it from the prologue a while back, so you
shouldn't be seeing it anymore.
For reference, though, you can ignore it. It's only job is to remove
any whitespace that follows. (In this case, it was swallowing the
newline character. That, and the empty \mbox{} caused the baseline of
the margin note to align with the baseline of the first line of the
paragraph. Details, details..)
--Kevin
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] "do not translate this" note
Hey, Martin.
2010/4/8 Martin Lukeš :
> Hi Kevin
> I'd like to ask about translating.
> At the beginning of the manual there are few strings with "do not translate
> this" note. For example just this one
> https://translations.launchpad.net/ubuntu-manual/lucid-e1/+pots/ubuntu-manual/cs/1/+translate
> Here draws my attention the {en} part.
> Most of the following strings are tempting as well.
>
> So should we for example alter the {en} for {cs} or not?
> And if not. Are we suppose to leave these strings alone with no translation
> at all. Or could we copy the original text as translation, so it could be no
> more between untranslated strings.
You should not translate that string. If you like, you can accept the
original string as the 'translation' so that it doesn't sit around as
'untranslated' the entire time.
That string in particular sets the default language if there is no
other language specified. The Makefile will set the appropriate
language code at compile-time.
Other strings that have been marked as 'do not translate' are usually
modified at compile-time, as well.
--Kevin
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] New style guide
'allo.
2010/4/10 Martin Lukeš :
> Hi Kevin
> I have a question ... again. ;)
Great! :)
> This time it is about \newglossaryentry command.
>>
>> \newglossaryentry{⟨keyword⟩}{name={⟨term⟩}, description={⟨definition⟩}
>
> I'd like to know if we really shouldn't translate "keyword".
> And what is the difference between the "keyword" and a "term".
The ⟨keyword⟩ is actually a label used internally by LaTeX to link the
\newglossaryentry and the \gls commands. It should be left
untranslated as I think LaTeX may not like non-ASCII characters in the
label. The ⟨keyword⟩ itself never appears in the text, just the
⟨term⟩.
Also, while it may not appear in the glossary entries in English, if
your language forms plurals of the words using some other mechanism
than simply appending an 's' to the end of the word, you'll want to
add plural=⟨plural form⟩. Something like:
\newglossaryentry{cherry}{name={cherry}, description={A small, red,
tasty fruit that is often baked in pies.}, plural={cherries}}
This allows us to use the \glspl{cherry} command in the text:
I like \gls{cherry} pie. \Gls{cherry} pie contains lots of \glspl{cherry}.
produces:
I like cherry pie. Cherry pie contains lots of cherries.
I hope that helps clear things up a bit. Let me know if you have
further questions. (The glossary stuff is a bit more complicated and
can be rather confusing.)
> BTW you have the old directory/chapter organization in Style Guide.
Ah, I fixed that the other day but apparently forgot to upload the new
PDF. I've done that now.
Thanks!
--Kevin
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] quotes
Hello, Martin. 2010/4/11 Martin Lukeš : > Hi Kevin > I'd like to ask you about quotation marks for Czech language. > You wrote "Quotation marks for other languages are entered as their Unicode > characters." in Style Guide. > In hand-written expression we are used to write quotes like „this“. > How do we do that in manual? In plain TeX (and plain LaTeX), English-style quotation marks are entered using `` and ''. Since we're using XeLaTeX (which supports multiple languages and Unicode), if you use different quotation marks in your language, replace the `` and '' with the opening and closing quotation marks that you normally use. You said that you are using „these quotation marks“, so I expect you can enter those quotation marks into the translation just as you did into this email message. --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] quotes
'allo.
2010/4/11 Martin Lukeš :
> Well, it's actually not that easy.
> I wrote we use those quotes in hand-written expression. When we write quotes
> on PC we're depending on text editor to automatically change "these" to
> „these“ since on our keyboards is just "this" character as double quotes.
>
> Is there a "simple"/any way to do this?
Ah, I understand.
Okay, there's a package I had halfway set up to try to make this a bit
easier, but never finished it. If you answer the following questions,
I can set it up for Czech for you. (And if anyone else wants to use
these commands for their own language, email me with your language and
the quote styles you use.)
For 'outer quotes', you're using „these“. What do 'inner' quotes look like?
For example, in the following sentence, replace the quotes here with
the quotes you would use in Czech:
"Kevin said, 'I have an easy way to write quotation marks,' " Martin
pointed out.
Once I have this info, I'll add Czech quotes to the quotation marks
database. Then you can use the following commands to write the
sentence above:
\enquote{Kevin said, \enquote{I have an easy way to write quotation
marks,}} Martin pointed out.
The \enquote{text} command will put quotation marks around 'text'. It
will normally use 'outer' quotes, unless it's already inside those
outer quotes, in which case it will use 'inner' quotes.
You can run 'texdoc csquotes' to read the documentation for this
package if you want the gory details.
--Kevin
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 561868] Re: wrong text
Fixed in r781.
** Changed in: ubuntu-manual
Status: Confirmed => Fix Committed
** Changed in: ubuntu-manual
Assignee: (unassigned) => Kevin Godby (godbyk)
--
wrong text
https://bugs.launchpad.net/bugs/561868
You received this bug notification because you are a member of Ubuntu
Manual Team, which is subscribed to Ubuntu Manual.
Status in Ubuntu Manual: Fix Committed
Bug description:
\newglossaryentry{proprietary}{name={proprietary}, description={Companies made
by companies that don't release their source code under an open-source
license.}}
Located in ./frontmatter/glossary-entries.tex :99
"Companies made by companies" :D
Should be "Programs" or "Applications" " made by companies" of course.
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 560416] Re: Description of Bluetooth icon preferences incorrect
Sayantan---
If you can fix this bug and attach a patch, I'll get it applied.
Thanks!
--
Description of Bluetooth icon preferences incorrect
https://bugs.launchpad.net/bugs/560416
You received this bug notification because you are a member of Ubuntu
Manual Team, which is subscribed to Ubuntu Manual.
Status in Ubuntu Manual: Confirmed
Bug description:
Chapter and Page Number the bug is located on: 4 pg 113
What type of bug it is : Incorrect Information
The description of bluetooth icon preferences is incorrect.
You can access the Bluetooth preferences by right-clicking on the Bluetooth
icon on the right hand side of the top panel. It is usually located next to
the volume icon.
Right-clicking on the Bluetooth icon opens a popup menu with several choices,
such as an option to \menu{Turn off Bluetooth}.
The right clicks should be actually left clicks.
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 533444] Re: symbols for closing etc. of windows changed side
** Changed in: ubuntu-manual Status: Fix Committed => Fix Released -- symbols for closing etc. of windows changed side https://bugs.launchpad.net/bugs/533444 You received this bug notification because you are a member of Ubuntu Manual Team, which is a bug assignee. Status in Ubuntu Manual: Fix Released Bug description: With the new layout, the buttons for closing etc. of windows moved from right to left ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 563654] Re: Doubled information in item 1422 (in web browser) of manual
*** This bug is a duplicate of bug 560315 ***
https://bugs.launchpad.net/bugs/560315
** This bug has been marked a duplicate of bug 560315
Same sentence two times on string number 1422
--
Doubled information in item 1422 (in web browser) of manual
https://bugs.launchpad.net/bugs/563654
You received this bug notification because you are a member of Ubuntu
Manual Team, which is subscribed to Ubuntu Manual.
Status in Ubuntu Manual: New
Bug description:
Contents of item is twice it should be only:
The \commandlineapp{apt-get} \code{update} command can be used to quickly
refresh the list of packages that are available in the default Ubuntu
repositories, as well as any additional repositories added by the user (see
\chaplink{ch:software-management} for more information on repositories).
Manual version: Lucid-e1
Chapter and page: do not know I am translating using web browser
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 564183] Re: Wrong glossary tag
You're correct, it should be \glspl. I've fixed this in r790.
** Changed in: ubuntu-manual
Milestone: None => release-candidate
** Changed in: ubuntu-manual
Assignee: (unassigned) => Kevin Godby (godbyk)
** Changed in: ubuntu-manual
Importance: Undecided => High
** Changed in: ubuntu-manual
Status: New => Fix Committed
--
Wrong glossary tag
https://bugs.launchpad.net/bugs/564183
You received this bug notification because you are a member of Ubuntu
Manual Team, which is subscribed to Ubuntu Manual.
Status in Ubuntu Manual: Fix Committed
Bug description:
The line (Located in ./prologue/prologue.tex :63) (Launchpad string number 85)
\marginnote{Whilst modern graphical \gls{desktop environment}s have generally
replaced early ...
produces funny results in Asturian language. Being a plural, shouldn't we use
the plural tag? (with plural={blahblah}, if needed, in glossary definition):
\marginnote{Whilst modern graphical \glspl{desktop environment} have generally
replaced early ...
Best regards.
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 560315] Re: Same sentence two times on string number 1422
Fixed in r791. ** Changed in: ubuntu-manual Assignee: (unassigned) => Kevin Godby (godbyk) ** Changed in: ubuntu-manual Milestone: None => release-candidate ** Changed in: ubuntu-manual Status: Confirmed => Fix Committed -- Same sentence two times on string number 1422 https://bugs.launchpad.net/bugs/560315 You received this bug notification because you are a member of Ubuntu Manual Team, which is subscribed to Ubuntu Manual. Status in Ubuntu Manual: Fix Committed Bug description: The strings number 1422, 1424 ( https://translations.launchpad.net/ubuntu-manual/lucid-e1/+pots/ubuntu-manual/el/+translate?field.alternative_language-empty-marker=1&show=all&start=1420 ) have the same sentence two times. ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 564305] Re: wrong numbers
I've fixed this in r792. ** Changed in: ubuntu-manual Status: New => Fix Committed ** Changed in: ubuntu-manual Milestone: None => release-candidate -- wrong numbers https://bugs.launchpad.net/bugs/564305 You received this bug notification because you are a member of Ubuntu Manual Team, which is subscribed to Ubuntu Manual. Status in Ubuntu Manual: Fix Committed Bug description: ...and the one you see in front of you belongs to the default Ubuntu 10.10... Located in ./around-desktop/around-desktop.tex :58 Should be Ubuntu 10.04, right? ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] German quotation marks
Hello, Daniel.
On Fri, Apr 16, 2010 at 1:17 PM, Daniel Schury wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
>
> in german the manual needs to use »?« and ??? as quotation marks. What
> was the correct procedure to include them correctly, except just enter
> them into the translation?
You have the choice of either entering them directly into the
translation like that or wrapping the quoted text in the \enquote{...}
command. The \enquote{...} command will use the proper quotation
marks based on your language (if I have it set up properly) and the
level of quotation (i.e., it will keep track of whether to use inner
or outer quotation marks).
If \enquote{} doesn't work as expected (wrong quotation marks, errors,
etc.), send me an email with your language and the Unicode numbers for
the quotation marks you use (both opening and closing for inner and
outer quotes).
--Kevin
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] New style guide
Hey, Martin. I apologize for the late reply to this one. I flagged it to respond to later and it promptly got buried under a deluge of other email. 2010/4/12 Martin Lukeš : > Hi Kevin > Me again. ;) > > I noticed that you probably missed the \eg command when writing Style Guide. > Or it was on purpose since it is the simplest command I saw so far. :D The \eg and \ie commands are new. I sneaked those in at the last minute. \ie gets expanded to 'i.e.', a Latin abbreviation for 'id est', meaning 'that is' \eg gets expanded to 'e.g.', a Latin abbreviation for 'exempli gratia', meaning 'for the sake of example' or 'for example' When you're translating these two terms, you have two options: 1. Tell me what the equivalent of 'i.e.' and 'e.g.' are for your language and I'll adjust the macros for your language. If you choose this option, you won't need to translate the \ie or \eg commands individually; you can leave them as-is in the sentence. 2. Replace the \ie and \eg commands with appropriate translations for your language each time they occur in the text. If you'd like me to translate the macros for you (so you don't have to each time you encounter one), send me the name of your language and the proper translations for 'i.e.' and 'e.g.'. Thanks! --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] Final draft of the US English manual
Hello, everyone. I've uploaded the final draft of the US English manual. If you have a few minutes, I'd appreciate it if you would page through it and let me know of any bugs you notice. http://builds.ubuntu-manual.org/builds/ubuntu-manual-final-draft.pdf You can either reply to this email with the bugs you've found or message me in the IRC channel. If I'm offline when you message me on IRC, I'll see your message when I wake up. I'm hoping to upload this to lulu.com later today or tomorrow so I have time to set things up and make sure it's ready for purchase starting the 29th. Thanks again for all your help and hard work! We've come a long way in the past few months, and it's only been possible with your contributions. --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 570125] Re: No version of TeX Live was detected while texlive IS installed
When you ran the TeX Live 2009 installation script, did you enable the 'create symlinks' option? If not, I would run 'sudo tlmgr --gui' (this requires that you have the perl-tk package installed), then from the Actions menu, click "Handle symlinks in system dirs". From the dialog that appears, click the "Update symbolic links" button. This will create the symlinks so that the tlmgr has a symlink in the path. After that's been done, running 'which tlmgr' should show the result '/usr/local/bin/tlmgr' or another path to the tlmgr script. After that, the install-pkgs.sh script should successfully detect the TeX Live installation. If this doesn't work, please let me know and we can investigate it further. ** Changed in: ubuntu-manual Assignee: (unassigned) => Kevin Godby (godbyk) -- No version of TeX Live was detected while texlive IS installed https://bugs.launchpad.net/bugs/570125 You received this bug notification because you are a member of Ubuntu Manual Team, which is subscribed to Ubuntu Manual. Status in Ubuntu Manual: New Bug description: ~/ubuntu-manual/pkgs$ ./install-pkgs.sh Checking TeX Live version...Status: install ok installed No version of TeX Live was detected. It appears that you do not have TeX Live 2009 installed. Please follow the installation instructions on the Ubuntu Manual wiki to install TeX Live 2009: BUT apt-cache policy texlive texlive: Installed: 2009-7 Candidate: 2009-7 Version table: *** 2009-7 0 500 http://fr.archive.ubuntu.com lucid/main Packages 100 /var/lib/dpkg/status Maybe texlive is not "fully" installed but this is another question... BTW, texlive-base is also installed... The script seems to be unaware about texlive2009/lucid... ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Final draft of the US English manual
Hello, Jeremy. On Tue, Apr 27, 2010 at 9:58 AM, Jeremy Bicha wrote: > The index looks pretty bad. There are nearly-duplicate entries like: > > Apt, 123 > apt, 123 > Apt-get, 123 > Apt-get, 123-125, 137 > F-Spot, 27 > F-Spot Photo Manager, 83 > gedit, 123 > gedit Text Editor, 27 > Nautilus, 29-32, 34, 130 > Nautilus File Manager, 121 > > Others include (Ubuntu) Software Center, Pidgin, Rhythmbox, (Mozilla) > Firefox I agree completely. > I reported this via the Google Docs form shortly before string freeze but > maybe my bug was lost. Your bug wasn't lost, we just haven't had time to address the issue in this first edition. It's one of the top things on my list for the second edition (which will will start working on in just a few days). Once I've got this first edition released (and take a second to catch my breath), I'll write up some notes on how I think the indexing and glossary stuff should work. Then we can get those up to speed. Thanks for reporting this again, though! --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 568652] Re: Mac OS X in lower case
Per the name ("Mac OS X" versus "Mac OS" versus "OS X", etc.): Apple
consistently uses "Mac OS X". The name of the operating system is "Mac
OS" and it's version 10 (X in roman numerals). [It should, in fact, be
pronounced "Mac Oh-Ess Ten". Apple uses to be quite insistent on this
when it was first released.]
Per the case: "OS X" is actually set in small-caps, not lowercase.
Similarly, GNOME, KDE, XFCE, DAAP, IP, and other acronyms are set in
small caps. There is an argument to be made that "OS X" is two short
words and shouldn't be set in small-caps. I debated whether to use
uppercase or small caps for quite a while. In the end, I decided to set
them in small-caps for the sake of consistency.
If you would like to argue about the case of text "OS X", feel free to
leave your argument here and I'll consider them -- I'm still a bit on
the fence about this one.
** Changed in: ubuntu-manual
Assignee: (unassigned) => Kevin Godby (godbyk)
** Changed in: ubuntu-manual
Milestone: None => edition-2
--
Mac OS X in lower case
https://bugs.launchpad.net/bugs/568652
You received this bug notification because you are a member of Ubuntu
Manual Team, which is subscribed to Ubuntu Manual.
Status in Ubuntu Manual: Confirmed
Bug description:
"Many applications designed for Microsoft Windows or Mac os x will
not run on Ubuntu"
"Since Ubuntu’s market share is not as substantial as Microsoft’s Windows or
Apple’s Mac os x"
First, I think it should read: "Mac OS X"
Second I would consider calling it "Mac OS"..
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] application tag
Hello, Martin. 2010/4/29 Martin Lukeš : > Hey Kevin > I know it's late for the first release, anyway. > > Relating to bug https://bugs.launchpad.net/ubuntu-manual/+bug/565343 about > manual conventions. > I found that \application tag do nothing. At least it looks like. > For an example see attached image where "Ubuntu Software Center" is in this > tag. Other occurrences of this tag looks the same. You're partially correct. Initially, the \application tag did two things: Set the application name bold-faced type, and added an index entry. When reading through the manual, though, having everything in bold (button names, application names, tabs, drop-down lists, checkboxes, radio buttons, text field names, menu names, etc.) was a bit too much. It made it difficult to read. To help alleviate this a bit, I turned off the bold-faced type for the application names. The \application tag does still, however, add an entry to the index. --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Plans for the websites
Hello. On Thu, Apr 29, 2010 at 5:34 PM, Ilya Haykinson wrote: > I would add to this "Create a way to read the manual online", i.e. embed > some flash-based PDF display, to let people without a PDF reader look > through our manual. You could embed Google's PDF viewer on our website: https://docs.google.com/viewer I think it'll be a lot more interesting when we have an HTML version of the manual online, though. (I've got some ideas there.) > We should also try to find a way to have key phrases from the manual indexed > by search engines -- otherwise people won't find the manual when trying to > answer their questions. I think Google, at least, does a fairly decent job of indexing PDFs. I'm not sure if it's aware of the PDFs on our site yet or not. Adnane: Something we might want to look into is creating a sitemap.xml, too. (http://www.google.com/support/webmasters/bin/answer.py?answer=156184&hl=en) --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] Tabula rasa
Hey, guys. Before we all get started on updating the lucid-e2 branch, I wanted to run an idea by you. I'm hoping that those more experienced with bzr/Launchpad can help. Right now, our branch is over 150 MB in size. The actual size of the source files required to build the manual is less than a megabyte. Many of the files in the branch are either no longer needed or don't belong there. The website has been moved to its own repository, for instance. Unfortunately, when you delete a file, it seems that its history is still kept in the repository and when someone branches the repository, that history must be downloaded, too. I propose that we create a completely new branch -- with no history and no files -- and then copy the requisite files from the lucid-1e-en branch (which is where the latest edits are) into this new branch. Is there a better way to handle this situation? (I admit I'm not that familiar with bzr.) Thanks for your help! --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] application tag
'allo.
2010/4/29 Martin Lukeš :
> Right, index. Totally forgot about that. ;)
No worries. :)
> I might have just few more questions.
> Since application tag doesn't change the font, it's fine if I do something
> like:
>>
>> Pomocí \application{Writer}u.
>
> Whole "Writeru" word will be with the same font and all?
>
> And since Czech language has one beautiful "burden" called declension, when
> I do:
>>
>> Pomocí \application{Centra softwaru pro Ubuntu}.
>
> And then mark its basic form:
>>
>> Použijte \application{Centrum softwaru pro Ubuntu}.
>
> Then in index I get two items marking the same application just because of
> two characters. Is there a workaround so both could be under one item? Their
> basic form would be the best. ;)
Yeah, I knew this would eventually come up!
Okay, I've modified the \application command slightly. I'll first
illustrate its use with your examples above:
Pomocí \application[Writer]{Writeru}.
Pomocí \application[Centrum softwaru pro Ubuntu]{Centra softwaru pro Ubuntu}.
Použijte \application{Centrum softwaru pro Ubuntu}.
Given that input, the PDF will contain the following:
Pomocí Writeru.
Pomocí Centra softwaru pro Ubuntu.
Použijte Centrum softwaru pro Ubuntu.
And the index will contain the following two entries:
Centrum softwaru pro Ubuntu
Writer
Now for the details. The first argument (inside square brackets [])
is an *optional* argument. If you provide this optional argument,
that is what will appear in the index. If you don't supply the
optional argument, the mandatory argument (that which appears in
braces {}) is what will appear in the index. The document text will
always display what was provided in the mandatory (braces {})
argument.
\application[index entry]{in-text words}
This means you can use whatever declension is called for in text (as
the mandatory argument), and keep the index entries consolidated by
using a canonical name in the optional argument.
The \commandlineapp macro will work the same way.
Does this solve the problem? And are there other commands that need
this treatment?
Thanks!
--Kevin
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] [Bug 572318] Re: website looks misaligned in epiphany
** Project changed: ubuntu-manual => ubuntu-manual-website ** Changed in: ubuntu-manual-website Assignee: (unassigned) => Adnane Belmadiaf (adnane) -- website looks misaligned in epiphany https://bugs.launchpad.net/bugs/572318 You received this bug notification because you are a member of Ubuntu Manual Team, which is subscribed to Ubuntu Manual. Status in Ubuntu Manual Website: New Bug description: Your website looks missaligned Using Lucid Epiphany browser. ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] How to translate \chaplink{ch:learning-more}
Hello.
On Tue, May 4, 2010 at 11:42 AM, Quynh Vu Do wrote:
> Hi,
>
> Is it right that translation to Vietnamese of the following string:
> \chaplink{ch:learning-more}
>
> should be like:
> \chaplink{ch:học-thêm-nữa}
>
> i.e. each word in the chapter name should be separated by dashes, not blank
> characters?
>
> and not like
> \chaplink{ch:học thêm nữa}
The text inside the \chaplink command should match the text inside the
corresponding \label command.
I would strongly recommend leaving the \chaplink and \label commands
untranslated. I don't know if XeLaTeX can handle non-ASCII characters
in the labels.
--Kevin
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] State of the bzr branches
Hello, all. I wanted to give you an update on the state of the branches we've set up for our project. lucid-e1: This branch contains the locked English version of the manual that the translators are working against. This branch should not be modified by anyone other than Throsten Wilms (thorwil) and I (godbyk). Everyone else can safely ignore this branch. lucid-e2: This branch contains the ongoing work for Getting Started with Ubuntu 10.04, Second Edition. This is a new branch that I just created. (The previous branch that lived here has been moved out of the way so we can start with anew without bringing in files that don't belong.) If you would like to help with editing on this branch, please remove any previous branches you have lying about and pull a fresh copy of this branch: bzr branch lp:ubuntu-manual Be careful that you only add files that are required for compiling the manual. No website files or other material that won't appear in the manual should be in this branch. maverick: This branch will be used for Getting Started with Ubuntu 10.10. There shouldn't be any activity or work in this branch yet. (It will probably be wiped out and restarted based on lucid-e2 just prior to starting work on the Maverick manual, so any changes made here will likely be lost.) Do not make any changes to this branch at this time. Please let me know if you have any questions. Thanks! --Kevin Godby ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
[Ubuntu-manual] Releasing translated editions
Hello, everyone. Now that we've successfully released Getting Started with Ubuntu 10.04 in English, it's time to turn our attention to releasing the translated versions. Each translated version will be released as it's ready. To ensure that the translated versions are as high quality as the original English version, we will assign an editor to each translation. The editor will work with the translators and will let us know when their translation is ready to be released. Before the translation is released, the following must be done: 1. All of the screenshots must be taken and proofed. To check the status of the screenshots for your language, see http://screenshots.ubuntu-manual.org/. If you have any questions about the screenshots, you can ask on this mailing list or in our IRC channel. 2. All of the text must be translated in Launchpad. To check the status of your translation, see https://translations.launchpad.net/ubuntu-manual. 3. The translated manual must compile cleanly to the PDF. There must be no errors during compilation. You can check the status of the your translations PDF at http://builds.ubuntu-manual.org/. If you have questions about the status there or need help troubleshooting an error or warning message, you may contact me via this list or in the IRC channel. 4. Finally, the editor will need to go through the translated manual and make sure that it looks good visually. This means that the margin notes should be properly aligned with the paragraphs they refer to and they're not falling off the page. Screenshots should be in place. And the design of the manual (layout, typography, title page, etc.) should be of excellent quality. I will work with you on this (as much of these issues are handled in the code that I have to write myself). Once the editor has approved all of the above, three versions of the manual will be created: (a) a PDF suitable for on-screen viewing (with colored hyperlinks), (b) a PDF suitable for printing at home (without hyperlinks), and (c) a version to be submitted to lulu.com for sale (which requires US letter-sized paper instead of A4 paper). For this process to work, we will need an editor for each translation. If you would like to be the editor for your translation, please respond to this email with your full name, email address, Launchpad ID, and language. The editors should be fluent in the language, willing to help edit .tex files directly (primarily to rearrange margin notes and other tweaks), have a critical eye for grammar, punctuation, design, and typography. (You will, of course, be able to have other translators help you with this work.) As an editor, you will be the primary point of contact for that translation and will have the final say as to when the translation gets published. If you have any questions about this process, please feel free to respond to this email or chat with us in the IRC channel. The IRC channel is located on Freenode #ubuntu-manual. My IRC nick is godbyk. Thanks for all your hard work and help in making the Ubuntu Manual Project such a success! --Kevin Godby ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Contributing to the project
Hello, Paul. On Thu, May 6, 2010 at 4:22 PM, Paul Strickland wrote: > Hello, > > When I upgraded to Ubuntu 10.04 I was made aware of the Ubuntu Manual > project, and thought the document was an excellent guide for people new > to the operating system, so congratulations. > > I wanted to ask if I could offer some of my time to the project. Looking > at your Wiki page, I think I would probably fit best in the Editor > category. If you can make use of me I'd be glad to contribute in some > way; I've been using Ubuntu for about a year now and feel as though I > could be helping to increase its popularity! We'd be very glad to have your help! As you've noticed, we've just released Getting Started with Ubuntu 10.04. We now have two parallel goals: (1) release the translated versions as they're completed, and (2) edit our manual to fix all the bugs we didn't have time to get to previously and release a second edition. If you'd like to help us with editing the second edition, there are two primary ways to go about it: (1) read through the first edition of the manual (which you can download from our site at http://ubuntu-manual.org/) and file bugs in Launchpad, or (2) if you're feeling more adventurous, and don't mind editing TeX files, you can download and install TeX Live 2009, check out our code from the bzr repository, and make corrections to the files themselves. If you'd like to go the second route, the instructions at http://ubuntu-manual.org/getinvolved/editors will help you get started. (The instructions can be a bit obtuse in some places, so if you hit snags, feel free to ask us for help. Additionally, if you have recommendations for improving the instructions, I'll happily accept those, too.) In any event, welcome to the project! if you have any questions, comments, criticisms, etc., feel free to email this list or visit us on IRC (Freenode) in #ubuntu-manual. Thanks for your interest! --Kevin Godby ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Contributing to the project
Hello, Denise. On Fri, May 7, 2010 at 11:32 AM, Denise Wood wrote: > Greetings Ubuntu Manual Folk! > > I thought I'd properly say hello - I rather worry I'd intruded in the > meeting last night without introducing myself (I'm Synergetic on > freenode). Not at all -- we always appreciate input from anywhere we can get it. > My name is Denise - I'm currently a final-year MA Linguistics student > from the U.S. studying in Edinburgh, Scotland. I've been using Ubuntu > since 2004 and have led a couple install days and helped numerous > friends with installs. It's a fantastic operating system but I've not > had the opportunity to contribute more than a few bug reports. > > I've worked a technical writer and really enjoy writing accessible > manuals - I heard about the Ubuntu Manual team through a friend of > mine who heard of it from one of Jono's podcasts and I thought it > would be a fantastic way to get involved and give back to the > community. Excellent! We could use the help of some technical writers -- not only in writing content but also in critiquing our style and helping us improve it to better address our audience's needs. One of the tasks I'd like to focus on during the next few weeks is establishing a style guide. Currently our style guide is just a collection of notes I tossed together for a quick introduction to LaTeX. It's primarily technical material and doesn't cover writing style, grammar, usage, voice, etc. You can see the current version of the style guide at http://files.ubuntu-manual.org/style-guide.pdf. If you'd like to help improve and expand our style guide, you can add some notes to this pad: http://pad.ubuntu-uk.org/ump-style-guide. I will probably send out an email a bit later this week about it so we can really start working on it. > One thing I thought might be improved is the "Become a Writer" link on > the Ubuntu Manual page - it rather immediately sends you a page for > getting an SSH key installing LaTeX and bazaar and such things - but > it should have "Join our Community" first where they might find, > perhaps, a friendly list of people contributing and the sub-projects > they're working on and a list of things that could be done by people > just joining. I just worry that some people might find the list of > installation requirements a bit intimidating to be confronted with > before even signing up and having an idea of how the community and > project is organised. I agree completely. The current authors/editors page is a quite scary to stumble across. Currently it serves primarily as a link we can point people to when they want to get started. But a friendlier introduction and overview would be much better. I think the instructions should be broken up into multiple pages as well. > Hopefully I can be of help to the community - I look forward to > getting to know you all! Welcome to the Ubuntu Manual project! --Kevin Godby ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] What are the dimensions of the printed book version ?
Hello. On Sat, May 8, 2010 at 9:54 AM, Quynh Vu Do wrote: > Hi, > > In Vietnam we are considering printing Getting Started with Ubuntu 10.04 in > Vietnamese locally. > Do you know what would be the best dimensions for the printed version, based > on the PDF downloaded from the UMP website? > I suppose it will be something like 14x18cm ? > > I understood the manual could also be commanded on lulu.com but it seems to > be not yet available. The Vietnamese version of the manual hasn't been released yet, as it still needs to be edited. The English version of the manual is currently available from lulu.com at http://www.lulu.com/content/paperback-book/getting-started-with-ubuntu-1004/8709550. The Vietnamese manual will be released in two paper sizes: A4 (210 × 297 mm) and US letter (8.5 × 11 inches). The version printed through lulu.com will be US letter size. --Kevin Godby ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] (ast) Translated items are now suggestions
Hello.
On Sat, May 8, 2010 at 2:14 PM, Xuacu wrote:
> Hi there!
>
> I've found that already translated items in Asturian language now
> appears as suggestions in LaunchPad.
>
> After a quick overview, it looks like glossary entries which use an
> apostrophe (') within the translated string. Before I accept the
> suggestions, I'd like to know if that's because TeX warnings, errors, or
> some similar thing. It looks just fine in the current asturian build of
> the Manual!
I'm still investigating the situation. Recently, many of the
translated strings (in all the translations, not just Asturian) have
been demoted to 'suggested' instead of 'accepted'. I've contacted some
of the Launchpad guys to help figure out what's happened, but I
haven't got a response yet. I'll let you know what I discover.
I just updated the builds page (http://builds.ubuntu-manual.org/) with
the latest translations from Launchpad and the Asturian PDF is
compiling successfully.
--Kevin
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-manual
More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Releasing translated editions
Hello. Thanks! I've added you to the translation editors list. Here's a quick status report on the Asturian translation: * Nearly one third of the manual has been translated to Asturian. * The Asturian translation does compile correctly. There are a couple warnings that I'll help you fix soon. * There are still 10 screenshots that need to be taken in Asturian. The next step is to continue translating the text into Asturian and collect the remaining screenshots. On Sat, May 8, 2010 at 10:17 AM, Xuacu wrote: > I'm an absolute beginner to TeX, whose learning I've been > procrastinating for years :) Perhaps now it's the right time to give it > a go... Any advice for first steps with TeX? > > I'll try to get an sprint from my team in order to have a working > version of the Manual before lucid-e2 is due (July, isn't it?). > Hopefully, by the end of May we'll have all the screenshots in place and > the translations done. That gives us about one month to proofread the > Manual and to tweak on the TeX side of life. Right now the focus for translators has been on lucid-e1. The second edition (lucid-e2) will have a lot of string changes, not because of major content changes, but due to my rearranging the .tex code. (I've moved the margin notes around in the code so that they better align with the main text. The unfortunate side effect of this is that when I combine two separate strings (margin note + main text paragraph) into one string (containing both), Launchpad will consider this as a new string and likely won't recognize that it's a combination of two separate strings. This doesn't, however, prevent translators from copying and pasting the strings from the lucid-e1 translation to the lucid-e2 translation. If you have any questions, feel free to contact me. Thanks again for volunteering to be an editor and helping to translate the manual into Asturian! --Kevin Godby ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Contributing to the project
Hello, Paul. On Sun, May 9, 2010 at 8:20 AM, Paul Strickland wrote: > Thanks for the information. I followed the instructions for branching > the manual code and installing TeX Live 2009 without too many problems. > The only thing is that there doesn't appear to be a ubuntu-manual/pkgs/ > directory from which to run the install-pkgs.sh script. > > I think I've got plenty of material to read to try to familiarise myself > with the project, so I'll get stuck into that and keep an eye out for > any further news. Whoops! When I created the new second edition branch, I forgot to bring across the install-pkgs.sh script. I've copied it over and uploaded it to the branch. If you run 'bzr pull', it should appear now. Thanks for the heads-up! If you encounter any further problems, please let me know. Thanks again for helping with the Ubuntu manual project! --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-manual] Strange issues at translations on Launchpad
Hello, all. I'm aware of the problem, but I haven't figured out the cause yet. No one's responded in the Launchpad IRC channel yet. Since Benjamin Humphrey is at UDS with some of the Launchpad developers, I've tasked him with cornering one of the developers until they can help us figure out what's happened. If I hear anything, I'll post it to the list. --Kevin ___ Mailing list: https://launchpad.net/~ubuntu-manual Post to : ubuntu-manual@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-manual More help : https://help.launchpad.net/ListHelp
