## Friday, March 15, 2013

Created: 14th March 2013M / 3 Jamadilawal 1434H, Fr. [Ubuntu 12.04 Precise Pangolin]
Published: 15th March 2013M / 3 Jamadilawal 1434H, Fr.
Updated:

Assalamualaikum.

After creating the Bunga in Blender, see this post:
Bunga Blender
http://ubuntudigest.blogspot.com/2013/03/bunga-blender.html

... I went on to try create the letter Dad in Blender. Dad is the 15-th letter of the Arabic alphabet and the 16-th letter of the Jawi alphabet. The early result looked like a letter made of modelling clay, see Pic 1.

Pic 1 - Blender. The early result.

To create a better-looking letter, I thought of importing a file then tracing the letter but some how couldn't import the SVG file into Blender and didn't know why.

After watching this tutorial:
Blender Tutorial Import .svg file from Inkscape, Edit, Apply Texture, & Export 3d Image
http://youtu.be/jD0MBYmnJSk

... I realized that my mistake was I tried to import text instead of path. The text has to be converted to a path first, and then can it be imported into Blender. Referring to Pic 2, in Inkscape, select the object (text) then go to Path > Object to Path.

Using the Edit path by nodes cursor (see Pic 3), click the now-path object. The outline of the now-path object should have nodes like that in Pic 4 .

Pic 2 - Inkscape. Converting object to path.

Pic 3 - Inkscape. The Edit path by nodes cursor.

Pic 4 - Inkscape. Nodes, after converting object to path.

Shown in Pic 5 is the imported SVG Dad after some rotating, scaling and texturing. Shown in Pic 6 and Pic 7 are the final results of Pic 5.

Between Pic 6 and Pic 7:
- Pic 6 has a thicker extrusion and dimmer lighting
- Pic 7 has a thinner extrusion and brighter lighting.

Pic 5 - Blender. The flat SVG Dad.

Pic 6 - Blender. The final result 1.

Pic 7 - Blender. The final result 2.

blender.org
http://www.blender.org/

Inkscape. Draw Freely .
http://inkscape.org/

Alhamdulillah. Wassalam.

## Sunday, March 10, 2013

### Bunga Blender

Created: 10th March 2013M / 27 Rabiulakhir 1434H, Su. [Ubuntu 12.04 Precise Pangolin]
Published: 10th March 2013M / 27 Rabiulakhir 1434H, Su.
Updated: -

Assalamualaikum.

After creating a static gingerbread man using Blender, see here:
Enche' Biskut Halia Blender
http://ubuntudigest.blogspot.com/2013/02/enche-biskut-halia-blender.html

...  I went on to try-out the animated gingerbread man tutorial, see here:
Your First Animation in 30 plus 30 Minutes Part II

Unfortunately, I couldn't animate it. The gingerbread man won't take-on any pose; it stands there like a scarecrow. I don't know if I got the rigging or the skinning wrong :(

Pic 1 is the early result of trying something else instead of moping because of the animation failure.

Pic 1 - The early result.

Pic 2 - The final result. Much better.

In Pic 2, I don't know how to create a sunburst pattern for the petals, so a radial pattern will have to do :)

blender.org
http://www.blender.org/

Alhamdulillah. Wassalam.

## Saturday, February 23, 2013

### Enche' Biskut Halia Blender

Created: 22nd February 2013M / 12 Rabiulakhir 1434H, Sa. [Ubuntu 12.04 Precise Pangolin]
Published: 23rd February 2013M / 12 Rabiulakhir 1434H, Sa.
Updated: -

Assalamualaikum.

This is Eche' Biskut Halia, see Pic 1, my gingerbread man created using Blender 2.62 (see Pic 2). Somehow my gingerbread man reminds me of biskut kopi (coffee biscuit) sprinkled with coffee powder ^_^

Compare Enche' Biskut with the other gingerbread man in Pic 3.

Pic 1 - Enche' Biskut Halia the biskut kopi man.

Pic 2 - Splash screen. Blender 2.62.

Pic 3 - Gus the Blender Wiki gingerbread man.

Enche' Biskut's texture wasn't created on purpose to look that way. I just don't know where I got the steps wrong.

Tryout the gingerbread man tutorial here:
Your First Animation in 30 plus 30 Minutes Part I

blender.org
http://www.blender.org/

Wassalam.

## Wednesday, February 20, 2013

### Installing fonts for Z Notation symbols

Created: 7th February 2013M / 26 Rabiulawal 1434H, Th. [Ubuntu 12.04 Precise Pangolin]
Published: 20th February 2013M / 9 Rabiulakhir 1434H, We.
Updated: -

Assalamualaikum warahmatullah. My husband wanted to use the Z Notation domain antirestriction symbol, see Pic 1, in his assignment.

Pic 1 - Domain antirestriction symbol of the Z Notation using the Code2000 font as displayed here:
Unicode Character 'Z NOTATION DOMAIN ANTIRESTRICTION' (U+2A64)
http://www.fileformat.info/info/unicode/char/2a64/index.htm

I was unable to do a thorough search in the list of fonts in LibreOffice Writer because the Special Character dialog hang for unknown reasons. Up to that point there was no similar symbol to be found. I shutdown his laptop then moved-on to my laptop to do an online search.

Scrolling through the list of symbols here:
Unicode Characters in the 'Symbol, Math' Category
http://www.fileformat.info/info/unicode/category/Sm/list.htm
... I finally found the symbol. See Pic 2.

Pic 2 - List of math symbols, before installing the necessary font. In the rightmost column are images of the symbol. In the column next to the images are the symbols as displayed by the browser.

To check whether or not your brower supports the symbol in Pic 1, simply click this link:
Browser Test Page for Unicode Character 'Z NOTATION DOMAIN ANTIRESTRICTION' (U+2A64)
http://www.fileformat.info/info/unicode/char/2a64/browsertest.htm

The unsupported symbol will look pixeled like in Pic 3 while the supported symbol will look smooth like in Pic 4; that is unless the symbol is originally created to have a pixeled-look like the GNU Unifont in Pic 6.

Pic 3 means:
"You don't have the font in your system so the symbol is not displayed correctly in the browser."

Pic 4 means:
"You have the font in your system so the symbol is displayed correctly in the browser."

Proceed if you need to install the font.

Pic 3 - Unsupported. Pixeled. From the FileFormat.Info website.

Pic 4 - Supported. Smooth. From the FileFormat.Info website.

Part B: Local fonts check

To check the fonts in your system that supports the symbol in Pic 1, see Pic 5, simply click this link:
Local Font List
http://www.fileformat.info/info/unicode/font/fontlist.htm?text=⩤+-+Unicode+Character+'Z+NOTATION+DOMAIN+ANTIRESTRICTION'+(U%2B2A64)

Pic 5 - Checking local fonts, after installing a font that supports the symbol in Pic 1.

Prior to this post, no fonts in my system can display the symbol correctly. So a font that supports this symbol needs to be installed.

Part C: List of fonts that supports the Z Notation characters

Click the View All text-link to preview the symbols in the list of fonts installed on the FileFormat.Info server that supports the Z Notation symbols, see Pic 6, here:
Z NOTATION DOMAIN ANTIRESTRICTION (U+2A64) Font Support
http://www.fileformat.info/info/unicode/char/2a64/fontsupport.htm

Pic 6 - Among the fonts that support the Z Notation symbols. From the FileFormat.Info website.

Among the fonts that supports the Z Notation characters are:
• Code2000
• EversonMono
• EversonMono-Oblique
• GNU Unifont
• LastResort
• Quivira
• STIXGeneral-Regular
• Symbola
• Unicode BMP Fallback SIL

Note that only the bolded fonts are available in Ubuntu Software Center.

Part D: Installing a font that supports the Z Notation characters

In Part C, I chose to use the STIXGeneral-Regular font.

1. Run Ubuntu Software Center.

2. In the search field, type-in the search term, see Pic 7:
stix
The search results will auto-filter.

Pic 7 - Refer to Step 2. Searching for the package.

3. Click the...
Scientic and Technical Information eXchange fonts
fonts-stix
... package. See Pic 7.

Then choose either:

A. Click the Install button (see Pic 7) to install right-away.

or

B. Click the More Info button (see Pic 7) to read more about the package and click the Install button later. See Pic 8.

Pic 8 - Refer to Step 3.B. More information about the STIX (Scientic and Technical Information eXchange) font package.

4. The Authenticate dialog will pop-up. See Pic 9.

Enter the password in the Password: field then click the Authenticate button.

Allow the installation process to take place.

Pic 9 - Refer to Step 4. Authenticating the installation.

5. After the installation process is completed, either:
- test your browser, refer to Part A; or
- try the local font check, refer to Part B, (the STIXGeneral font is used in Pic 5); or
- try-out the newly-installed font in LibreOffice Writer.

Alhamdulillah. Wassalam.

## Sunday, February 17, 2013

### How To: Solve Warnings and Badboxes in LaTeX

Created: 8th December 2012M / 24 Muharam 1434H, Sa.
Published: 17th February 2013M / 6 Rabiulakhir 1434H, Su.
Updated:

Assalamualaikum warahmatullah. Inspired by this statement:
... I would never accept a final PDF where there's some Overfull \hbox.

http://tex.stackexchange.com/a/50838
... I decided to solve all the warnings and badboxes in my thesis although there is no problem at all to produce a PDF output (PDFLaTeX).

Starting with about 0 errors, 31 warnings, 212 badboxes (see Pic 1), I've managed to trim them down to 0 errors, 0 warnings, 3 badboxes (see Pic 2). The remaining badboxes are in the generated bibliography which I don't know how to solve.

Pic 1 - Starting with 0 errors, 31 warnings, 212 badboxes.

Pic 2 - Ending with 0 errors, 0 warnings, 3 badboxes.

1. Overfull \hbox messages tell you that some line sticks out over the right margin;

2. Underfull \hbox messages tell you that some line is poorly typeset (or that you've improperly used \\ to leave a vertical space (for example, typing two \\ in a row);

3. Underfull \vbox messages usually tell you that a page is poorly typeset.

http://tex.stackexchange.com/a/50838

What are underfull hboxes and vboxes and how can I get rid of them?
http://tex.stackexchange.com/questions/138/what-are-underfull-hboxes-and-vboxes-and-how-can-i-get-rid-of-them

Similar are \hbadness and vbadness which are a measure of how bad a box is, typically how much white space has had to be stretched. the exact number is not usually that relevant but 0 is good and 10000 is infinitely bad (TeX's badness calculation arbitrarily forces any very bad boxes to this amount).

http://tex.stackexchange.com/a/50850

My suggestion is to solve the warnings as much as possible first, and then solve the badboxes.

Part A: The draft

As suggested by Otis:
If you use draft mode (\documentclass[draft]{article}) you can see black lines on the side of your document where there is overfull hbox badness. This is a convenient way to find and fix these errors. – Otis Jul 26 '10 at 19:54

Source: What does “overfull hbox” mean?
In comment by Otis
http://tex.stackexchange.com/questions/35/what-does-overfull-hbox-mean#comment21_39

1. In the preamble, add the term (see Pic 3):
draft
...in the \documentclass.

Pic 3 - Refer to Step 1. Creating the draft.

2. Compile the document by Build > Compile > PDFLaTeX for the first compile. See Pic 4.

The following compiles can use the Build > QuickBuild. See Pic 5.

Pic 4 - Refer to Step 2. Compiling the PDF output.

Pic 5 - Refer to Step 2.

Don't worry when the figures in the output document are substituted with a thin black-bordered hollow rectangle, see Pic 6. Compare Pic 6 with Pic 7.

If you seem to get errors when previously there weren't any errors, try running this step (QuickBuild compile) a few times. Try about 3 to 4 times or more until you get about the same amount of warnings and badboxes as you had before changing the document into a draft.

Pic 6 - Refer to Step 2. The draft as viewed in Okular.

Pic 7 - Refer to Step 2. The original/finished document as viewed in Okular.

3. Make the necessary corrections to solve the warnings and badboxes. Refer to Part B to Part G in this post.

4. As this "drafting" step is temporary, the draft term added in Step 1 should be removed after the required corrections are completed in order to return to the 'print'/'real' mode.

Part B: "Shell escape feature is not enabled."

One of the warnings that might arise in Kile from Step 2 is the "Shell escape feature is not enabled." warning. See Pic 8.

Pic 8 - "Shell escape feature is not enabled." warning.

By solving the shell escape warning, this deducted 1 warning for me. See Pic 9.

Pic 9 - Progressing with 0 errors, 30 warnings, 212 badboxes.

Development of LaTeX frontend kile. () > eps && pdf

5. Go to Settings > Configure Kile... . See Pic 10.

Pic 10 - Refer to Step 5. Accessing the Configure - Kile dialog.

6. In the Configure - Kile dialog, see Pic 11,
in the leftmost column, go to Tools > Build.

Then under the Select a tool column, select PDFLaTeX.

Go to the General tab. In the Options: field, change from this:
-interaction=nonstopmode '%source'

... to this:
-interaction=nonstopmode -shell-escape '%source'

Source: Forward & Reverse DVI with multiple file document
http://www.latex-community.org/viewtopic.php?f=20&t=3380#p13225

Then click the OK button.

Pic 11 - Refer to Step 6. Enabling the shell escape option.

7. Compile the document. Refer to Step 2.

Part C: !h' float specifier changed to !ht'.

Fixing the "!h' float specifier changed to !ht'." warning (see Pic 12) should reduce the number of warnings.

Pic 12 - The "!h' float specifier changed to !ht'." warning.

The float specifiers:
h means here allowed,
t means top,
b means bottom,
p means on a float-page,
! means try harder! to place it earlier.

Source: h' float specifier changed to ht' warning when not attempting to specify a float
http://tex.stackexchange.com/a/1527

Usually h is too strict. This way you don't allow top, bottom or page placement. Use at least ht instead, or relax it to htbp or even !htbp if you like. If you really need it to be exactly "here", use the H option together with the float package. There are further ways. But adding placement options is usually fine.

Source: LaTeX Warning About Height, \hbox, and \vbox, and ht
http://tex.stackexchange.com/a/6983

LaTeX/Floats, Figures and Captions > Floats
http://en.wikibooks.org/wiki/LaTeX/Floats,_Figures_and_Captions#Floats

8. Check the float specifiers in the *.tex files.

Change from [!h] or [h!]
to [!ht] or [!hb] or any specifier combination you want depending on your needs. See Pic 13 and Pic 15.

Pic 13 - Refer to Step 8. Float specifier for a figure in my thesis.

9. Compile the document. Refer to Step 2.

My suggestion is: change the float specifier for one figure or table at a time then compile. If the number of warning goes down, only then proceed to the next figure or table.

Part D: "No positions in optional float specifier."

Fixing the "No positions in optional float specifier." warning (see Pic 14) should reduce the number of warnings.

Pic 14 - The "No positions in optional float specifier." warning.

I use sidewaysfigure and sidewaystable. Previously i didn't use the float specifier for the sideways because if I used an unsuitable specifier, LaTeX will lump all the figures at the end of the chapter instead of placing them where I have placed them throughout the chapter.

If you put in a suitable specifier, the warning goes away and the object (figure/ table) stays where you want it to be.

10. For the sidewaysfigure or sidewaystable, instead of using [!h] or [!ht], I used [!p]. See Pic 15.

Pic 15 - Refer to Step 10. The float specifier for a sidewaysfigure in my thesis.

11. Compile the document. Refer to Step 2.

My suggestion is: change the float specifier for one figure or table at a time then compile. If the number of warning goes down, only then proceed to the next figure or table.

The draft for Pic 15 is shown in Pic 16, and the "real" page is shown in Pic 17.

Pic 16 - Refer to Step 11. The sidewaysfigure in draft mode.

Pic 17 - Refer to Step 11. The sidewaysfigure in print mode.

Part E: "Font shape OT1/cmr/bx/sc' undefined(Font) using OT1/cmr/bx/n' instead on input line ##."

Fixing the "Font shape OT1/cmr/bx/sc' undefined(Font) using OT1/cmr/bx/n' instead on input line ##." warning (see Pic 18) should reduce the number of warnings.

Pic 18 - The "Font shape OT1/cmr/bx/sc' undefined(Font) using OT1/cmr/bx/n' instead on input line 6." warning.

You did nothing wrong. TeX tells you that it does not have Small Caps bold Computer Modern font, so it switches to bold normal font. This is a design decision by font author (Knuth) not to have this variant; you may try to find fonts that have bold small caps (not that I know of such) or to fake the effect using uppercase.

Actually your line is already in uppercase, so I wonder whether you really need small caps: usually people use small caps with lowercase letters, with \textsc{\MakeLowercase{...}}

Source: A problem with \textsc
http://tex.stackexchange.com/a/37620

12. There are 2 solutions I can think of, attemped, and worked for me:

A. The solution I used in my thesis is to remove the Small Caps code, \textsc and simply type in all capitals. See Pic 19.

B. Another way is as Boris mentioned. The code is shown in Pic 19 and the output is shown in Pic 20.

Pic 19 - Refer to Step 12. The Small Caps code. All caps (above) and Small Caps (below).

Pic 20 - Refer to Step 12. The output for Pic 19 at 150% zoom in Okular. All caps (above) and Small Caps (below).

13. Compile the document. Refer to Step 2.

Part F: "Overfull \hbox (##pt too wide) in paragraph"

Fixing the "Overfull \hbox (##pt too wide) in paragraph" badbox (see Pic 21) should reduce the number of badboxes.

Pic 21 - The "Overfull \hbox (##pt too wide) in paragraph" badbox.

but what can be done about Overfull \hbox? – alfC Apr 5 at 18:10

@alfC Some small text editing usually solves the problem. I use to say that very rarely the first or even the fourth version of a text has so polished a prose that it's become untouchable. :) – egreg Apr 5 at 19:40

small text editing means changing the choice of words? (just asking). – alfC Apr 6 at 7:08

@alfC That's one of the possibilities. In some case just altering the word order can help; adding or removing a "that"; applying a hyphenation that TeX wouldn't have chosen; … – egreg Apr 6 at 8:58

http://tex.stackexchange.com/a/50838

14. Scroll in the drafted output (refer to Part A) to look for a thick black vertical (with respect to the text direction) line. These thick lines mark the items that exceed the right-hand margin.

See Pic 22 for an example of an overfull figure,
Pic 23 for an overfull sidewaysfigure,
Pic 24 for an overfull table, and
Pic 25 for an overfull text.

Pic 22 - Refer to Step 14. Example of an overfull figure.

Pic 23 - Refer to Step 14. Example of an overfull sidewaysfigure.

Pic 24 - Refer to Step 14. Example of an overfull table.

Pic 25 - Refer to Step 14. Example of an overfull text.

15. When you see the thick line, go the related *.tex file.

Note that these are only suggestions of what-to-do to overcome the badboxes. Adjust accordingly to suit your needs.

A. If it's a figure, scale-down the figure.

B. If it's a table, adjust the cell size, or font size, or wording.

C. If it's texts, adjust the horizontal space for the text, or change the wording, or add hyphenation.

16. Compile the document. Refer to Step 2.

Part G: Fixing the Underfull \hbox badboxes

This fix was inspired by this post:
You should rarely need to use \\ in documents apart from its use in alignments (where it is a macro based on the \cr primitive), and you should rarely need \par in documents as a blank line should suffice.

Source: When to use \par and when \\
http://tex.stackexchange.com/a/82666

The usual mistakes:
The usual mistake is *ending* a paragraph with \\

As I did just above -- with a blank line or \par following after \\. People do this to increase the paragraph separation, when they should instead set \parskip.  The underfull box arises because the paragraph-fill space (\parfillskip) is discarded when a totally empty line occurs.

If you *begin* a paragraph with \\ (\\ after a blank line) LaTeX complains explicitly.

Source: Underfull \hbox (badness 10000) warning

The intent of \\ is to fill with whitespace and produce a linebreak. Maybe you are thinking of \linebreak rather than \\ (or \newline).

Source: Underfull \hbox (badness 10000) warning

Initially I used \\ at the end of paragraphs like in Pic 26.

Then I used \vspace and \par at the beginning of paragraphs like in Pic 27.

In the end I used \vspace and blank lines. I didn't use \setlength{\parskip} because it upsets the spacing-between-paragraphs of the whole document whereas I want it to effect only the chapters; fine-writing the template might be able to make it work as needed. So to obtain the spacing-between-paragraphs, I used \vspace{8.0 mm}. The extra blank lines are for my own readability.

Pic 26 - Using \\ at the end of a paragraph.

Pic 27 - Using \vspace{8.0 mm} \par at the beginning of a paragraph.

17. In the *.tex file, I deleted all \\ and \par and rearranged \vspace{8.0 mm} to be above paragraphs. See Pic 28.

Note that I use \\ in a list or any text that has no blank lines in between. See Pic 29.

Pic 28 - Refer to Step 17. Using \vspace{8.0 mm} and blank lines.
The "Naturals fibers" paragraph is on a new page after a sidewaysfigure, thus explains the absent \vspace{8.0 mm} above the paragraph.

Pic 29 - Refer to Step 17. Using \\ in a list.

18. Compile the document. Refer to Step 2.

The output of Pic 28 is shown in Pic 30

Pic 30 - Refer to Step 18. The output of the paragraph at 100% zoom in Okular.

Alhamdulillah. Wassalam.