User talk:Ikarsik

From Wikibooks, the open-content textbooks collection

Hello and welcome to Wikibooks!

Here are some tips to help you get started:

• You can sign your name on Talk and vote pages using four tildes, like this: ~~~~.
• Remember to conduct any editing experiments in the sandbox.
• If you're a Wikipedian, see Wikibooks:Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
  • If you want to base your work here on materials from Wikipedia, please use WB:RFI to bring the material over in compliance with the GFDL.
• If you're an instructor and plan on using wikibooks for a class project, see Wikibooks:Guidelines for class projects
• Please say hello at the Staff Lounge with any questions or ideas.
• Eventually, you might want to read the Manual of Style and Policies and Guidelines.
  • Please take a look at Wikibooks:Naming policy before starting a new book.
• Remember to maintain a Neutral point of view.
• Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page.

Good luck! --Herby ^{talk thyme} 08:16, 8 November 2006 (UTC)

Contents 1 HSC Extension 1 and 2 Mathematics/Linear functions 2 Nice Edits 3 Hello again 4 Hic 5 Japanese Wikibook discussion

[edit] HSC Extension 1 and 2 Mathematics/Linear functions

There are errors on that page with the math syntax. If you need help to fix the TeX markup, ask at WB:TECH. Happy editing! – Mike.lifeguard | ^talk 03:10, 2 December 2007 (UTC)

[edit] Nice Edits

I saw your edits to MIPS and Circuit Theory. Thanks for the help! Every little bit helps, and even small edits make books better. --Whiteknight (Page) (Talk) 01:32, 16 January 2008 (UTC)

Congratulations also for all the corrections you are making on the C++ Programming book, big help thanks... --Panic (talk) 04:48, 17 January 2008 (UTC)

[edit] Hello again

Where was the problem you detected on the print version?
I have restored it to the previous state so we can fix it (duplicating the all chapters will not fix it and will break the auto-update functionality that was created, editors will have to remember to edit both pages, and that is prone to generate errors).
Due to transclusions taking some time to update (probably the error you mentioned was due to that) it will take some time for the serve to restore the structure (probably more than 24h), try to check in the all chapters version (that should be the same without some of the print version text).
I will also take a closer look also later to see if I detect any problem. (You can use the by chapter view to make it easier, all views are structured as to represent smaller parts of the bigger page that is the print version) --Panic (talk) 15:39, 16 April 2008 (UTC)

The TOC problem should be a minor one, as stated in the header that information should not get printed, if it is then I or someone else have probably forced a toc on a low content subpage to help navigation (I remember doing something like that somewhere) but was confident that the print version would not print it... --Panic (talk) 15:43, 16 April 2008 (UTC)

The problem I saw with the print version was with putting

{{:C++ Programming/All Chapters}}

in the print version code. It made a link to All_Chapters instead of including its text. It might just do that for me though, or you might want that. The only thing that the print version page has that All_Chapters doesn't is the license, so if you added the license to the All_Chapters page, you could use that as your print version, because a print version should have all chapters. Shouldn't it?

I know in the code for the Fundamentals section there is a __TOC__ above the transcludes, but by removing that the TOC is moved down further in the page to another section that has TOC forced. I didn't want to go through just getting rid of TOCs because that might make the single page views look very bad. When I put the transcludes from All_Chapters in the print version after __NOTOC__ a TOC still shows up because __TOC__ in the Fundamentals chapter overrides __NOTOC__ at the top of the print versions code. This doesn't really matter for registered users because we can turn off TOCs in preferences, but unregistered readers would get the TOC just before the Fundamentals chapter when reading it. Not a big issue but I couldn't really do anything else to help so I just decided to try and fix this. Please check this, sorry for any inconvenience, and hello again to you too =) rawrawrer (talk) 18:16, 16 April 2008 (UTC)

Hummm I see, what you saw was the same that is present now ? only a link, this can be due to two things something was changes in the way transclusion works or some change was made and the server hasn't yet updated the output. Lets see if it takes more than 24h to update and if it does we should ask in the administration area why it stopped working.

The previous, and what we want is the view of the all chapters with the inclusion of the license (needed to satisfy its requirements on the print version) also the top header removes some of the navigation schemes from the output (like TOCs) so it should solve the last part of your post above, even if it is shown when you view the print version, it will not be present (as the warning box), it will be removed.

Well let's wait and see if the trasnclusion is updated, if not then something was changed or some error exists on the page, I can swear that it worked as intended but not on this location the creation date of the page to recent (04:47, 5 November 2006) so I can't check if something was different or altered. I think what is happening is that since the page is generated form another transcluded page if any change is done down the chain it will have to be generated for the hole collection to work, since I recently moved some pages that maybe the reason also. --Panic (talk) 19:17, 16 April 2008 (UTC)

I've asked User talk:Mike.lifeguard to see if he reaches the same conclusion or knows of a feasible alternative. --Panic (talk) 19:25, 16 April 2008 (UTC)

Ok, so it works now and User:Mike.lifeguard has removed all the forced TOCs from the pages, so no more TOC in the middle of the book. Thanks Mike! But this still has the code from All_Chapters being copied to the print versions code, so updating All_Chapters wont update the print version. Maybe if we transcluded the individual pages in All_Chapters instead of the chapters containing them, which transclude the pages anyway, the software would let us transclude All_Chapters. rawrawrer (talk) 08:15, 17 April 2008 (UTC)

[edit] Hic

That last wording/logic correction made my skin crawl a lot more that normal because the previous edition was attributed to me. I take this chance to state that I only have the blame of not having noticed that before :) hic...
Great work on proofreading it (I have asked several persons to take to that task but I've come to believe that most people doesn't read books cover to cover any more, at least technical books).
I can have some blame on some crazy wording as my first language isn't English and I do some of the edits at weird hours, any way it's 11.01 a.m and I'm off to bed now, I just checked your last work and couldn't sleep without commenting on it :) --Panic (talk) 10:05, 18 April 2008 (UTC)

thankyou =). I'm just reading quickly through the intro part. I'll probably do better proofreading in the object oriented chapter, because I never bothered to learn any of that the first time I looked at c++, so it will all be new material. I'm not really worried about the spelling, as long as I can read it. I made a quick PDF file for fun for this book, I'll upload it later and put the tag on the TOC1 page. It's messy but I think some of the pages look pretty good, and adobe reader can generate the bookmarks for each section. rawrawrer (talk) 11:50, 18 April 2008 (UTC)

I will move for the to removal TOC2, it always created problems, in navigation and the logical flow of the content. Most people don't use it and it has not been maintained. If that occurs it will restore TOC1 to the front page and restore navigation (no fallback to the multiple toc page to resume reading). I don't know if that will also help the PDF navigation (I never created a PDF from a Wikibook). I prefer reading on the screen than on real paper. Did multiple TOC created any problem on the PDF? --Panic (talk) 18:55, 18 April 2008 (UTC)

The code highlight in off on the PDF. O solution to remove TODOs from the print version should also be studied and the green syntax label that I've been using on the C Standard Library has lost it's box rendering it very ugly, may it be a result of a skin change you made on Wikibooks ? --Panic (talk) 19:25, 18 April 2008 (UTC)

I noticed that, but just ignored it. I think it is caused by the way I created the PDF. I had never created a PDF from a wikibook either and so I just tested it by saving the print page as a html file then opening it in OpenOffice.org writer and doing some basic formatting then exporting it to PDF. I'm pretty sure the change in formatting is caused by the monobook.css and common.css styling rules being left out. I think this might just be firefox not saving the css files locally, or something, so maybe if I just add the styling rules in at the start of the saved html file it will all be good. Meh, I'll look at it later. I just wanted C++ Programming to look like it meant business with a PDF file and all.

But the removal of the protected page with links to all 3 TOCs will be great. There hasn't been any talk on that for a while now, so there shouldn't be any opposition (right?). rawrawrer (talk) 19:58, 18 April 2008 (UTC)

I can only hope. It has all been my fault, I did think having multiple structures of a single book could be great and the framework (Wikibooks) does permit it, the only problem was the navigational aspect (only one of the navigations could be dominant), before User:Darklama implemented TOC2 there was another TOC also (deprecated by lack of use) that fallowed the main TOC but implemented a distinct navigational and layout scheme. Problems arose because TOC2 did not fallow the structural integrity of the previous TOCs it shifted pages and chapters (TOC1 did try to comply with some of the new views to enable the changes and in the long run it did improve structurally). My main objection was that User:Darklama changes were made unilaterally and disregarding stated oposition (that lead to moving TOC2 to the front page), deletionist (removed content due to idea that the book should be smaller and more to the point as in stick only to the standard side not the practical aspects, most alterations have still to be verified)...). User:Darklama has now created a new C++ book that would enable him to express his vision. To be fair and transparent I will have inform him that I'll be pushing for the pages removal, lets see if he can live with the changes...

As result that mess I'm also pushing for the prohibition of additional TOCs, see the conventions discussion page. --Panic (talk) 20:17, 18 April 2008 (UTC)

[edit] Japanese Wikibook discussion

Hi Ikarsik,

I just added a comment on Talk:Japanese#Wow._This_is_a_mess which I wanted to draw your attention to as you've been involved in this book. --Swift (talk) 14:49, 10 June 2008 (UTC)