Copyright © 2008 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
The XSL 1.1 specification defines the features and syntax for the Extensible Stylesheet Language (XSL), a language for expressing stylesheets. This document enumerates the collected requirements for a 2.0 version of XSL. There are two parts to XSL: XSL Transformations (XSLT) for transformation of documents and XSL Formatting Objects (XSL-FO) for formatting of documents. This is the requirements document for XSL-FO and not for XSLT.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
This is a First Public Working Draft of "Extensible Stylesheet Language (XSL) Requirements Version 2.0" which is expected to become a Working Group Note.
The XSL WG has provided a unique opportunity to provide feedback to the working group through a W3C Requirements Survey found at http://www.w3.org/2002/09/wbs/1/xslfo20requirements/ . Please take the time to fill out the survey and help us understand your priorities for the next release of XSL formatting objects. Additional comments and feedback on individual requirements should be provided using the W3C public Bugzilla system . If access to the bugzilla system is not feasible, you may send your comments to<EMAIL_ADDRESS>. Each bugzilla entry and email message should contain only one error report. It will be very helpful if you include the string [FO2.0Req] in the subject line of your report, whether made in Bugzilla or in email. Archives of the comments and responses are available at http://lists.w3.org/Archives/Public/xsl-editors/ .
This document was developed by the XSL Working Group as part of the W3C XML activity .
This requirements document introduces planned new work for XSL-FO 2.0.
Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. The group does not expect this document to become a W3C Recommendation. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
1 Introduction
1.1 Feedback
1.2 Writing modes
2 Pagination and Layout
2.1 General Region
2.1.1 Non-rectangular areas
2.1.2 Add text to path
2.1.3 Runarounds
2.1.4 Copyfitting
2.1.5 Properties at non-tag boundaries
2.1.6 First line indent on first line of page, region or column
2.1.7 Initial Caps
2.2 Pages
2.2.1 Footnotes
<IP_ADDRESS> Column wide
<IP_ADDRESS> Multiple columns
<IP_ADDRESS> Table footnotes
<IP_ADDRESS> Coalescing footnotes
<IP_ADDRESS> Restart numbering
<IP_ADDRESS> Maximum size
<IP_ADDRESS> Other properties
<IP_ADDRESS> Properties from area tree
2.2.2 Floats
<IP_ADDRESS> Page wide and column wide floats
<IP_ADDRESS> Floats alignment
<IP_ADDRESS> Stack floats
<IP_ADDRESS> Distance of floats
2.2.3 Marginalia
<IP_ADDRESS> Keep marginalia together with other objects
<IP_ADDRESS> Large marginalia
2.2.4 Vertical Positioning
<IP_ADDRESS> Feathering
<IP_ADDRESS> Correlating vertical position
<IP_ADDRESS> Vertical alignment within a page or column
<IP_ADDRESS> Vertical alignment specific for the last column
<IP_ADDRESS> Vertical justification across pages and columns
2.2.5 Tables and lists
<IP_ADDRESS> Decimal alignment
<IP_ADDRESS> Table header/footer on boundaries
<IP_ADDRESS> Split tables
<IP_ADDRESS> Repeat contents of split spanned cell
<IP_ADDRESS> Cell borders extending beyond the table
<IP_ADDRESS> Adjacent borders
<IP_ADDRESS> Borders on break
<IP_ADDRESS> Spanning cell over all row and columns
2.2.6 Side-by-side
2.2.7 Numbering
<IP_ADDRESS> Additional numbering
<IP_ADDRESS> Cross-references to other numbers
<IP_ADDRESS> Calculations with page numbers
<IP_ADDRESS> Multiple sets of page numbers
<IP_ADDRESS> Control increments of page numbers
2.2.8 Cross-references
<IP_ADDRESS> Textual cross-references
<IP_ADDRESS> Cross-reference to a specific region on a page
<IP_ADDRESS> Cross-reference ranges and coalescing
2.2.9 Markers
<IP_ADDRESS> List all markers
<IP_ADDRESS> Organize all markers
<IP_ADDRESS> Coalescing markers
<IP_ADDRESS> Generalized markers
2.2.10 Text before or after a break
2.2.11 Columns
<IP_ADDRESS> Column balancing
<IP_ADDRESS> Column spanning
<IP_ADDRESS> Spanning columns in nested formatting objects
<IP_ADDRESS> Strong vs. weak spanning
<IP_ADDRESS> Multiple columns of different widths
<IP_ADDRESS> Multi-column layout in all regions and block-containers
2.2.12 Layout master set
<IP_ADDRESS> Interleaving layout-master-set
<IP_ADDRESS> Repeatable sub-sequence-specifier
<IP_ADDRESS>
Change master every
n
pages
<IP_ADDRESS> Background content
2.2.13 Variable-sized regions
2.2.14 Adjustable Region Sizes
2.2.15 Binding edge
2.2.16 Multi-directional page collation order
2.2.17 Spreads
2.2.18 Bleeds
2.2.19 Synchronize text of flows
2.2.20 Total block-progression-dimension
2.2.21 Different page geometry based on flows' content
2.2.22 Relationship of two objects
2.3 Feedback from pagination stage
2.4 Document collection
2.4.1 Master index
2.4.2 Hyperlink management
3 Expressions
3.1 Including information from formatting time
3.2 Pagination information
3.3 Output result of expression
3.4 User defined units of measurement
3.5 Getting values of properties
4 Inheritance
4.1 Inheritance down area tree
4.2 Inheritance at reference area boundaries
5 Composition
5.1 Fonts
5.1.1 Improved font support
5.1.2 Unicode ranges
5.1.3 Font dependent on script or language
5.1.4 Font specific features
5.1.5 Kerning
5.1.6 Ligatures
5.1.7 XSL-FO inside other languages
5.2 Force line justification
5.3 Alignment around breaks
5.4 Hanging punctuation
5.5 Tabs and tab stops
5.6 Word and letter spacing
5.6.1 Word and letter spacing exclusions
5.6.2 Punctuation spacing
5.6.3 Specify priority between word and letter spacing
5.7 Hyphenation and line breaking
5.7.1 Number of syllables
5.7.2 Syllable widows
5.7.3 Hyphenation exceptions
5.7.4 Line breaks without hyphen character
5.7.5 Word widows
5.7.6 Minimum length of last line
6 Further improved non-Western language support
7 Images
7.1 Cropping images
7.2 Rotate images in 90 degree increments
7.3 Rotate images over arbitrary angles
7.4 Callouts
7.5 Multi-page images
8 Improvements for specific output formats or devices
8.1 Annotations that appear in output
8.2 Base URL
8.3 Print specific properties
8.4 Marks for paper folding machines
9 Rendering
9.1 Animations with graphics
9.2 Other types of animations
9.3 Z-index
9.4 Border styles
9.5 Rounded corners
9.6 Color support
9.6.1 Transparency
10 Collaboration with SVG
10.1 Masks
10.2 Rotations
10.3 Transformations
11 Other
11.1 Foreign objects
11.2 Metadata on objects
11.3 Generalized metadata
11.4 xml:base
11.5 Schema for XSL-FO
11.6 Compatibility
14 References
The W3C is in the process of developing the second major version of XSL-FO, the formatting specification component of XSL. XSL-FO is widely deployed in industry and academia where multiple output forms (typically print and online) are needed from single source XML. It is used in many diverse applications and countries on a large number of implementations to create technical documentation, reports and contracts, terms and conditions, invoices and other forms processing, such as driver’s licenses, postal forms, etc. XSL-FO is also widely used for heavy multilingual work because of the internationalization aspects provided in 1.0 to accommodate multiple and mixed writing modes (writing directions such as left-to-right, top-to-bottom, right-to-left, etc.) of the world's languages.
The primary goals of the W3C XSL Working Group in developing XSL 2.0 are to provide more sophisticated formatting and layout, enhanced internationalization to provide special formatting objects for Japanese and other Asian and non-Western languages and scripts and to improve integration with other technologies such as SVG and MathML.
A number of XSL 1.0 implementations already support dynamic inclusion of vector graphics using W3C SVG. The XSL and SVG WGs want to define a tighter interface between XSL-FO and SVG to provide enhanced functionality. Experiments with the use of SVG paths to create non-rectangular text regions, or "run-arounds", have helped to motivate further work on deeper integration of SVG graphics inside XSL-FO documents, and to work with the SVG WG on specifying the meaning of XSL-FO markup inside SVG graphics. A similar level of integration with MathML is contemplated.
The XSL WG has provided a unique opportunity to provide feedback to the working group through a W3C Requirements Survey found at http://www.w3.org/2002/09/wbs/1/xslfo20requirements/ . Please take the time to fill out the survey and help us understand your priorities for the next release of XSL formatting objects. Additional comments and feedback on individual requirements should be provided using the W3C public Bugzilla system . If access to the bugzilla system is not feasible, you may send your comments to<EMAIL_ADDRESS>. Each bugzilla entry and email message should contain only one error report. It will be very helpful if you include the string [FO2.0Req] in the subject line of your report, whether made in Bugzilla or in email. Archives of the comments and responses are available at http://lists.w3.org/Archives/Public/xsl-editors/ .
We use terms like top, bottom, vertical and horizontal in this document to be easy to understand. We know that when we write the specification, we have to talk in terms of before, after, start, end, block-progression-direction, inline-progression-direction etc, the same as XSL 1.0 and 1.1 did.
Add support for non-rectangular areas wherever appropriate. This is for areas where the content needs to be flowed inside an non-rectangular shape.
Run text on a path including flowing from one path to another. This goes further than simply including SVG, as we're also supporting the line breaking rules that XSL-FO provides. Text should be able to flow from one line to the next line of the multiline paths but it needs to be explicitly specified what each line of the path is, as we do not intend to stack paths automatically. The intent is to apply the normal line building properties to text on a path.
Add support for runarounds or intrusions (text flowing around illustrations, regions and other objects). This is related to effects obtained by overlapping areas of either rectangular or non-rectangular shape in any suitable combination, but it doesn't really require non-rectangular areas.
Allow one object to intrude into another:
Support multiple intrusions
Support intrusions into all 4 sides
Support specifying pull-quotes without the need to repeat the content of the pull-quote. This is related to <IP_ADDRESS> Generalized markers
Support cut-outs
The objects (both the intruder as well as the object intruded upon) may be of arbitrary shape.
Allow users to specify the relations between the objects that are impacted by the intrusion:
Specify where the objects should be positioned. The objects may be relatively or absolutely specified.
Specify separation/gap between intruders & other regions.
The intruder's size may be pre-defined or specified dynamically. It may be a region or a flowing object. An example of a dynamically sized object is a pullquote where the size of the pullquote depends on the amount of text, or a graphic where the size of is dependent on the external graphic.
Specify a priority between objects
Specify a keep/anchor between the text and the intruder. This is related to 2.2.22 Relationship of two objects
Add support for copyfitting, for example to shrink or grow content (change properties of text, line-spacing, ...) to make it constrain to a certain area. This is going to be managed by a defined set of properties, and in the stylesheet it will be possible to define the preference and priority for which properties should be changed. That list of properties that can be used for copyfitting is going to be defined.
Additionally, multiple instances of alternative content can be provided to determine best fit.
This includes copyfitting across a given number of pages, regions, columns etc, for example to constrain the number of pages to 5 pages.
Add the ability to keep consistency in the document, e.g. when a specific area is copyfitted with 10 pt fonts, all other similar text should be the same.
Add support for specifying the properties on the specified number of lines or certain parts in areas, e.g. the first 5 cm of the area should be in bold.
Allow users to specify that first line indent should be different on the first line of a page, region or column. This is a specific case of 2.1.5 Properties at non-tag boundaries and is also related to 5.3 Alignment around breaks .
Add support for raised initial capitals and n -line dropped capitals. This includes support for the first n characters. See also 2.1.5 Properties at non-tag boundaries .
Add support for multiple columns in the footnote region, where the number of columns may be different from the number of columns in the page.
Add support for table footnotes. These are footnote bodies that get rendered within the table (as opposed to at the bottom of the page) when the footnote reference appears on the table fragment on that page.
Add support for coalescing footnotes. This means that the same footnote should only be shown once when it appears multiple times on the same page.
Allow users to specify the maximum size of the footnote area in relation to the body and for footnotes to continue on the next page.
Allow users to specify other properties of the footnotes, such as margins, spacing etc.
Add support for specifying properties such as the fontsize of footnotes to be taken from the area tree, instead of from the formatting object tree. This is related to 4 Inheritance .
Improve support for floats. Currently we can only float to the top.
We should differentiate page wide, column wide or n -column wide floats.
Add support for marginalia.
Keep marginalia together with other objects, such as blocks or inlines. We should specify the alignment of the marginalia, as this is typically a smaller font size. For example align the baselines, align the top of the two lines, etc. Support a variety of positions of marginalia, e.g. position them at the left on a left-hand page and at the right on a right-hand page.
Note:
In some cases, marginalia are seen as an alternative to footnotes, so some footnote properties should also apply to marginalia, for example numbering and restarting numbering.
The following graphic show an examples of marginalia:
The following picture shows collision of 2 marginalia:
This graphic shows marginalia on the two sides of the flow:
This graphic shows an example of the relative alignment of the marginalia and the text. At the top of the page, the first lines of the marginalia and the text are aligned at the before-edge. When in the middle of the page, the first line of the marginalia and the corresponding line of the text are visually aligned on a particular baseline (in the case of mixed text).
If marginalia become larger than the space on the page, they should force the text and/or the related marginalia to move to the following page. Also permit breaking of marginalia.
This graphic is showing the situation where some breaking is preferable:
This graphic shows one solution, by breaking the flow so that the entire marginalia is brought to the next page, together with the text it belongs to:
This graphic shows another solution, by breaking the marginalia:
Add support for feathering, to vertically adjust lines. Feathering is vertical justification with very small amounts.
Add support for correlating vertical position so that lines of text on two adjacent pages, columns or regions are visually next to each other. Also support alignment of the two sides of the same sheet, so that the lines of text on the back side and front side of the sheet are aligned (this is a common requirement when the sheets of paper are very thin).
Add support for vertical alignment, such as centering the content of the columns or aligning to the bottom within pages, regions or columns.
To improve decimal alignment, extend the character alignment in table cells to permit a specification of the horizontal position of the alignment point within the column.
Be able to specify different instances of what the table header or footer should be depending on the different boundaries (page, column and region). This also would allow specifying that certain headers must be omitted at certain boundaries.
Allow users to specify that tables can be split horizontally. It should be possible to have a column repeated when the table is split horizontally, by specifying a row header. There should be a way to keep the split parts visually next to each other depending on binding edge.
In case a table is split over multiple pages and both the rows and columns don’t fit a page, allow users to specify which table part comes out in which order (rows first or columns first).
This graphic shows a table before it is split. Neither all of the rows, nor all of the columns fit on one page, so the table needs to be split.
The following graphics show 4 pages that contain the split table. The order in which the pages will come out depends on the users preference, and the two alternatives are marked with green (columns first) and blue (rows first) numbers.
Allow users to specify that when a spanned cell in a table is split, the entire cell contents should be repeated on each table instance. This applies to splitting as well as spanning in the block-progression-direction as well as the inline-progression-direction.
Allow the column lines to extend down or right the table to visually indicate that the table continues. When this happens, any vertical border should be extended beyond the bottom border for the last row or right column.
When one formatting object is immediately preceding another in block-progression-dimension, be able to specify what to do with their adjacent borders.
Allow having different borders when a break occurs so that a formatting object is split, e.g. a cell that splits, have a thinner border for the split.
The current specification of XSL says that number-rows-spanned and number-columns-spanned should be a positive integer. Other specifications, such as HTML 4.01, allow 0 as a value, which means that all rows or columns of the current table section are spanned over. This behavior may be added to XSL 2.0, either by allowing 0 as a value, or some other solution.
Introduce a way to position objects next to each other. Side-by-side includes complex positioning and breaking rules (in some cases similar to the constraints necessary for marginalia).
Add support for line number, column number and region number. For example number only every fifth line, etc.
The following are requirements for line numbers, but they apply to columns numbers and region numbers as well:
Line numbering side (start/end/...)
Line numbering separation -- distance of number from the text
Line numbering format (1, 2, 3...; 001, 002, 003...; A, B, C...)
Line numbering text properties (font-family, font-size, ...)
Starting line number -- 1 by default, but can be changed by user
Continuation -- should numbering continue from previous object, or should be restarted
Line numbering restart -- where numbering restarts (document, page-sequence, object, page, column)
Line number only each n -th number
Line number separator
Line number alignment
Allow users to make cross-references to anything that can be numbered, such as the numbers introduced in <IP_ADDRESS> Additional numbering .
It should be possible to do calculations with page numbers. For example to determine the number of pages in a section.
Have multiple series of page numbers in the whole document that can be output on selected pages (even outputting multiple page numbers on the same page). As an example, take the case where a document contains both a letter and a contract. In that case, you want to be able to have a page number starting from 1 for the entire document, that is also output on all pages, as well as a page number starting from 1 for just the contract that is only output on the pages of the contract.
Specify that page numbers should not increment on certain pages.
For example, the case where back side containing the 'conditions of sale' shouldn't be numbered and thus the page number shouldn't be incremented. A document containing 4 pages, page 1 with page number '1', page 2 being the back side of page 1 containing conditions of sale and not numbered, page 3 with page number '2', page 4 being the back side of page 3 containing conditions of sale and not numbered again. What is actually being accomplished is simulating printing a 2 page document (with page numbers 1 and 2) on 2 sheets of preprinted paper, each containing the conditions of sale on the back side.
We want the formatter to detect where the cross-referenced object is located (e.g. where on the page, or on which page such as the previous page). We want to allow the insertion of variable text for cross-references depending on both the page number on which the cross-reference appears and the target page, for example 'see previous page' or 'see opposite page'.
Extend retrieve-marker and retrieve-table-marker to enable listing all markers on the page (e.g. to list all index terms on the page or show a list of destinations in a list of hotels). Provide in a way to ‘carry-over’ the markers from previous (not following) pages. This should be done in all cases, not just in the case the current page contains no markers.
When retrieving all markers of a page, add the ability to organize them. This includes removing duplicates, sorting markers and indicating how to format them (e.g. each marker on a separate line or separated with commas).
Markings at particular page, column, table (horizontal and vertical) or region breaks. For example add text ‘continued on next page’ or ‘continued from previous page’. The text may be just fixed text, or retrieved from the page or a cross-reference.
Allow the span property to have effect when specified on formatting objects that are not direct children of an fo:flow.
Be able to define layout-master-sets not only at the top of the FO tree, but also interleaving page-sequences, to allow users to define and change masters, such as simple-page-master and page-sequence master, on the fly instead of having to specify all the masters in the beginning of the FO tree. When traversing the FO tree in pre-order traversal, the master must be defined before it may be referenced by a master-reference property.
Have sets of pages repeatable within the same page-sequence.
Allow specifying that every n -th page, a different master should be used. This is a specific case of <IP_ADDRESS> Repeatable sub-sequence-specifier . For example, use master A for page 1, 2, 3, 4, then master B for page 5, then master A again for 6, 7, 8, 9 then master B for page 10, etc...
Dynamically size the region-start, -end, -before and -after so that it sizes according to the content of the region. This may well be not applied to the current simple-page-master. This is a simple case of 2.2.14 Adjustable Region Sizes for the case where the page has a typical 'border layout'.
Support specifying which edge remains in its original position and which edge moves when the region grows (or multiple edges may move). This applies to all of the dimensions. Related to this is the notion of an anchored edge that can be anchored with respect to the page or with respect to another area. Some overlapping may occur with other regions that aren’t part of the specified constraints. The anchors are related to 2.2.22 Relationship of two objects
Add support for specifying the binding edge. This is related to duplex/simplex of 8.3 Print specific properties .
Add support for multi directional page collation order in a single document. For example a single book where the front part starts in one language and the backside starts from another language. Another example is that of Japanese magazines that combine vertical layout from the back and horizontal layout from the front.
Be able to treat two facing pages (a two page spread) as a single unit. For example to allow images to cross the page boundaries.
Add support for bleeds. For example, bleeds allow an image to go beyond the page boundaries so that when you print, bind and cut the paper you don’t have any white space showing. It has got to be in the context of the output media, so this is related strongly to 8.3 Print specific properties .
Synchronize the text of flows that have a relationship to each other, and specify how near or how far they can go from each other. The relationship between the text of the two flows may also be expressed using some form of anchors. This is related to 2.2.22 Relationship of two objects .
For example, this is needed to keep two translated paragraphs next to each other in a two column document where one column is in one language and another column in another language.
Allow users to specify the sum of the block-progression-dimensions of the generated areas instead or in addition to specifying the block-progression-dimension of each generated instance.
Support different page geometries based on the flows that have been exhausted and those that have still content to be placed. For example, when having two regions A and B, both laid out next to each other on a single page, once flow A is exhausted, make B use the entire available space on the page.
Give the ability to use information from the pagination step of one formatting episode in determining layout of the following formatting episode. This ability also allows making changes to the pages, reordering pages, merging multiple flows and do many other post processing tasks. One example of using XSL-FO for this is by representing the result of the first formatting episode each formatted page in a separate page-sequence, so that when this XSL-FO instance is fed into an XSL-FO formatter again, the same amount of pages would be generated as there are page sequences in the XSL-FO instance.
As a specific example, take the process that involves sending out a letter followed by a contract for a large number of customers. This involves an envelope machine that will take the individual sheets of paper and put them in an envelope. This process has the additional constraint that an envelope can only hold n pages, so when the letter + contract contain more than n pages, and extra sheet of paper must be produced that contains the address again, so that this contract can be sent in multiple envelopes. This envelope machine is typically driven by OMR marks, which are lines or markings on the paper that indicate which is the first/last page of the envelope. These markings typically also include a checksum that contains the sheetnumber so that the envelope machine can detect when it took two sheets at the same time. Adding these markings to the output involves logic that needs to know how many pages are generated.
The working group will investigate relationships between multiple input documents and multiple output documents.
The term 'document collection' refers to a document that is actually composed of multiple documents. Once this concept of ‘document collection’ is defined, we can add features that need the relationships between multiple documents such as a master index or hyperlink management.
Modify the expression language to allow expressions that include information that’s only available at formatting time.
Some examples of this are the size of a block, the height of a line, etc.
Be able to compute expressions that are based on information that is only available after the pagination stage. For example, this allows to calculate the subtotal of the current page (as opposed to a running total that is already supported in XSL 1.1 with table markers). Once this expression can be calculated, you can use 3.3 Output result of expression to output its result .
Allow users to output the result of expressions on area tree, traits, markers or text content. For example to calculate the subtotal of a certain page (as opposed to a running total that is already supported in XSL 1.1 with table markers).
Inheritance of properties down the area tree (as opposed to the formatting object tree in previous versions of XSL).
One example of this is inheritance with footnotes that should inherit the properties of the footnote are as opposed to the properties of the area in the body that contains the referenced text.
Another example is the case where there are two regions on a page that contain the flowed text (text is flowed for to Region A, then to region B). Region A has a black background and region B has a white background. The text color should be white in region A and black in region B.
This may include SVG font capabilities, such as referring to an external font pointed to with a URI, or being able to define fonts like SVG fonts. For more information on SVG fonts, see Chapter 20 of SVG 1.1 .
Use a different font-family (already supported by SVG) and different font-size (not yet supported by SVG) for characters depending on the Unicode range.
Make font-size and font-family dependent on the script or language.
Add additional properties to give access to font specific features, e.g. in initial swash caps, oldstyle figures, and/or other features such as those available in OpenType.
Allow users to specify constraints to control ligatures, like forcing the use of ligatures, or avoiding the use of ligatures even though they are available. This requirement includes the large number of parameters that may be necessary to control ligatures for those languages where the ligatures are font dependent, such as Arabic.
Allow users to force line justification when the line length is within a certain range. For example, normally the last line of a paragraph would not be justified, but if the last line is longer than a certain threshold, justify it anyway.
Currently XSL has justification parameters for 'all text but the last line' and the 'last line'. Add properties to specify what the alignment should be for the 'last line before a break' and the 'first line after a break'.
Add support for hanging punctuation, both for western as non-western languages.
Add support for tabs and tab stops that people are used to from word processors. The main requirement for this seems to be compatibility with other formats, mainly word processor formats.
Allow excluding specific characters or Unicode classes (for example numerals) from word and letter spacing.
The following set of requirements is related to hyphenation. All hyphenation settings need to be language-dependent so that you can set different values for the various languages you use in a given document.
Allow specifying the number of syllables in addition to the number of characters to control hyphenation.
Note:
We are concerned how to divide things reliably in syllables. (This requirement comes from the Print Workshop in Heidelberg.)
Add syllable level widow and orphan controls. We can only do this if we implement 5.7.1 Number of syllables .
Allow specifying language-specific hyphenation exceptions. This could for example be done by providing a pointer (e.g., <uri-specification>) to a list of language-specific hyphenation exceptions.
Allow the specification of a set of characters after which the composition process may introduce a line break without inserting a hyphen character. For example for '/' characters in URLs.
Improve support for non-Western languages, such as Mongolian, Indic languages, Thai, Japanese, Chinese, etc. The working group invites language experts to identify language specific features that are currently not yet supported by XSL.
Specifically, the Japanese Layout Taskforce is creating a document about requirements for general Japanese layout realized with technologies like CSS, SVG and XSL-FO. The document is currently in draft stage and is being developed further by the Japanese participants in the task force. This document will be an input to the XSL working group as a source of requirements.
This document will be an input to the XSL working group as a source of requirements.
Cropping images, including bleed and non-rectangular cropping. See 2.2.18 Bleeds and 10.1 Masks .
Add support for adding annotations that appear in the output, e.g. comments or text highlighting in PDF.
Add support for setting the base URL for output formats that support this, such as PDF or HTML.
Specifying print specific properties such as the following.
Input/output trays
Duplex/simplex
Dpi depending on output format
Grayscaling or patterns or colors
Glossy paper (has influence on formatting as well)
Crop marks
Registration marks
Bleeds (also described at 2.2.18 Bleeds )
This will probably be done with a Job Control specification such as JDF.
Add support for animations contained within the graphics.
Note:
This could be related to 10 Collaboration with SVG .
Add support for other types of animation. For example an ant crawling around the borders of a table, a business chart with drilldown/zoom functionality, go to next page every 3 seconds.
Note:
This could be related to 10 Collaboration with SVG .
Improve absolute position, layering and positioning by extending the Z-index property so that it can cross formatting object boundaries. Also support z-index on regions (also required for more complex page layout).
You should be able to specify these border styles for individual borders or individual corners. Patterns may be segmented, so that we have different borders for the corners etc.
Add support for extensible border patterns, e.g. with numbers and thicknesses of lines, dashes.
Tiled graphics and images as borders, for example, for borders typically surrounding a stock certiticate.
For XSL-FO 2.0 we want to have a close collaboration between the XSL and SVG working groups. Wherever possible we will try to use SVG functionality rather than reinventing our own. Working with SVG is part of the solution to other requirements outlined in this document.
By implementing XSL-FO and SVG, some of the extra conformance criteria that apply are inheritance at language boundaries, SVG transformations of XSL-FO result renditions, nesting languages.
One example of how SVG and XSL-FO can be used is shown in this picture, coming from the SVG Print 1.2 Primer dated 21 December 2007 .
Improve the embedding of foreign objects inside XSL-FO to allow a tighter coupling. Examples of these are SVG, MathML, XForms, etc.
Specify metadata that may influence the output, like PDF keywords, producer, etc., or be used for other purposes.


3 men arrested for murder of 15-year-old girl in KZN
by Kamva SomdyalaKwaZulu-Natal police have arrested three men who allegedly murdered 15-year-old Cebisile Luphondwe, burnt and then buried her body in a shallow grave outside a farm in Glencore.
The police claimed Luphondwe and her boyfriend might have had an argument on Monday afternoon after which she was allegedly assaulted and stabbed to death.
Provincial spokesperson Colonel Thembeka Mbele said her body was burned and buried in a shallow grave outside the farm in Glencore.
"Family members opened a missing persons docket after she did not return home," added Mbele.
The victim's boyfriend, aged 23, was arrested in Ladysmith.
"Upon investigation, two more suspects, aged 28 and 29, were arrested for murder."
"The swift response of the integrated team in making sure that the alleged murderers were brought to book is highly commended.
"We are appealing to residents to allow the police to conduct their investigation freely and not to take the law into their own hands," said KwaZulu-Natal provincial commissioner Lieutenant General Khombinkosi Jula.
Last month, a KwaZulu-Natal teacher was arrested for allegedly kidnapping and murdering a 12-year-old pupil.
The teacher, 28-year-old Sanele Ngubane, is alleged to have arranged a meeting with pupil Lwazi Tembe from Thengane Reserve.
Lwazi's body was discovered in a shallow grave on a sports field in Emanguzi, News24 previously reported.


BY EDWIN JAHIEL
BORN YESTERDAY (1993)** Directed by Luis Mandocki. Written by Douglas McGrath, based on the play by Garson Kanin. Photography, Lajos Koltai. Editing, Lesley Walker. Production design, Lawrence G. Paull. Music, George Fenton. Cast: Melanie Griffith, John Goodman, Don Johnson, Edward Herrmann, Max Perlich, Fred Dalton Thompson, Nora Dunn, Benjamin C. Bradlee, Sally Quinn, et al. Released by Hollywood Pictures. 102 minutes., Rated PG (language)
Two movies by Mexicans in one week: Maria Novaro directs the Mexican ³Danzon² and Luis Mandocki (³Gaby-a True Story² and ³White Palace²) directs ³Born Yesterday.²
In 1946, Garson Kaninıs ³Born Yesterday² was a Broadway hit. In 1950 it became a movie directed by George Cukor. Both works made a star of Judy Holliday. The current ³Born Yesterday² claims to be based on the play, but it is closer to the movie.
I am getting tired of comparing originals and remakes, as I have done recently for ³Sommersby,² ³The Vanishing² and ³Point of No Return.² This time, I will make only passing remarks.
The 1950 film is by far the better of the two. It is also good in itself, even though the comparison is, understandably, making some critics overpraise the original. The new version, though only fair, does make an unboring time-passer.
Crass and shady millionaire Harry Brock (John Goodman) goes to Washington in order, not to clean it up like Mr. Smith, but to push some crooked senators already on his payroll into saving a military base adjoining his mammoth development. He is accompanied by his mistress Billie Dawn (Melanie Griffith), a ditsy blonde ex-Vegas hoofer whom he loves but treats like dirt. Also with him are his "consigliere" Edward Herrmann and Harryıs nephew Max Perlich.
In a world of luxury, name-dropping, phony chic and dachshund limos, and in a series of scenes -- some funny, others not -- Billieıs unbelievable mega-stupidity and ignorance prove to be embarrassments. Harry hires smarty-pants journalist Paul Verrall (Don Johnson) to tutor her. At first Paul refuses, but then a $500 a day fee (plus expenses, I would imagine) overcomes his principles.
Even a pea-brain can guess what will happen, starting with Billieıs ³I donıt want some stuffy old tutor.² Guess whom the camera shows next? Right away, she makes blatant passes at Paul, and after some bits oı business (funny and non-funny)Billie blooms instantly into wisdom, learning and Paul-crush.
She asimilates learning with the speed of a movie E.T., learns about the Constitution, reads Tocqueville, discusses him -- when in reality she might have learned, at the very most, to speak like tabloid headlines. Educating Eliza Doolittle or Rita was credible, but educating Billie?
The hors-dıoeuvre to this menu is in ³Being There² mode, as Billie learns the eight responses for all occasions. Cued by Paul, she applies them. Itıs dumb, itıs entertaining, and it includes the goof ³Thatıs about as funny as a Democrat being elected President. ² The movie must have been made during the Bushian post-Desert Storm glow.
Among the howl-inducers is Billieıs profundity. She contemplating a Van Gogh in a museum. ³Itıs so small but it feels bigger than the whole room.² Another is her mnemotechnical trick to remember Constitutional Amendments. At a posh Washington restaurant she sings them to the tune of ³The Twelve Days of Christmas² with band and co-eating celebrities obligato. Just recalling this can make one blush from embarrassment.
Meanwhile, back at a dude ranch, Paul has been falling for Billie faster than the "blitzkrieg,"the lightning-fast initial German victories in World War II. This is infinitely less credible than in the 1950 edition. But then Paul himself is unbelievable, a pallid character with a deep tan that keeps reminding you that you are watching Don Johnson, a.k. a. Mr. Melanie Griffith, Hollywood Actor, here transferred from the streets of Miami to the power corridors of Washington Vice.
Everything is telegraphed and marked like runway lights in an airfield. Itıs no surprise that the pliant Billie (in whose name Harry has most of his properties) will rebel and show Harry and Washington a thing or two.
She also shows her legs. I had not intended to see this film until I saw an ad that showed, intriguingly, a pair of beautiful legs with a manıs leg (contortionism?) draped over the gams (a word used in the original playıs period). My curiosity was not libidinous but nostalgic and cine-referential : the photograph somehow brought memories of ³The Graduate²ıs poster and Mrs. Robinson.
Lackaday! Even if Billie becomes a graduate of sorts, this movie is no ³Graduate.² But it does have some small surprises. Item. The legs in the photograph must be those of a body double. Item. Don Johnson is short, shorter even than Melanie. I bet that, as in Alan Ladd pictures, they used a lot of boxes and special camera angles to play down the differences in size. Item. Edward Herrmann is wasted. Item. In his microscopic role, the small Max Perlich is totally superfluous. Perhaps he was edited out in the final cut. Perhaps Perlich knew somebody.
Item. Goof or subtlety? Paul, a writer and savant who also teaches at Georgetown, tells Billie: ³If I get involved with you Iım no different THAN Harry.² Billie, seconds later: ³Youıre no different FROM Harry.² (Capitalization mine).
Item. Paul: ³Hello, how have you been?² Billie: ³Very GOOD And you?² Paul: ³Pretty GOOD.² To think that in spelling bees, some kids age 11 to 13, in my town, can spell ³sporran,² ³cerography, ² ³zaibatsu² or ³wapentake.²
Among the sins of ³Born Yesterday². First, not any two characters ever connect or show rapport. Secondly, Johnson and Goodman are both miscast, the first being made into a phony intellectual, the second into a massive, crude ball of dumbness that lacks the nastiness of his predecessors, Paul Douglas on the stage, Broderick Crawford on the screen. This Harry is so ludicrous that his contorsions on a dance floor conjure up Barnum and Baileyıs kneeling elephants.
The movie misses a major opportunity : to illustrate that a little knowledge is a dangerous thing by taking many of the Washington celebs who scoffed at Billie and expose them as mere possessors of tidbits and veneers, morsels handy for posing as smart, educated, literate or chic. In the kingdom of the blind, one-eyed people are kings. Thereıs a whole comedic expose to be made on this subject.
"BY"has an ostentatious look of unbridled capitalism and profiteering. The hotel where much of the action takes place is the luxurious Willard, gutted in 1986 and restored as the Willard-Intercontinental. But Harryıs imperially Presidential penthouse suite is an imaginary construct of 4,000 square feet where charges for a few days can be more than the average Americanıs yearly salary. The skillful setup of this suite allowed a great deal of camera mobility and deep-focus shots.
The better news is that overall the picture does not bore and does entertain, even though there are no major laughs, because, perhaps of the underlying, mean-spirited mood of the picture.
The Golden Raspberry Foundation has awarded Melanie Griffith the prize for Worst Actress of the Year (for ³Shining Through² and ³ A Stranger Among Us²). But now she redeems herself as the best of four choices to replace Judy Holliday. Melanie, a Black Belt among cerebrally challenged stars, fits her part so effortlessly here that you are not even conscious of her notorious little-girl voice. But then again, Judy Holliday convinced us that inside her uncultured dumdum persona a smart, sharp ³natural² was waiting to come out. With Melanie Griffith, this takes a leap of faith.
Written April 6, 1993
" Le mauvais gout mene au crime" (Stendhal)
Edwin Jahiel's movie reviews are at http://www.prairienet.org/ejahiel
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


| Interface | Description |
|---|---|
| ComponentRegistry |
Represents the registry of all components allowing them to be registered for injection.
|
| Converter<T> |
Converts a string value to an object.
|
| Result |
A resource requisition result.
|
| TwoWayConverter<T> |
A converter that also converts an object to a safe string.
|
| Validator |
A validator interface for vraptor3.
Based on hamcrest, it allows you to assert for specific situations. |
| View |
| Class | Description |
|---|---|
| VRaptor |
VRaptor entry point.
Provider configuration is supported through init parameter. |
| Exception | Description |
|---|---|
| InterceptionException | |
| VRaptorException |
The base
Exception type for VRaptor. |
| Annotation Type | Description |
|---|---|
| Consumes |
Indicates that the resource method expects the specified MIME content-types
in the request.
|
| Convert |
Registers a class as a converter.
|
| Delete |
Supports the DELETE http method.
|
| Get |
Supports the GET http method.
|
| Head |
Supports the HEAD http method.
|
| HeaderParam | |
| Intercepts |
Notifies vraptor to use this interceptor in the interceptor stack.
Interceptors annotated are run in any order, therefore if the sequence is important to your project, use an annotated InterceptorSequence. |
| Lazy |
Identifies that given class should be used with a lazy strategy.
|
| Options |
Supports the OPTIONS http method.
|
| Patch |
Supports the PATCH http method.
|
| Path |
Sets a custom path to allow web requisitions to access this resource.
To be used together with web methods annotations as Get, Post and so on. |
| Post |
Supports the POST http method.
|
| Put |
Supports the PUT http method.
|
| Resource |
Resources are entry points for requests; i.e, requests are handled by VRaptor Resources.
|
| Trace |
Supports the TRACE http method.
|
Copyright © 2013 Caelum. All Rights Reserved.


{% extends "free_software.html" %} {% block logo %} {% endblock %} {% block software %}
Twilio is the easiest way to send SMS messages and/or interact with phones from your application.
Twilio has a program for social good organizations (like you!) which provides $500 in credit and a permanent 25% discount.
You will have to sign up for a normal account, and then fill out the application form. Send us an email at<EMAIL_ADDRESS>if you end up applying, we’d like to know if you find Twilio useful, and we can help make sure you get approved!
{% endblock %}


cpp-netlib includes and implements a number of HTTP clients that you can use and embed in your own applications. All of the HTTP client implementations:
- Cannot be copied. This means you may have to store instances of the clients in dynamic memory if you intend to use them as function parameters or pass them around in smart pointers or by reference.
- Assume that requests made are independent of each other. There currently is no cookie or session management system built-in to cpp-netlib’s HTTP client implementations.
- Are header-only and are compiled-into your application. Future releases in case you want to upgrade the implementation you are using in your application will be distributed as header-only implementations, which means you have to re-compile your application to use a newer version of the implementations.
The HTTP clients all share the same API, but the internals are documented in terms of what is different and what to expect with the different implementations.
There is a single user-facing template class named basic_client which takes three template parameters:
- Tag - which static tag you choose that defines the behavior of the client.
- http_version_major - an unsigned int that defines the HTTP major version number, this directly affects the HTTP messages sent by the client.
- http_version_minor - an unsigned int that defines the HTTP minor version number.
There are two major different class of implementations of the basic_client template that depend on which tag you choose: Synchronous Clients and Asynchronous Clients. These two different classes are described in their own sections following this one. What follows is a table of all tags supported by the HTTP client implementation provided by cpp-netlib.
| Tag | Description |
|---|---|
| http_default_8bit_tcp_resolve | This is the default HTTP implementation tag that resolves addresses with a TCP resolver and provides a synchronous/blocking HTTP client interface. |
| http_default_8bit_udp_resolve | This is similar to the above tag except that it specifies the HTTP client to use a UDP resolver. It also provides a synchronous/ blocking HTTP client interface. |
| http_keepalive_8bit_tcp_resolve | This tag specifies that the HTTP client by default will keep connections to the server alive. It only makes sense if the version_major and version_minor are both 1, to indicate HTTP 1.1. This tag causes the HTTP client to resolve using a TCP resolver and provides a synchronous/ blocking HTTP client interface. |
| http_keepalive_8bit_udp_resolve | This is similar to the above tag except that it specifies the HTTP client to use a UDP resolver. It also provides a synchronous/ blocking HTTP client interface. |
| http_async_8bit_tcp_resolve | This tag provides an active HTTP client object implementation that uses a TCP resolver. Response objects returned will encapsulate a number of Boost.Thread shared futures to hold values. Users don’t have to see this as they are implementation details. |
| http_async_8bit_udp_resolve | This is similar to the above tag except that specifies the HTTP client to use a UDP resolver. |
In the above table the tags follow a pattern for describing the behavior introduced by the tags. This pattern is shown below:
<protocol>_<modifier>_<character-width>_<resolve-strategy>
For example, the tag http_default_8bit_tcp_resolve indicates the protocol http, a modifier default, a character width of 8bit, and a resolve strategy of tcp_resolve.
Of the client tags shown in the table, the following makes the basic_client behave as a fully synchronous client.
- http_default_8bit_tcp_resolve
- http_default_8bit_udp_resolve
- http_keepalive_8bit_tcp_resolve
- http_keepalive_8bit_udp_resolve
The synchronous client implements all the operations of the client underneath the interface all block to wait for I/O to finish. All the member methods are synchronous and will block until the response object is ready or throws if erros are encountered in the performance of the HTTP requests.
Warning
The synchronous clients are NOT thread safe. You will need to do external synchronization to use synchronous client implementations.
The following tags specify the basic_client to behave in an asynchronous manner:
- http_async_8bit_tcp_resolve
- http_async_8bit_udp_resolve
An asynchronous client implementation means that``basic_client<...>`` is an Active Object. This means that the client has and manages its own lifetime thread, and returns values that are asynchronously filled in. The response object encapsulates Boost.Thread futures which get filled in once the values are available.
The asynchronous clients implement all operations asynchronously which are hidden from the user. The interface is still synchronous but the fetching of data happens on a different thread.
Note
The asynchronous clients are thread safe, and can be shared across many threads. Each request starts a sequence of asynchronous operations dedicated to that request. The client does not re-cycle connections and uses a one-request-one-connection model.
In this section we assume that the following typedef is in effect:
typedef boost::network::http::basic_client<
boost::network::http::tags::http_default_8bit_udp_resolve
, 1
,1
>
client;
Also, that code using the HTTP client will have use the following header:
#include <boost/network/include/http/client.hpp>
The client implementation can be default constructed, or customized at initialization.
| [1] | In Asynchronous Clients, redirects are not followed. This means the response objects will contain whatever HTTP response was retrieved by the client implementation. |
| [2] | In Asynchronous Clients, only caching resolved endpoints take effect. |
The client implementation supports various HTTP methods. The following constructs assume that a client has been properly constructed named client_ and that there is an appropriately constructed request object named request_ and that there is an appropriately constructed response object named response_ like the following:
client client_();
client::request request_("http://cpp-netib.github.com/");
client::response response_;


Chapter 6. Email Quotes and Inclusion Conventions
Part I. Introduction
One area where conventions for on-line writing are still in some flux is the marking of included material from earlier messages — what would be called ‘block quotations’ in ordinary English. From the usual typographic convention employed for these (smaller font at an extra indent), there derived a practice of included text being indented by one ASCII TAB (0001001) character, which under Unix and many other environments gives the appearance of an 8-space indent.
Early mail and netnews readers had no facility for including messages this way, so people had to paste in copy manually. BSD Mail(1) was the first message agent to support inclusion, and early Usenetters emulated its style. But the TAB character tended to push included text too far to the right (especially in multiply nested inclusions), leading to ugly wraparounds. After a brief period of confusion (during which an inclusion leader consisting of three or four spaces became established in EMACS and a few mailers), the use of leading > or > `` became standard, perhaps owing to its use in ed(1) to display tabs (alternatively, it may derive from the ``> that some early Unix mailers used to quote lines starting with “From” in text, so they wouldn’t look like the beginnings of new message headers). Inclusions within inclusions keep their > leaders, so the ‘nesting level’ of a quotation is visually apparent.
The practice of including text from the parent article when posting a followup helped solve what had been a major nuisance on Usenet: the fact that articles do not arrive at different sites in the same order. Careless posters used to post articles that would begin with, or even consist entirely of, “No, that’s wrong” or “I agree” or the like. It was hard to see who was responding to what. Consequently, around 1984, new news-posting software evolved a facility to automatically include the text of a previous article, marked with “> ” or whatever the poster chose. The poster was expected to delete all but the relevant lines. The result has been that, now, careless posters post articles containing the entire text of a preceding article, followed only by “No, that’s wrong” or “I agree”.
Many people feel that this cure is worse than the original disease, and there soon appeared newsreader software designed to let the reader skip over included text if desired. Today, some posting software rejects articles containing too high a proportion of lines beginning with ‘>’ — but this too has led to undesirable workarounds, such as the deliberate inclusion of zero-content filler lines which aren’t quoted and thus pull the message below the rejection threshold.
Inclusion practice is still evolving, and disputes over the ‘correct’ inclusion style occasionally lead to *holy wars*.
Most netters view an inclusion as a promise that comment on it will immediately follow. The preferred, conversational style looks like this,
or for short messages like this:
Thanks to poor design of some PC-based mail agents (notably Microsoft Outlook and Outlook Express), one will occasionally see the entire quoted message after the response, like this
but this practice is strongly deprecated.
Though > remains the standard inclusion leader, | is occasionally used for extended quotations where original variations in indentation are being retained (one mailer even combines these and uses |>). One also sees different styles of quoting a number of authors in the same message: one (deprecated because it loses information) uses a leader of > `` for everyone, another (the most common) is ``> > > >, > > > ``, etc. (or ``>>>> ``, ``>>>, etc., depending on line length and nesting depth) reflecting the original order of messages, and yet another is to use a different citation leader for each author, say > ``, ``: ``, ``|, @ (preserving nesting so that the inclusion order of messages is still apparent, or tagging the inclusions with authors’ names). Yet another style is to use each poster’s initials (or login name) as a citation leader for that poster.
Occasionally one sees a ``# `` leader used for quotations from authoritative sources such as standards documents; the intended allusion is to the root prompt (the special Unix command prompt issued when one is running as the privileged super-user).
| Prev | Up | Next |
| Chapter 5. Hacker Writing Style | Home | Chapter 7. Hacker Speech Style |


Hash Class
This is an implementation of a dictionary/hash that does not convert its keys into Strings. Keys can therefore actually by anything!
Constructor
Hash
()
Item Index
Methods
- fromObject static
- get
- getElements
- hasKey
- put
- size
Methods
fromObject
(
static
-
object
Creates a new Hash from a given JavaScript object.
Parameters:
-
object
Object
get
(
Mixed
-
key
-
[equalityFunction]
Returns the value (or null) for the specified key.
Parameters:
-
key
Mixed -
[equalityFunction]
Function optionalThis optional function can overwrite the test for equality between keys. This function expects the parameters: (the current key in the key iteration, 'key'). If this parameters is omitted '===' is used.
Returns:
Mixed:
getElements
()
Get the elements of the Tuple.
hasKey
(
Boolean
-
key
Indicates whether the Hash has the specified key.
Parameters:
-
key
Mixed
Returns:
put
(
Hash
chainable
-
key
-
val
Adds a new key-value pair or overwrites an existing one.
Parameters:
-
key
Mixed -
val
Mixed
Returns:
Hash:
This instance.
size
()
Integer
Returns the number of entries in the Hash.
Returns:
Integer:


Home sales — and prices — are sizzling in a batch of understated inner-ring suburbs where first-time buyers and downsizing empty nesters are finding deals on modest ramblers and sensible split-levels in low-key neighborhoods that offer the kinds of value you can no longer find in many more popular central city neighborhoods. From Circle Pines to Brooklyn Center, these low-key communities offer great schools and easy access to jobs, transportation and shopping.
To find out which cities were most popular last year, the Star Tribune compiled its fourth annual Hot Housing Index, which ranks communities based on where houses sold more quickly than the year before; prices posted the biggest gains; sellers got closest to their asking price and market times fell the most.
The Hot Housing Index combines key housing metrics from year-end data provided by the Minneapolis Area Realtors: change in the median price per square foot; median days on market; percent of list price received by seller; and change in closed sales compared to the previous year. We ranked each community on those metrics, then added the rankings together to get an index score. This year, the Star Tribune excluded sales of newly constructed homes because not all new homes are sold through the Multiple Listing Service.
Use the search tool below to see rankings for the more than 100 cities included in the Hot Housing Index, plus historical real estate sales data for those cities and other cities in the 13-county metro area that didn't have enough sales last year to be included in the index. Historical data is also available for Minneapolis and St. Paul neighborhoods.


Education & Experiences
Html
HTML is my sit amet, rebum. Stet clita kasd gubergren, no sea.
Css
HTML is my sit amet, rebum. Stet clita kasd gubergren, no sea.
Php
HTML is my sit amet, rebum. Stet clita kasd gubergren, no sea.
Vue Js
HTML is my sit amet, rebum. Stet clita kasd gubergren, no sea.
Node Js
HTML is my sit amet, rebum. Stet clita kasd gubergren, no sea.
Sass
HTML is my sit amet, rebum. Stet clita kasd gubergren, no sea.

Envato Market
Envato University - 2014-2020
Harvard University is my sit amet, con sectetur adipisicing elit.
Master of Programming
Califonia IT University - 2012-2016
Harvard University is my sit amet, con sectetur adipisicing elit.


Module: Fishbans::BlockEngine
- Included in:
- Fishbans
- Defined in:
- lib/block_engine.rb
Instance Method Summary collapse
-
#get_block(id, metadata = nil, size = 42) ⇒ ChunkyPNG::Image
Gets a block image by its ID and Metadata.
-
#get_monster(id, three = false, size = 42) ⇒ ChunkyPNG::Image
Gets the monster image by its ID.
Instance Method Details
#get_block(id, metadata = nil, size = 42) ⇒ ChunkyPNG::Image
Gets a block image by its ID and Metadata. Unfortunately it uses the old block IDs rather than the new ones, so you have to memorize those pesky integers.
14 15 16 17 18 19 20 |
# File 'lib/block_engine.rb', line 14 def get_block(id, = nil, size = 42) url = "http://blocks.fishbans.com/#{id}" url += "-#{}" unless .nil? url += "/#{size}" if size != 42 response = get(url, false) ChunkyPNG::Image.from_blob(response.body) end |
#get_monster(id, three = false, size = 42) ⇒ ChunkyPNG::Image
Gets the monster image by its ID.
33 34 35 36 37 38 39 40 41 42 |
# File 'lib/block_engine.rb', line 33 def get_monster(id, three = false, size = 42) id = id.to_s url = 'http://blocks.fishbans.com' url += "/#{id}" if id =~ /^m/ url += "/m#{id}" if id !~ /^m/ url += '-3d' if three url += "/#{size}" if size != 42 response = get(url, false) ChunkyPNG::Image.from_blob(response.body) end |


Oman's State Council set to hold first session this month
by Times News ServiceMuscat: The State Council will hold its first annual session on November 14, following a directive from His Majesty Sultan Qaboos bin Said.
A statement issued by Oman News Agency said the State Council will hold its first session of seventh term (2019-2023).
“ Upon His Majesty the Sultan's orders, the State Council will start its seventh term (2019-2023) and will hold its first session for its first annual session on Thursday, 14 November 2019.”


Measure your meetings with Quiik. You’ll see their value increase and time wasted decrease. Guaranteed.


By Sachith Mendis
Nietzsche is lying to us in his On the Genealogy of Morality. The book is ostensibly presented as a historical work on the origins of morality, but even in the subtitle Nietzsche betrays the work’s polemical nature. An interpretation of Nietzsche’s genealogy as historically true is questionable, primarily because he affords so little attention to historical detail, and as a result, any insight into genuine history garnered from the Genealogy has to be extremely interpretative.
What purpose does genealogy serve then? This paper will argue that there is instrumental value in a genealogical exploration, in that—even if historically inaccurate—such an endeavour calls into question the legitimacy of morality. It does this by showing that morality could arise from contingent, emotive conditions that do not reliably generate true facts, and by dismantling the unquestionable authority of morality—by questioning its origins. Neither of these need the genealogy to be historically accurate, as much as they need it to be feasible as a historical narrative.
This paper then goes on to show that the genealogy’s support of Nietzsche’s moral critique goes further than just introducing doubt. A reading of Nietzsche’s genealogy as intentionally deceptive, and as a polemical tool to lower his reader’s defences explains why he chooses to frame most of the book as a genealogical endeavour, and makes sense of some of Nietzsche’s more confusing passages. This essay will explore the Genealogy’s preface, the last four sections of its second treatise, as well as its summary chapter in Ecce Homo to this end, and will show that, while Nietzsche’s genealogy is not necessarily historical, it is still crucially important to his project.
On the Genealogy of Morality purports itself to be a historical work—insofar as genealogy is related to history—and it is tempting to use its historical project as a basis for the critique of morality it presents. When Nietzsche introduces the book by claiming it to be about his “thoughts on the origins of our moral prejudices” (GM P:2), and a reader finds that the work critiques the value of morality, it is intuitive for her to think that it is this exploration of an origin that grounds such a critique.
Michael Forster argues that “the historical strength of Nietzsche’s thesis has not been well appreciated” (354). Forster claims that Nietzsche is referring to Palestine around the time of Christ as the setting for the slave revolt, where the master morals of ‘good’ and ‘bad’ are inverted into the slave morals of ‘evil’ and ‘good’ respectively. In this period, Palestine “was thickly settled with poleis, or cities, whose inhabitants were largely Greeks, and was in addition ruled by the Romans” (ibid.), while the Jewish population were oppressed by both groups. It might be this relationship between the Romans and the Jews that Nietzsche alludes to in section 13 of the first essay in his analogy of the “great birds of prey” and the “lambs”. If Nietzsche was talking about this period, how are we to understand the nature of the slave revolt? Was it a singular event, such as the Jewish revolts circa. 70 CE during which the second temple was destroyed, and after which some claim the rabbis began compiling the Talmud (Grayzel 193)?
Another compelling interpretation of the slave revolt is that is occurred during the Babylonian exile, when the Jews were scattered across Mesopotamia after a crushing military defeat in 605 BCE. If this were the case, perhaps the slave revolt was a gradual process during the exile, when the Jewish conception of Yahweh changed from a poly-theistic local god to a mono-theistic universal God. It’s in this change, arguably, that the Jewish deity stopped being a tribal god for good fortune—particularly in war—and became a ‘God of all gods’ which moralised against traditionally tribal values.
It is unlikely that a strict historicist interpretation of the Genealogy, as in Forster and Schuringa, is sound. Put simply: the imprecision with which Nietzsche speaks historically, and the ambiguity in his narrative that means a historical reading must be extremely interpretative, as above, does not seem like the work of a sincere historian. It is unclear why Nietzsche would not be clearer in his history, if he is referring so specifically to a particular historical period.
Adversaries to a historicist reading argue that the Genealogy would commit the “genetic fallacy” by equating morality’s suspicious past with reason to be suspicious of it today. Neil Sinhababu claims that Nietzsche does not make this mistake. Rather, the Genealogy shows that “moral beliefs arise through a process that does not reliably generate true belief” (270) because they are the manifestations of highly emotive responses to an extremely trying situation (slavery; the Babylonian exile). This “Unreliability Argument” (ibid.) undermines the validity of supposed moral facts generated in this way. Even if his genealogy is not completely historically accurate, Nietzsche convincingly shows that a value system as foundational as morality could arise from an emotionally contingent setting, which at the very least warrants questioning its validity.
But does this mean Nietzsche’s basis for critiquing morality rests on his genealogy? Sinhababu finds a historical reading to be an inappropriate basis for a genuine critique. In Sinhababu’s reading, “Nietzsche regards the nobles’ moral beliefs as unjustified and false as well,” because they are similarly formed by a process “driven by powerful emotions” (266). He concludes that “Nietzsche approves of the noble morality not because it is true or because the nobles are epistemically justified in accepting it, but because it promotes the active, proud, strong-willed lifestyle [my emphasis] that the nobles enjoy” (267). On what basis would Nietzsche praise an “active, proud, strong-willed lifestyle” (ibid.)?
Raymond Geuss argues that history has “genuine, if strictly limited, value” (285), and that Nietzsche is sincerely trying to be accurate. But Guess similarly does not accept that such a history—even if genuine—would form a basis for Nietzsche’s critique of morality. Instead, the critique of the value of morality is that “morality has overwhelmingly negative value as a major hindrance to the enhancement of life” (285)—not that morality has a dubious past. Here we can begin to see how Nietzsche grounds his critique: the key lies in his concepts of life affirmation and denial, of which the former leads to “the enhancement of life” (ibid.) or an “active, proud, strong-willed lifestyle” (Sinhababu, 267).
In line with Sinhababu and Geuss’ readings, Nietzsche seems to doubt grounding a critique of values on their history. In The Gay Science he says: “A morality could even have grown out of an error, and the realization of this fact would not so much as touch the problem of its value” (345).
Why, then, does Nietzsche frame his exploration as a genealogical/historical endeavour when, ultimately, such an account fails to ground the critique he is aiming for? Alexander Nehamas points out that Nietzsche’s genealogy helps de-solidify the foundation morality is built on, whereby it is taken as a priori, or ‘categorical’, or a ‘universal’ truth. For Nehamas: “The Genealogy contains a sustained effort on Nietzsche’s part to show that morality is a subject fit for interpretation” (58). What Nietzsche is doing in his critique—unlike traditional moral philosophers in the canon—is calling into question the value of morality itself, as opposed to particular moral values. This upheaval of morality as a priori is what allows Nietzsche to posit it as a relative nature, and to inspire his readers to overcome what has been utterly ingrained into them: “for those who employ critical history for the sake of life, there is even a noteworthy consolation: that of knowing that this first nature was once a second nature and that every victorious second nature will become a first” (HL 3).
There is instrumental value, then, in Nietzsche’s genealogy, as acknowledging the sheer fact that one can even think of morality as having a history, is a step towards understanding “that there are no moral facts whatever” (TI “Improvers”: 1, Nietzsche’s emphasis). This stance makes an important step: it shows that even though Nietzsche’s project is ostensibly historical, genealogy is used as a tool to support his real critique of morality on the basis that it is life-denying.
To what extent, then, is genealogy used to support Nietzsche’s moral critique? Does it do more than just undermine morality’s basis, and pit morality as unlikely to be true, as in Sinhababu? Nietzsche does, after all, frame his entire book through this genealogical lens. Ken Gemes argues that Nietzsche’s historical account is intentionally deceptive, and that it acts to distract the reader from the real focus of his critique: modern readers’ “ultimate embodiment of the ascetic ideal” (191). We can see this by understanding Nietzsche’s genealogy as ultimately polemical, or a rhetorical tool for distracting his audience. Through this lens, Nietzsche’s contradictions and curious changes in topic in the preface and the end of the second treatise make sense, and his flagrant historical inaccuracy proves not to be a problem to his critique of morality.
Nietzsche is intentionally misleading his reader in the Genealogy. “We are unknown to ourselves” (GM P:1) is how he chooses to start the book: this could be saying that “we” don’t know our (moral) history, or—in line with our moving away from a historical understanding of genealogy—it could be signalling towards some other aspect of ourselves that we’re not cognizant of. The first section of the preface ends with: “We remain of necessity strangers to ourselves [my emphasis] … with respect to ourselves we are not ‘knowers’ … [Nietzsche’s ellipsis]” (ibid.), and as if in the same breath, the second section starts—with a markedly different tone, and a switch in topic from “us” not knowing ourselves to “the origins of our moral prejudices” (GM P:2). This sort of manic tonal switch is not infrequent in Nietzsche’s work, but it is disconcerting how he does not explain his opening remarks. As Gemes puts it, “the whole theme of our being strangers to ourselves is quickly and quietly dropped” (2006, 192).
In his summary of the Genealogy in Ecce Homo, Nietzsche says that its three essays are "uncannier [my emphasis] than anything else written so far” with regards to “expression, intention, and the art of surprise,” (EH “Genealogy”). He describes the book as "calculated to mislead: cool, scientific, even ironic, deliberately foreground, deliberately holding off” (ibid.): it is difficult to read these lines and not be unnerved by the idea that Nietzsche might be hiding something.
Why would Nietzsche want to deceive his reader? Because the subject of the Genealogy’s critique is uncannily close to home. Nietzsche’s critique centres on his reader—not her ancestors—and, as such, he must be indirect in how he presents it to avoid provoking a “reflex denial and a refusal to countenance his message” (Gemes, 192). Gemes also argues that Nietzsche—in proto-Freudian fashion—believes that subconscious or “deeper forms of realization … are necessary for genuine change” (192). A genealogical narrative, as it were, is a rhetorical tool employed by Nietzsche to lower his reader’s guard, and to affect them on a sub-conscious level. In this view, the Genealogy is not intended as a handbook for healers that outlines an issue, its symptoms, and its cures; Nietzsche’s book is the medicine that will, through subtlety and subterfuge, make readers grow aware of their sickness, critical of its ill-worth, and resistant to its manifestation as modern compassionate morality.
Zooming out, it can be useful to track Nietzsche’s tone through the book to see how his object of criticism shifts from an ancestral Other to the modern reader, and how the book shifts from deceptive to explicit. The first essay of the Genealogy is quite explicitly about “the triumph of Judeo-Christian slave morality over the Greek/Roman master morality” (Gemes, 192). The second essay shifts the focus a little closer to home, with its arguments on conscience (more recognisable to modern readers than some aristocratic distinction of sets of values), but still ostensibly chooses to focus on ancient believers of God. The third essay is where Nietzsche begins to let on to his reader that his critique is, in fact, of modernity. As Gemes argues, it is here that Nietzsche begins to criticise the modern, post-religious ideals of “truth, objectivity, and science” (193) as the most recent manifestation of the ascetic ideal. Even here, however, Nietzsche is far from explicit in calling out his readers. According to Gemes, “[i]t is in GM III:23 that we find ourselves for the first time more directly addressed” (ibid.): the first 22 sections focus instead on religious and historical ascetism. A genealogical account, then, must be critically important to this project, if much of the book is framed by one. Through Gemes’ reading, it becomes clear that genealogy is foundational to the text—just not in a historical way. The potency of Nietzsche’s critique relies on its ability to slip past his reader’s defences, so they grow to abhor the sort of life-denying ascetism he is criticising, before realising they embody it.
The last four sections of the second treatise are particularly interesting in light of this as they parallel the end of GM P:1 when Nietzsche stops himself from being too frank with his reader. GM II:22 has a strong emphasis on God, religion, and the early Jews’ internalization of drives. Nietzsche makes it seem like believing in a life-denying metaphysics of an afterlife is an essential pre-requisite to internalization, as it redirects attention from the world around us, to the promise of a world beyond our own. GM II:23 talks about the ancient Greeks, and how their religious metaphysics helped them keep “bad conscience at arm’s length”: this is again historical, but perhaps Nietzsche expects his reader to draw more of an analogy between herself and the Greeks than with the Jews.
There is a change of tone in section 24, where Nietzsche says that “[w]e modern humans, we are the heirs of millennia of conscience-vivisection and cruelty to the animal-self … For all too long man has regarded his natural inclinations with an ‘evil eye,’ so that in him they have finally become wedded to ‘bad conscience’” (GM II:24). This contrasts section 22’s implication that bad conscience—a result of the internalization of drives—requires some religious metaphysics through which to moralise bad drives; for the first time in the second essay, Nietzsche accuses modernity of the same unhealthy behaviour. This section betrays Nietzsche’s subterranean criticism of the reader, with his repeated use of “us” and “we”, and his situating the critique in “this decaying self-doubting present”, and “today” (GM II:24).
Tomasello’s (2008) usage-based theory argues grammatical structures arise from using words: linguistic structures are constructed by communicating meaning. We can see this hierarchy by observing how infants communicate. According to Tomasello, “human infants communicate in some fairly sophisticated ways before they have acquired any linguistic conventions” (2009, 70), for example by pointing and gesturing.
Towards the end of the section, Nietzsche says “… this bell-stroke of noon … that makes the will free again” (GM II:24). This parallels the “twelve strokes of noon” that leave the “self-absorbed person” of the first section of the preface—the stranger to them self—rubbing their ears and asking, “who are we actually” (GM P:1): Nietzsche is talking about us. As with the restricting ellipsis at the end of GM P:1, Nietzsche catches himself in section 25: “—But what am I saying? Enough! Enough! At this point there is only one thing fitting for me, to be silent” (GM II:25).
A reading of Nietzsche’s genealogy as “intentionally misleading,” (Gemes, 191) and of his real target in the Genealogy being modern readers and their post-religious scientific ideals makes sense of these uncanny lines, and is coherent with the Genealogy’s closing critique of the will to truth and science as ascetic. Through such a lens, Nietzsche’s history as outlined in the first treatise is an intentionally deceptive one, to win him the allegiance of his contemporary anti-Semitic audience. While Nietzsche could be trying to be historically accurate at times, it isn’t fundamentally important to his argument that he is, and with this in mind, Nietzsche’s critique of morality is still grounded and pertinent, even if his history is wrong. This is because his real target—as revealed towards the end of the third treatise—is modernity and its unceasing will to truth. The unnerving sections in the preface and at the end of the second treatise are clues Nietzsche leaves behind for the reader who has read past GM III:22, who comes back "afterwards" and ask[s], completely amazed, completely disconcerted, ‘what did we actually experience just now?’” (GM P:1).
*
Readers of the Genealogy as historical must justify the one consistency in Nietzsche’s history: its ambiguity. There’s no reason for Nietzsche to deliberately speak ‘in between the lines’ if his intention was to reveal some disturbing historical truths, and then ground a critique of morality on that revelation. A critique of morality understood as grounded on Nietzsche’s second-order values of life-affirmation and denial, then, is more compelling than one grounded historically (for a note on how these might be defined, see n2), but leaves open the question as to why the book is framed as a genealogical exercise in the first place.
As such, Nietzsche’s genealogy is best understood as rhetorical, or polemical. Not only does the proposal that morality can have a history undermine its authority and ontological status, but through a carefully crafted historical narrative, Nietzsche is able to use his genealogical account as a façade behind which he hides the real subject of his critique—the reader. By shrouding his genuine critique with a genealogical narrative that is intentionally historically ambiguous, Nietzsche appeals to as many readers as possible, inviting them to fill in the gaps. There’s a limit to how inclusive Nietzsche could have been, however, and as such from a modern vantage point, his focus on the Jews and anti-Semitic tone seem to be a transparent appeal to the xenophobic inclinations of his contemporaries, instead of sincere history.
In this way, genealogy is not historical for Nietzsche, but it is crucial to his project. It is only under the cover of genealogy that Nietzsche’s real critique can become pertinent in his readers, and can begin to dismantle within them their life-denying attitudes. A view of genealogy in this way means that Nietzsche’s historical inaccuracy (or apathy) does not undermine the Genealogy’s overall critique of morality Further, a reading of Nietzsche’s genealogy as deceptive makes sense of his oscillatory tone throughout the Genealogy, as well as the disconcerting claims of misdirection in the book’s Ecce Homo chapter. Through the lens of deceptive genealogy, sections such as those in the beginning of the preface, and at the end of the second treatise make sense as allusions to Nietzsche’s real critique, and serve to make sure the critique of his reader is properly absorbed.
Gemes, Ken. “‘‘We Remain of Necessity Strangers to Ourselves’’: The Key Message of Nietzsche’s Genealogy.” Acampora, Christa Davis. Nietzsche's On the Genealogy of Morals: Critical Essays. Rowman & Littlefield Publishers, 2006. 191-208.
—. “Freud and Nietzsche on sublimation.” Journal of Nietzsche Studies (2009): 38-59.
Geuss, Raymond. “Nietzsche and Genealogy.” European Journal of Philosophy 2.3 (1994): 274-292.
Grayzel, Solomon. A History of the Jews: From the Babylonian Exile to the Present. Penguin Books, 1984.
Huddleston, Andrew. “Nietzsche on the Health of the Soul.” Inquiry 60.1-2 (2017): 135-164.
Kaufmann, Walter. Nietzsche: Philosopher, Psychologist, Antichrist. Princeton University Press, 1950.
Nehamas, Alexander. “The Genealogy of Genealogy: Interpretation in Nietzsche’s Second Untimely Meditation and in the Genealogy of Morals.” Acampora, Christa Davis. Nietzsche's On the Genealogy of Morals: Critical Essays. Rowman & Littelfield, 2006. 57-65.
Nietzsche, Friedrich. Dawn: Thoughts on the Presumptions of Morality. Trans. Brittain Smith. Stanford University Press, 2011.
—. Human, All Too Human, I: A Book for Free Spirits. Trans. Gary Handwerk. Stanford University Press, 1995.
—. On the Genealogy of Morality. Trans. Maudemarie Clark and Alan J. Swensen. Hackett Publishing, 1998.
Nietzsche, Friedrich. “On the Uses and Disadvantages of History for Life.” Untimely Meditations. Trans. R. J. Hollingdale. Cambridge University Press, 1997. 57-124.
—. The Gay Science. Trans. Josefine Nauckhoff. Cambridge University Press, 2001.
—. Twilight of the Idols. Trans. R. J. Hollingdale. Penguin Books, 1968.
Sinhababu, Neil. “Vengeful Thinking and Moral Epistemology.” Leiter, Brian and Neil Sinhababu. Nietzsche and Morality. Oxford University Press, 2007. 262-280.


When I tried speed it was during a visit home, involved was my friend and 2 relatives, also another friend who rolled constantly. We free based it. I felt very present, when I reclined in my comfy chair, sat back and listened to the chit chat, hardly getting involved. I was put at an ease which was bordering on intense. The rolling-often other friend, happened to not eat any pills that night, only a few drinks, 2 or 3, he suddenly left, very abruptly and with hardly a word. No one has heard from him since, but a girl we know saw him at an after-hours, a few weeks later. I stayed until the next night. Mainly alert and present, and pleasant.
Then a few weeks later. I used a little bit later. But, not memorable. Once, I went out on a night before having to work in the morning, I spotted a guy that's all interested in me, I told him that I needed to stay awake until work, and throughout the shift of 8 hours. Every twenty minutes or so I get his baggie off him. I was new to it and did a lot as it turns out. Work wasn't a problem. My Job is to stock shelves with natural products. I was quiet and attentive to being thorough.
The problem arose of my being too aware of each instant, a consequence was the day seeming longer. in the latter half of he shift I grew antsy. Found myself having delusions of everyone giving me deliberate attention. When I coordinated with my boss, I felt that I came across intensely, and in a frenzy. Things got strange and uneasy when I saw a co-worker to my left and turning a corner saw her again. OH WOW! I didn't like it.
I called my boyfriend of only 2 weeks and had him come get me, so I wouldn't have to take the public transit. I couldn’t wait to leave. Getting very anxious to get from there. At his house I felt not so alone and fearful, but still I was sketchy and thought he might murder me, in different ways. By a gun which is kept in the house, in which case I planned to leap through the window, forgetting about the iron bars.  I didn't know him as well as I do now, or imagine to. We argued dramatically over some truth issues, not related to the speed, he has been 'jacked up' himself in his time.
These days I repeat use in the same way, going to parties of worthwhile DJs, working a few hours later. I'm better about it. And now am finding that I can easier function without any use beyond the club. It does take a long time to wrap up the 8 hours, often without a break, so to be able to leave sooner.
I stay up on my nights off and read The Lord of the Rings. The eeriness I'm subject to noticeably.
No complaints really, I keep attentive to any rise of psychosis in myself. I have a friend who become paranoid and delusive. She may have been a bona fide schizophrenic. She has amazing goals, but seemed peculiar and distant. She didn't return calls, for fear of being a polluting influence. She killed herself. I recommend weariness, and precaution to not get in too deeply. Be vigilant of changes in your physical, mental, emotional, perhaps spiritual embodiments. I'm having a nice time. I don't regret my taking it at all.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


About Me
My name is Andrew Rivera.
I'm 25 years old.
I'm a Computer Science major at Southern Connecticut State University.
My favorite sports are Football, Soccer, and Baseball.
My favorite teams are Dallas Cowboys, Barcelona, New York Yankees.
HEAD
My name is Andrew Rivera.
I'm 25 years old.
I'm a Computer Science major at Southern Connecticut State University.
My favorite sports are Football, Soccer, and Baseball.
My favorite teams are Dallas Cowboys, Barcelona, New York Yankees.


| Xmega Application Note | |||||
Union of pointers to 64-, 32-, 16- and 8-bit unsigned integers. More...
#include <compiler.h>
Data Fields | |
| S16 * | s16ptr |
| S32 * | s32ptr |
| S64 * | s64ptr |
| S8 * | s8ptr |
| U16 * | u16ptr |
| U32 * | u32ptr |
| U64 * | u64ptr |
| U8 * | u8ptr |
Union of pointers to 64-, 32-, 16- and 8-bit unsigned integers.
Definition at line 177 of file compiler.h.
Definition at line 183 of file compiler.h.
Definition at line 181 of file compiler.h.
Definition at line 179 of file compiler.h.
Definition at line 185 of file compiler.h.
Definition at line 184 of file compiler.h.
Definition at line 182 of file compiler.h.
Definition at line 180 of file compiler.h.
Definition at line 186 of file compiler.h.
| Generated on Fri Oct 22 12:15:26 2010 for AVR1300 Using the Xmega ADC by 1.6.3 |


Uguisubari (鴬張り or 鶯張り) are wooden floors that rub together and produce a squeeky chirping sound when walked upon. They are used in the hallways of some shrines, temples, and palaces.
These floors, when dry, naturally produce this sound, however from the early 1800s onward, the floors were built in such a way that the floors would squeek whenever put under pressure, regardless if they are dry or not. This allowed the floors to act as a security device, preventing someone's passage to ever go unnoticed.


Lyrical Notes
(Spring 2018) azywong.github.io/lyricalnotes - github.com/azywong/lyricalnotesA look at Billboard’s Hot 100 over the years via data visulization with d3.js.
github.com/azywong - linkedin.com/in/allisonzywong - azywong.com
A look at Billboard’s Hot 100 over the years via data visulization with d3.js.
A todo list and calendar app built using Node.js, javascript and postgres.
(username: test / password: test)
Worked with the Data Science department of PNC Bank to build a web application with Node.js, javascript and MSSQL to create a testing portal that: automated the running of data modelling scripts, saved the end modelling results and intermediate logs in a relational database, showed this all in a dashboard with interactive graphs.
Research Assistant for VGL Lab at USF - vgl.cs.usfca.edu
Intern at the Digital Solutions Team
Teaching Assistant for Data Visualization Class
Software Development.


Ruby vs Javascript
Ruby Hashes vs. JavaScript Objects
Objects (similar to Ruby’s hash), declared as variables, are a way of organizing key/value pairs. For example, var cat = {color: "grey", name: "Spot", age: "12"};
To access the value of an associated key, you can call that on the variable name: cat.name returns "Spot". You can also easily delete a key/value pair by writing delete cat.name.
To declare a new key/value pair, write: cat.gender = "male";.
This appends this new data point to the end of the Object.
There is a very interesting blog post written by the flatiron school on the differences of Ruby and JS syntax its here it really goes over how to find index within arrays methods vs functions
Ruby classes vs. JavaScript constructor functions
JS objects don;t have a formal class, an thus there is no special way in defining instance of a class. IN RUBY its easy to define instance of classes with keyword new. And it's also easy to define instance variables with the def initialize method within a class.
JavaScript instances are created with a constructor. The constructor of an instance is a function that was invoked with the new operator. In JavaScript, any function can be a constructor, even if it doesn’t look like one:
// => undefined
square(2)
// => 4
square(2).constructor
//=> [Function: Number]
new square(2)
//=> {}
new square(2).constructor
//=> [Function: square]
Javascript objects are composite data structures comprised of properties
var obj = {};
obj.name = "Adam"
is the same as
var obj = {
name: "Adam"
};
which is the same as
var obj = {};
obj["name"] = "Adam";
};
every function in JS is potentially a constructor and can be an instance of the function. WHAT??...
How does JS define behaviour of instances?
- JavaScript doesn’t have a special syntax or special kind of object for that, it has “prototypes.” Prototypes are objects, but unlike a classical system, there are no special methods or properties associated with a prototype. Any object can be a prototype, even an empty object. In fact, that’s exactly what is associated with a constructor by default
Lets compare Ruby Classes vs JS Prototypes
You can see the instance variables and if you wanted to get an instance of the class que you would simply use the new method on it, but in JS it is slightly different first we need to look at the prototype of the que
Here we can see that using the keyword this.array
andthis.head
shows that in JS any object can be a prototype“Classes” are objects in most “classical” languages, but they are a special kind of object. In JavaScript, prototypes are not a special kind of object, they’re just objects.
source http://raganwald.com/2013/02/10/prototypes.html
Ruby documentation vs. JavaScript documentation
the difference in the ruby documenation vs JS documentation is very broad, we rely heavly on the Ruby docs as the "bible" on all things ruby as for JS we rely on the Mozzilla Developers network
Looping in Ruby vs. Looping in JavaScript
in JS you would loop through doing this var languages = ["HTML", "CSS", "JavaScript", "Python", "Ruby"];
for (i=0;i
in Ruby you would do pretty much the same thing but you would do +=1 instead of i ++
JS uses the each for each loop, for in, for, and for of


Next create entity descriptions for the entities in the model. Our model will have two entities: City and Neighborhood
City
Neighborhood


FAQs
What is Lorem Ipsum?
New common language will be more simple and regular than the existing European languages. It will be as simple as occidental.
Where does it come from?
Everyone realizes why a new common language would be desirable one could refuse to pay expensive translators.
Where can I get some?
If several languages coalesce, the grammar of the resulting language is more simple and regular than that of the individual languages.
Why do we use it?
Their separate existence is a myth. For science, music, sport, etc, Europe uses the same vocabulary.
Where can I get some?
To an English person, it will seem like simplified English, as a skeptical Cambridge friend of mine told me what Occidental
Where can I get some?
If several languages coalesce, the grammar of the resulting language is more simple and regular than that of the individual languages.
Can't find what you are looking for?
To achieve this, it would be necessary to have uniform grammar, pronunciation and more common words if several languages coalesce


abstract class SiteUser implements UserInterface
Constants
| STATUS_INACTIVE |
|
| STATUS_ACTIVE |
|
Methods
|
setAccountId(bigint $accountId)
Set account id |
||
| bigint |
getAccountId()
Get accountId |
|
| bigint |
getId()
Alias for getAccountId |
|
| setEmail($email) | ||
| getEmail() | ||
| setPassword($password) | ||
| getFirstName() | ||
| setFirstName($firstName) | ||
| getMiddleName() | ||
| setMiddleName($middleName) | ||
| getLastName() | ||
| setLastName($lastName) | ||
|
getPassword()
UserInterface |
||
| getSalt() | ||
| getUsername() | ||
| getRoles() | ||
| eraseCredentials() | ||
| __toString() | ||
| getFullName() |
Details
at line 29
public
setAccountId(bigint $accountId)
Set account id
at line 39
public bigint
getAccountId()
Get accountId
at line 49
public bigint
getId()
Alias for getAccountId
at line 54
public
setEmail($email)
at line 61
public
getEmail()
at line 66
public
setPassword($password)
at line 73
public
getFirstName()
at line 78
public
setFirstName($firstName)
at line 85
public
getMiddleName()
at line 90
public
setMiddleName($middleName)
at line 97
public
getLastName()
at line 102
public
setLastName($lastName)
at line 113
public
getPassword()
UserInterface


Create a new configuration file.
Path to the configuration file.
Configuration files folder.
ConfigFile constructor options object.
Get an array of folder names of the config file's path. Treat the config folder as the root folder such that only folders will be listed that are sub-folders of the root config folder.
Array of folder names.
Load the JSON object contained by the configuration file.
Process the path and filename of the configuration file regarding to the contained tags.
Configuration file class, representing a single configuration file inside the configuration folder or one of its sub-folders.


After the installation I created a test post and only after that noticed the URL:
http://localhost/Graffiti/first-post
Notice there is not any extension and the URL looks very clear. But HOW? I did not do neither of the following:
- Added wild-card mapping;
- Configured Web.config with IIS 7 as I have IIS 6;
- Run any script or something.
The Default.aspx is auto-generated and just has some settings. The content is stored in the database.
Do you see now how this wildcard-mapping works?
It just allows IIS to handle friendly-urls by creating a real resource. But the actual URL that gets processed on the server is:
http://localhost/Graffiti/first-post/Default.aspx
That does make assumption that IIS has Default Document with name “Default.aspx”. Removing it will kill the whole idea of such friendly-urls.
The idea is dead simple and indeed a good one.
I am not sure weather I like it or not. One thing I definitely don’t like so far is the fact that the folder will get polluted with all those folders and files.


The product name:
What do you call your product ? Think of something that's easy to remember that contains key words that will help people find it.
Product Source:
Provide us some information about what your product is how and when it came to be produced.
The product type:
What product ctaegory does your product fall under ? Use the select pulldowns to refine the category.
Description:
Please describe your product here at length. Tell us why you think this product is exactly what Joonley stores will want to sell.
Price:
Please provide the suggested price - both q1 and q10:
Weight:
What will your product weight when shipped:


Question 5 : top 3 of the months most concerned by the cases of crimes
Click on a category of the legend to hide it from the graph


Reviews
Comparison
FAQs
About
Menu
Contact
We would love to hear from you!
Unfortunately the following types of emails will be ignored:
Requests for individual recommendations.
Requests for guest posts.
Any submissions that appear low-effort or automated.
Full Name
Email Address
Message


The System X Assembler processes System X assembly files (*.s), and generates System X object code (*.o) from them.
Usage: sxas [options] { FILE.s }