Protect Earth's natural resources by developing the necessary skills to turn your environmental passions into a career.
Preservation of the environment is more important now than it has ever been. Channel your love of and respect for nature into a degree that will open the doors to a rewarding career in the field of environmental science and studies.
Stetson's Environmental Science and Studies program is a diverse, interdisciplinary field encompassing art, science and policy which directly relates to agriculture, ecosystems, economics and toxicology. You will work within solid ethical and scientific frameworks to make well-supported decisions to protect natural resources, develop innovative solutions for environmental problems and exhibit bold leadership skills for environmental change.
The Stetson University environmental science program offers both bachelor of arts and bachelor of science tracks. The B.S. program involves the study of environmental issues from a natural science perspective with an emphasis on nature conservation. The B.A. program involves the study of environmental issues from a social science perspective with a focus on policy and culture.
Our program offers extensive opportunities for field experience, community-based projects and internships. Students have access to the G.I.S. computer lab, field studies laboratory and equipment, G.P.S. and the associated labs and equipment from member departments like biology and chemistry.
This track focuses on the protection of species and habitats. Students gain a strong foundation in policy and spatial analysis.
This track is geared toward students planning to work in agencies or environmental consulting firms. They learn methods of tackling problems of air and water pollution, waste management or renewable energy.
This track is for students who wish to address land-use issues, demography and other spatial perspectives in careers in planning or in agencies, consulting firms or non-profits.
This track is geared toward students interested in careers in environmental law, policy development, non-profits and planning.
This track is for students who are interested in leading culture change through art, communication and marketing, who plan to pursue careers in non-profits, for-profits and agencies with strong public education goals.
This track concerns studying the local and global aspects of human cultures as they are defined by the environment. Students in this track intend to pursue careers in non-profits, agencies and foreign service.
The core faculty in the Department of Environmental Science and Studies include geographers, ecologists, a geologist and an environmental attorney and policy specialist. Affiliated faculty who also support the programs come from multiple departments throughout Stetson's campus who focus on natural sciences, social sciences and humanities.
Our departmental and affiliated faculty are involved in diverse projects including greenhouse gas auditing, community planning for sea level rise, indigenous cultural conservation, the economics of water use, biography of historic conservation leaders, the ecology and hydrology of Florida springs, paleoclimate studies, native plant ecology, marine ecology, herpetology, air quality and atmospheric chemistry, and energy systems and culture.
As a major in either environmental science or environmental studies, you will have opportunities at a number of different natural resource agencies, firms and private industries.
Most students get hired as either geographic information systems specialists or ecologists.
Most students get hired as environmental managers or sustainability officers.
Conservation, research and educational missions are included.
This includes research and academic instruction.


One of the great things about our modern era is the way to safely alter our bodies to look pretty much anyway we would like within reason. However, a popular mode of fashion and expression can often have negative effects on our teeth and oral health. This is not meant to dissuade you from wearing oral piercings or getting one, but simply let you know about additional precautions you may need to take if you consider getting one. It is well-established that tongue and lip piercings can degrade teeth, gums, and other oral health problems, if not cared for properly.
If you have not gotten a piercing in your lip or tongue yet and are considering one, there is always the risk of pain, swelling, and damage to your nerves and blood vessels in your tongue or lip. The inside of your mouth, when producing saliva normally, is a warm, moist environment filled with bacteria and may be an ideal place for infection. This infection can become life threatening, particularly if you get encarditis, which is an infection of the heart and its valves. This can happen if bacteria from your mouth get into your bloodstream, which can happen, especially if a blood vessel is punctured. Also, there is a chance that your tongue may swell and potentially block your airway. Damage to a blood vessel may also result in serious blood loss, which can also be dangerous and life threatening.
This makes your mouth slightly less than ideal for a piercing. Additionally, the temptation to play with your piercing may result in cracked or damaged teeth, fillings, and other work. If you currently have a piercing or are considering get one, special care must be taken not to play with it excessively.
Nerve damage can occur in the tongue as well. Most nerve damage is temporary, but sometimes it can become permanent, lessening your sense of taste and ability to move your tongue.
If you are prone to metal sensitivities, which affect a small portion of the population depending on the metal. Certain implants, such as dental or orthopedic implants, have become recognized as causing an allergic reaction in certain patients. If you are aware of any sort of metal allergy, it is very important to know what sort of piercing you are getting or eschew it entirely.
Also, as your mouth is designed to be part of your digestive tract, the piercing, especially a tongue or inner piercing may result in excessive saliva production which can be an embarrassing problem.
Piercings, also due to their metallicity, can interfere with dental X-rays. They may also become loose and become a choking hazard if you are not careful.
Now, these are all the negatives that can occur, so what can you do to mitigate them or head them off? Quite a bit!
First, if you have any problems, especially if you may have an infection or suspect you may have an infection, such as fever, chills, shaking, or irregular coloring around the piercing site, call your doctor or dentist right away! If there is profuse bleeding or you feel faint, severely ills, or are having trouble breathing / tightness in the chest, go to the emergency room or call 911.
One of the biggest preventative steps you can take is keeping the piercing site clean by regularly rinsing out your mouth and removing it to clean it.
Be aware of your piercings location and try not to play with it, as tempting as it may be.
Always make sure your piercing is tightly fitted, so it does not come loose and becomes a choking hazard. Make sure your hands are clean before this, as piercing sites are already sensitive to bacterial intrusion.
If you are going to be participating in any activity that may become rough or physical, such as playing contact sports, participating in martial arts, or going to a concert where there may be pushing and shoving (such as a mosh pit), be sure to remove your piercings and take proper precautions such as a mouth guard.
And as always, see your dentist regularly and maintain proper dental hygiene.


text:
Dave Graham's Story of The Bridge of Ashes (V15)
Dave Graham spent about a year on his latest V15: The Bridge of Ashes (V15) in Rocky Mountain National Park, Colorado. "One of the most challenging projects I have ever completed," he says.
Bouldering Videos
Dave Graham: The Ice Knife (V15)
Dave Graham on (V15) from The Players
By Brian Solano
Uncut: Dave Graham Sends Monkey Wedding (V15)
By Climbing Staff

redpajama_set_name: RedPajamaCommonCrawl


text:
Found 242 UK NGOs working in Jersey
Figures refer to charities registered with the Charity Commission for England and Wales, based on areas of operation supplied to the Charity Commission by the charities themselves. Charities that say they work in more than 50 countries are not included. Total spending of these organisations includes work they carry out outside of Jersey.
NGOs working in Jersey also work in a further 195 countries, including the UK
Altogether, these NGOs spend £1,923.4m
* It is not possible to isolate spending only on Jersey, we can only report spending by organisations in all the countries they work in.
isles
List of UK-registered organisations operating in Jersey, sourced from data published by IATI publishers.
Data on Jersey from IATI d-portal
Jersey on devtracker


text:
require 'test_helper'
require 'timeout'
require 'socket'
class TestResponse < MiniTest::Unit::TestCase
  def setup
    @valid_request = "GET / HTTP/1.1\r\nHost: test.com\r\nContent-Type: text/plain\r\n\r\n"
    @close_request = "GET / HTTP/1.1\r\nHost: test.com\r\nContent-Type: text/plain\r\nConnection: Close\r\n\r\n"
    @http10_request = "GET / HTTP/1.0\r\nHost: test.com\r\nContent-Type: text/plain\r\n\r\n"
    @keep_request = "GET / HTTP/1.0\r\nHost: test.com\r\nContent-Type: text/plain\r\nConnection: Keep-Alive\r\n\r\n"

    @valid_post = "POST / HTTP/1.1\r\nHost: test.com\r\nContent-Type: text/plain\r\nContent-Length: 5\r\n\r\nhello"
    @valid_no_body = "GET / HTTP/1.1\r\nHost: test.com\r\nX-Status: 204\r\nContent-Type: text/plain\r\n\r\n"

    @headers = { "X-Header" => "Works" }
    @body = ["Hello"]
    @sz = @body[0].size.to_s

    @host = "127.0.0.1"
    @port = 8080

  end

  def teardown
    @client.close if @client
    @server.stop if @server
    sleep 0.1
  end

  def lines(count, s=@client)
    str = ""
    timeout(5) do
      count.times { str << s.gets }
    end
    str
  end

  def valid_response(size = @sz, close = false)
    conn = close ? "close" : "keep-alive"
    %r{HTTP/1.1 200 OK\r\nX-Header: Works\r\nServer: Jubilee\(\d\.\d\.\d\)\r\nContent-Length: #{size}\r\nConnection: #{conn}\r\nDate: (.*?)\r\n\r\n}
  end

  def test_one_with_content_length
    start_server
    @client << @valid_request
    sz = @body[0].size.to_s

    assert_match valid_response(sz), lines(7)
    assert_equal "Hello", @client.read(5)
  end

  def test_two_back_to_back
    start_server
    @client << @valid_request
    sz = @body[0].size.to_s

    assert_match valid_response(sz), lines(7)
    assert_equal "Hello", @client.read(5)

    @client << @valid_request
    sz = @body[0].size.to_s

    assert_match valid_response(sz), lines(7)
    assert_equal "Hello", @client.read(5)
  end

  def test_post_then_get
    start_server
    @client << @valid_post
    sz = @body[0].size.to_s

    assert_match valid_response(sz), lines(7)
    assert_equal "Hello", @client.read(5)

    @client << @valid_request
    sz = @body[0].size.to_s

    assert_match valid_response(sz), lines(7)
    assert_equal "Hello", @client.read(5)
  end

  def test_no_body_then_get
    start_server
    @client << @valid_no_body
    assert_match %r{HTTP/1.1 204 No Content\r\nX-Header: Works\r\nConnection: keep-alive\r\n(.*?\r\n)*?\r\n}, lines(6)

    @client << @valid_request
    sz = @body[0].size.to_s

    assert_match %r{HTTP/1.1 200 OK\r\nX-Header: Works\r\nServer: Jubilee\(\d\.\d\.\d\)\r\nContent-Length: #{sz}\r\nConnection: keep-alive\r\n(.*?\r\n)*?\r\n}, lines(7)
    assert_equal "Hello", @client.read(5)
  end

  def test_chunked
    start_server("chunked")

    @client << @valid_request

    assert_match %r{HTTP/1.1 200 OK\r\nX-Header: Works\r\nServer: Jubilee\(\d\.\d\.\d\)\r\nConnection: keep-alive\r\nTransfer-Encoding: chunked\r\nDate(.*?)\r\n\r\n5\r\nHello\r\n7\r\nChunked\r\n0\r\n\r\n}, lines(13)
  end

  def test_no_chunked_in_http10
    start_server("chunked")

    @client << @http10_request

    assert_match %r{HTTP/1.0 200 OK\r\nX-Header: Works\r\nServer: Jubilee\(\d\.\d\.\d\)\r\nConnection: close\r\nDate: (.*?)\r\n\r\n}, lines(6)
    assert_equal "HelloChunked", @client.read
  end

  def test_hex
    start_server("hex")
    str = "This is longer and will be in hex"

    @client << @valid_request

    assert_match %r{HTTP/1.1 200 OK\r\nX-Header: Works\r\nServer: Jubilee(.*?)\r\nConnection: keep-alive\r\nTransfer-Encoding: chunked\r\nDate: (.*?)\r\n\r\n5\r\nHello\r\n#{str.size.to_s(16)}\r\n#{str}\r\n0\r\n\r\n}, lines(13)

  end

  def test_client11_close
    start_server
    @client << @close_request
    sz = @body[0].size.to_s

    assert_match valid_response(sz, true), lines(7)
    assert_equal "Hello", @client.read(5)
  end

  def test_app_sets_content_length
    start_server("content_length")
    @client << @valid_request

    assert_match valid_response(11), lines(7)
    assert_equal "hello world", @client.read(11)
  end

  def test_allow_app_to_chunk_itself
    start_server("self_chunked")
    @client << @valid_request

    assert_match %r{HTTP/1.1 200 OK\r\nX-Header: Works\r\nServer: Jubilee(.*?)\r\nConnection: keep-alive\r\nTransfer-Encoding: chunked\r\nDate: (.*?)\r\n\r\n5\r\nhello\r\n0\r\n\r\n}, lines(11)
  end

  def test_two_requests_in_one_chunk
    start_server
    req = @valid_request.to_s
    req << "GET /second HTTP/1.1\r\nHost: test.com\r\nContent-Type: text/plain\r\n\r\n"

    @client << req

    sz = @body[0].size.to_s

    assert_match valid_response(sz), lines(7)
    assert_equal "Hello", @client.read(5)

    assert_match valid_response(sz), lines(7)
    assert_equal "Hello", @client.read(5)
  end

  def test_second_request_not_in_first_req_body
    start_server

    req = @valid_request.to_s
    req << "GET /second HTTP/1.1\r\nHost: test.com\r\nContent-Type: text/plain\r\n\r\n"

    @client << req

    sz = @body[0].size.to_s

    assert_match valid_response(sz), lines(7)
    assert_equal "Hello", @client.read(5)

    assert_match valid_response(sz), lines(7)
    assert_equal "Hello", @client.read(5)

    #assert_kind_of Jubilee::IORackInput, @inputs[0]
    #assert_kind_of Jubilee::IORackInput, @inputs[1]
  end

  def test_keepalive_doesnt_starve_clients
    start_server
    sz = @body[0].size.to_s

    @client << @valid_request

    c2 = TCPSocket.new @host, @port
    c2 << @valid_request

    out = IO.select([c2], nil, nil, 1)

    assert out, "select returned nil"
    assert_equal c2, out.first.first

    assert_match valid_response(sz), lines(7, c2)
    assert_equal "Hello", c2.read(5)
  end

  def start_server(ru='persistent')
    config = Jubilee::Configuration.new(rackup: File.expand_path("../../apps/#{ru}.ru", __FILE__), instances: 1)
    @server = Jubilee::Server.new(config.options)
    q = Queue.new
    @server.start{ q << 1 }
    q.pop
    sleep 0.1
    @client = TCPSocket.new @host, @port
  end
end

redpajama_set_name: RedPajamaGithub


We are delighted to announce that E-Learning materials, workbooks and activities are now available through Ecordia. These can also be integrated and pre-loaded into assessment plans and work templates on the Ecordia system.
Please have a look at the library of available modules and courses here.
All materials are tried, tested and written by industry experts. New courses, e-learning content, workbooks and activities will be continually added.
We have received exceptional interest in the learning materials and anyone who has registered their interest and made an enquiry up until now – and until the end of April – we are offering 10% discount on your first purchase if made by the end July 2017.
● Are volume discounts available? Yes, each colour group of courses have volume discounts.
● How often are the materials updated? The materials are updated as often as required to ensure they meet with current qualification standards.
● How many candidates can access the material concurrently? There is no limit on concurrent access for your candidates.
● Is there a maximum number of candidates we can offer the material to? There is no maximum limit. All candidate accounts for your centre will be able to access the learning materials and workbooks.


text:
Q: Method to get a value out of a Dictionary, or create one if it does not exist I have a Dictionary>. Is there any function which gets the list at a particular key, and or creates a list if it does not exist. For example, this does not work:
Dictionary<string, List<string>> d = new Dictionary<string, List<string>>();
d["Bob"].Add("Fred");

Right now I'd have to do this:
Dictionary<string, List<string>> d = new Dictionary<string, List<string>>();
List<string> l = d["Bob"];
if(l == null) { l = d["Bob"] = new List<string>(); }
l.Add("Fred");

I've considered adding an extension method Get(T key), which would allow me to do this:
Dictionary<string, List<string>> d = new Dictionary<string, List<string>>();
d.Get("Bob").Add("Fred");

But I wanted to check to see if something like this doesn't already exist.
Looks like this is a dupe, that had a good answer:
.NET Dictionary: get or create new

A: You can create an extension method like:
public static void CreateNewOrUpdateExisting<TKey, TValue>(
    this IDictionary<TKey, TValue> map, TKey key, TValue value)
{
    map[key] = value;
}

Source:
Method to Add new or update existing item in Dictionary

redpajama_set_name: RedPajamaStackExchange


text:
Q: Webview loading outside screen? This code was working with another aspx form, now when I changed the form, it works in blackberry's webview however the android now boots a external browser, even know before it booted within the application.
webview = (WebView) findViewById(R.id.webView1);
    webview.getSettings().setJavaScriptEnabled(true);
    webview.setInitialScale (5);
    webview.loadUrl(URL);
    webview.requestFocus(View.FOCUS_DOWN);

why is it loading outside the browser now?

A: All you need is to implement shouldOverrideUrlLoading() . A snippet from my recent project:
public class WebViewCustom extends Activity {

WebView mWebView;
String mUrl;
String urlHistory;
    @Override
    protected void onCreate(Bundle savedInstanceState) {

        super.onCreate(savedInstanceState);

        setContentView(R.layout.lessons_page);
        mWebView = (WebView) findViewById(R.id.webview);
        mWebView.setWebViewClient(new WebViewOverrideUrl());
        mWebView.getSettings().setJavaScriptEnabled(true);
        mWebView.getSettings().setPluginsEnabled(true);
        mWebView.loadUrl("YOUR-URL-HERE");

    }

       private class WebViewOverrideUrl extends WebViewClient {
            @Override
            public boolean shouldOverrideUrlLoading(WebView view, String url) {
                view.loadUrl(url);
                return true;
            }
        }

}
Happy coding!

A: Presumably, your server is issuing a redirect. If you implement a WebViewClient and have it override shouldOverrideUrlLoading(), you can force the redirect to be loaded in the WebView itself.


text:
FeaturedMagazine
Islam and Slavery – Why Debates over Slavery are Matter to Everyone
Madina365 28/08/2019
For any system of belief that vests ultimate authority in the past, slavery is a big moral problem. That goes for all three of the monotheistic faiths, and even for civil creeds such as traditional American patriotism, which is now wrestling hard with the fact that human equality's most eloquent advocates, the republic's founders, were also slave-owners.
For several reasons, this dilemma is an acute one for Muslims, as emerges in a scholarly but digestible new book, "Slavery and Islam", by Jonathan Brown, a professor at Georgetown University and himself a Muslim convert. He focuses on both theology and history right up to the mid-19th century—when slavery became a bone of contention between European imperial powers, full of new-found abolitionist zeal, and traditional Muslim authorities across the Middle East and beyond. Like everything else about the Muslim encounter with European colonialism, this is a painful memory, and many Muslims insist that the European stance was patronising and hypocritical.
In certain cases, the Muslim sheikhs' response to colonial pressure involved a tart recourse to Islam's holy texts, in which the existence of slavery is taken as an inexorable feature of human society. If God tolerated this system, the traditional Islamic scholars said, it was surely not for any human authority to abolish it.
Others told their Western critics that slavery, as practised under Islam, was a far more humane phenomenon than the bondage endured by say, American plantation workers; therefore the Westerners had no moral standing.
Although this lies outside the scope of Mr Brown's book, present-day discussions about slavery are further complicated by the much broader sense in which the word has come to be used. The term "modern slavery" now encompasses human trafficking, especially for sexual exploitation, as well as the bonded labour imposed for debts, for example in India. The term also covers forced labour mandated by harsh states like North Korea. According to the United Nations, at least 40m people endure modern slavery of one form or another.
However traditional slavery, in which humans are treated as chattels, and bequeath their status to their children, does still exist, even though all countries have abolished it. The places where the social reality of servitude lingers on are mostly in a swathe across North Africa: for example Mauritania, Niger, the Central African Republic and Sudan. In Mauritania, slavery was formally abolished by the French colonists in 1905, and by the independent republic in 1981, but last year the country was rebuked by the African Union for failing to stamp it out.
Nasser Weddady, a Mauritanian-American activist who encourages civil-society movements across North Africa, says the subject is so emotional in his home region that it is hard to have a calm discussion. People either exaggerate slavery's persistence or deny it ever existed. Many younger Arab Muslims have accepted the argument that Islam never endorsed slavery, and become upset when presented with evidence to the contrary, he has discovered.
That makes it all the more important for scholars to examine the evidence through an objective historical lens, as Mr Brown sets out to do. In truth, he writes, there can be no doubt that Islam's founding texts accept and assume the existence of slavery. They also strongly encourage masters to free their slaves, as a way of atoning for sin or simply as a disinterested act of piety.
But keeping slaves is not condemned: it is considered to be a logical consequence of war, in which the men, women and children of the losing side are taken captive. It also seems clear from the texts that male householders are allowed to take female captives as concubines.
On the other hand, it is also clear that in Islam, man's natural condition is freedom; when an abandoned child is discovered, it is assumed to be free. But where a child's parentage is known, the status of servitude passes down the generations. Unless they are explicitly freed, the children of slaves can expect to spend their lives in bondage.
Despite all that, the vast majority of today's Muslim thinkers share the modern view that slavery is an absolute evil, whose abolition is to be welcomed. As Mr Brown carefully explains, they use many different arguments to reconcile this position with the older texts. Some stress that freedom for all was always the divine purpose, and that God only allowed slavery in the early days of Islam as a concession to the realities of the age.
Others insist that God never really approved of slavery at all, and that regulating an evil phenomenon is not the same as endorsing it. Others still assert that Islam can evolve. They stress the entitlement of Muslim scholars, after due deliberation, to make fresh moral pronouncements through a process of ijma or consensus. Some scholars emphasise the right of legitimate rulers to make liberating reforms. In other words, the adage that "man can never abolish what God allowed" has largely been dropped.
To people outside the world of Islam, or indeed outside the world of revealed religion, it may seem unimportant which line of exegesis is used to reconcile modern thinking about slavery with Islam's holy writ. The main thing, surely, is the conclusion: that slavery is now and always will be unacceptable.
But Mr Brown convincingly shows that theology matters, if only because any argument that can be constructed theologically can also be deconstructed. The terrorist movement known as Daesh (or Islamic State) regards the legitimacy of slavery under Islam as axiomatic, and questions the right of anyone who thinks otherwise to be considered Muslim. Appallingly, it claimed scriptural authority for the right of its fighters to rape female captives of an alien faith, such as the Yazidis.
The ISIS "caliphate" may have been destroyed, but the group's ideas also need to be opposed theologically. Non-Muslims are unlikely to make much contribution to the minutiae of debate about what this or that passage in the Koran really means, but they can at least offer encouragement from the sidelines whenever the matter is being addressed in good faith.
Correction: An earlier version of this article said that under Islamic law, the child of a free father and slave mother is considered a slave. In fact, such a child is deemed free.
Source: The Economist
Madina365
Madina365 is online magazine which mission is promotion of Islamic history and forgotten Islamic tradition such as liberty, freedom of thought and free market society.
Hayy ibn Yaqdhan and the European Enlightenment
Women and Markets in Ottoman Empire
The Libertarian Character of the Islamic Economy
Freedom of Religion and Apostasy in Islam
Why Israel cannot be called a democratic state
Cryptocurrency eBooks Economics Featured Magazine
© Copyright 2020, All Rights Reserved | MADINA365


text:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">

  <meta content="text/html; charset=utf-8" http-equiv=Content-Type>
  <title>CSS Fragmentation Module Level 3</title>

  <link href="http://purl.org/dc/terms/" rel=schema.dcterms>
  <link href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright"
   rel=dcterms.rights>
  <meta content="CSS Fragmentation Module Level 3" name=dcterms.title>
  <meta content=text name=dcterms.type>
  <meta content=2014-01-16 name=dcterms.date>
  <meta content="Rossen Atanassov" name=dcterms.creator>
  <meta content="Microsoft Corporation" name=dcterms.creator>
  <meta
   content="Elika J. Etemad"
   name=dcterms.creator>
  <meta content="Mozilla Corporation" name=dcterms.creator>
  <meta content=W3C name=dcterms.publisher>
  <meta content="http://www.w3.org/TR/2014/WD-css3-break-20140116/"
   name=dcterms.identifier>
  <link href=default.css rel=stylesheet type="text/css">
  <link href="http://www.w3.org/StyleSheets/TR/W3C-WD.css" rel=stylesheet
   type="text/css">

CSS Fragmentation Module Level 3

Breaking the Web, one fragment at a
    time

W3C Working Draft 16 January 2014

This version:

http://www.w3.org/TR/2014/WD-css3-break-20140116/

Latest version:

http://www.w3.org/TR/css3-break/

Editor's Draft:

http://dev.w3.org/csswg/css3-break/

Previous version:

http://www.w3.org/TR/2012/WD-css3-break-20120823/

Editors:

Rossen Atanassov, Microsoft Corporation, ratan@microsoft.com

Elika J.
     Etemad, Mozilla Corporation

Issues List:

http://wiki.csswg.org/spec/css3-break

Feedback:

www-style@w3.org
     with subject line "[css-break] <var>… message topic
     …</var>" (archives)

Copyright © 2014 W3C® (MIT, ERCIM,
    Keio, Beihang), All Rights Reserved. W3C liability,
    trademark
    and document
    use rules apply.

 Abstract

 This module describes the fragmentation model that partitions a flow
   into pages, columns, or regions. It builds on the Page model module and
   introduces and defines the fragmentation model. It adds functionality for
   pagination, breaking variable fragment size and orientation, widows and
   orphans.

 Status of this document

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 document was edited in place on 23 June 2014 to fix a wrong "Previous Version" link.

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.

The (archived) public
   mailing list www-style@w3.org (see
   instructions) is preferred
   for discussion of this specification. When sending e-mail, please put the
   text "css3-break" in the subject, preferably like this:
   "[css3-break] …summary of comment…"

This document was produced by the CSS Working Group (part of
   the Style Activity).

This document was produced by a group operating under the 5 February
   2004 W3C Patent Policy. 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.

 See the Changes section for significant changes
   since the previous draft.

 Table of contents

1.  Introduction

1.1.  Module
      Interactions

1.2.  Values

2.
    Fragmentation Model and Terminology

2.1.  Parallel
      Fragmentation Flows

2.2.  Nested
      Fragmentation Flows

3.  Controlling
    Breaks

3.1.  Breaks
      Between Boxes: the 'break-before' and
      'break-after' properties

 Generic Break
        Values

 Page Break Values

 Column Break
        Values

 Region Break
        Values

3.2.  Breaks Within
      Boxes: the 'break-inside' property

3.3.  Breaks
      Between Lines: 'orphans', 'widows'

3.4.  Page
      Break Aliases: the 'page-break-before',
      'page-break-after', and 'page-break-inside' properties

4.  Rules for
    Breaking

4.1.  Possible
      Break Points

4.2.  Types of
      Breaks

4.3.  Forced
      Breaks

4.4.  Unforced
      Breaks

4.5.  Optimizing
      Unforced Breaks

5.  Box Model for
    Breaking

5.1.
      Breaking into Varying-size Fragmentainers

5.2.  Adjoining
      Margins at Breaks

5.3.  Splitting
      Boxes

5.4.
      Fragmented Borders and Backgrounds: the 'box-decoration-break' property

5.4.1.  Joining
        Boxes for 'slice'

5.5.  Transforms,
      Positioning, and Pagination

6.  Conformance

6.1.  Document
      Conventions

6.2.
      Conformance Classes

6.3.  Partial
      Implementations

6.4.  Experimental
      Implementations

6.5.  Non-Experimental
      Implementations

6.6.  CR Exit
      Criteria

 Changes

 Acknowledgments

References

Normative
      references

Other references

Index

Property index

1.  Introduction

This section is not normative.

 In paged media (e.g., paper, transparencies, photo album pages, pages
   displayed on computer screens as printed output simulations), as opposed
   to
   continuous media, the content of the document is split into one or
   more discrete display surfaces. In order to avoid awkward breaks (such as
   halfway through a line of text), the layout engine must be able to shift
   around content that would fall across the page break. This process is
   called <dfn id=pagination>pagination</dfn>.

 In CSS, in addition to paged media, certain layout features such as regions [CSS3-REGIONS] and multi-column layout [CSS3COL] create
   a similarly fragmented environment. The generic term for breaking content
   across containers is <dfn id=fragmentation>fragmentation</dfn>. This
   module explains how content breaks across fragmentation containers (fragmentainers) such as pages and columns
   and how such breaks can be controlled by the
   author.

1.1.  Module Interactions

 This module replaces and extends the pagination controls defined in [CSS21] section 13.3
   and in [CSS3PAGE].

1.2.  Values

 This specification follows the  CSS property
   definition conventions from [CSS21]. Value types not defined in
   this specification are defined in CSS Level 2 Revision 1 [CSS21]. Other CSS
   modules may expand the definitions of these value types: for example [CSS3VAL], when
   combined with this module, adds the 'initial'
   value to the properties defined here.

 In addition to the property-specific values listed in their
   definitions, all properties defined in this specification also accept the

   inherit keyword as their property value. For readability it has not
   been repeated explicitly.

2.  Fragmentation Model
   and Terminology

<dfn id=fragmentation-container>fragmentation container</dfn> (<dfn
    id=fragmentainer>fragmentainer</dfn>)

 A box—such as a page box, column box, or region—that contains a
    portion (or all) of a fragmented
    flow. Fragmentainers can be pre-defined, or generated as needed.
    When breakable content overflows a fragmentainer in the block dimension,
    instead of overflowing it breaks into the next container in its fragmentation context.

<dfn id=fragmentation-context>fragmentation context</dfn>

 An ordered series of fragmentainers, such as created by a multi-column element, a
    chain of CSS regions, or
    a paged media display. A
    given fragmentation context can only have one block flow direction across
    all its fragmentainers.

<dfn id=fragmented-flow>fragmented flow</dfn>

 A content flow that is being laid out in a fragmentation context. The fragmented flow consists of the
    content of a (possibly anonymous) box called the <dfn
    id=fragmentation-root>fragmentation root</dfn>.

<dfn id=fragmentation-direction>fragmentation direction</dfn>

 The block flow direction of the fragmentation context, i.e. the
    direction in which content is fragmented. (In this level of CSS, content
    only fragments in one dimension.)

<dfn id=fragmentation0>fragmentation</dfn>

 The process of splitting a content flow across the fragmentainers that form a fragmentation context.

<dfn id=box-fragment>box fragment</dfn> or <dfn
    id=fragment>fragment</dfn>

 The portion of a box that belongs to exactly one fragmentainer. A box in continuous flow
    always consists of only one fragment. A box in a fragmented flow consists
    of one or more fragments.

<dfn id=remaining-fragmentainer-extent>remaining fragmentainer
    extent</dfn>

 The remaining extent in the fragmentainer available to a given
    element, i.e. between the end of preceding content in fragmentainer and the edge of the fragmentainer.

 Each <dfn id=fragmentation-break>fragmentation break</dfn> (hereafter,
   <dfn id=break>break</dfn>) ends layout of the fragmented box in the
   current fragmentainer and causes the
   remaining content to be laid out in the next fragmentainer, in some cases causing a
   new fragmentainer to be generated to
   hold the deferred content.

 Breaking inline content into lines is another form of
   fragmentation, and similarly creates box fragments when it breaks inline
   boxes across line boxes.
   However, inline breaking is not covered here; see [CSS21]/[CSS3TEXT].

2.1.  Parallel Fragmentation
   Flows

 When multiple flows are laid out parallel to each other, fragmentation
   is performed independently in each flow. For example, if an element is
   floated, then a forced break inside the float will not affect the content
   wrapping outside the float (except insofar as it may increase the height
   of the float).

 The following are examples of parallel flows whose contents will
   fragment independently:

The contents of a float vs. the content wrapping outside the float.

The contents of a float vs. the contents of an adjacent float.

The contents of each table cell in a single table row.

The contents of each grid item in a single grid row.

The contents of each flex item in a flex layout row.

The contents of absolutely-positioned elements that cover the same
    range of their containing block's fragmentation context.

 Content overflowing the content edge of a fixed-size box is considered
   parallel to the content after the fixed-size box. Such content fragments
   within the context of the box's fragmented
   flow following normal fragmentation rules, increasing the length
   of the fragmented flow as necessary.

2.2.  Nested Fragmentation
   Flows

 Breaking a fragmentainer
   <var>F</var> effectively splits the fragmentainer into two fragmentainers (<var>F1</var>
   and <var>F2</var>). The only difference is that the type of
   break between the two pieces <var>F1</var> and
   <var>F2</var> is the type of break
   created by the fragmentation
   context that split <var>F</var>, not the type of break normally
   created by <var>F</var>'s own fragmentation context.

3.  Controlling Breaks

 The following sections explain how breaks are controlled in a fragmented flow. A page/column/region
   break opportunity between two boxes is under the influence of the
   containing block's 'break-inside' property, the 'break-after'
   property of the preceding element, and the 'break-before'
   property of the following element. A page/column/region break opportunity
   between line boxes is under the influence of the containing block's 'break-inside',
   'widows', and 'orphans' properties. A
   fragmentation break can be allowed, forced, or discouraged depending on
   the values of these properties. A forced break overrides any break
   restrictions acting at that break point. In the case of forced page
   breaks, the author can also specify on which page (left or right)
   the subsequent content should resume.

 See the section on rules for breaking for
   the exact rules on how these properties affect fragmentation.

3.1.  Breaks Between Boxes:
   the 'break-before' and 'break-after'
   properties

     Name:

     <dfn id=break-before>break-before</dfn>, <dfn
      id=break-after>break-after</dfn>

     Value:

     auto | avoid | always | any | avoid-page | page | left | right |
      recto | verso | avoid-column | column | avoid-region | region

     Initial:

     auto

     Applies to:

     block-level elements, table row groups, table rows (but see prose)

     Inherited:

     no

     Percentages:

     N/A

     Media:

     visual

     Computed value:

     specified value

 These properties specify page/column/region break behavior before/after
   the generated box. The <dfn id=forced-break-values>forced break
   values</dfn> 'always', 'any', 'left', 'right', 'recto', 'verso', 'page', 'column' and 'region' create
   a forced break in the flow while the <dfn
   id=avoid-break-values>avoid break values</dfn> 'avoid', 'avoid-page',
   'avoid-column' and 'avoid-region' indicate that content should be kept
   together.

 Since breaks are only allowed between siblings, not between a box and
   its container (see Possible Break Points),
   a 'break-before' value on a first-child box is
   propagated to its container. Likewise a 'break-after' value on a last-child box is
   propagated to its container. (Conflicting values combine as defined below.) This propagation
   stops before it breaks through the nearest matching fragmentation context.

 Values for 'break-before' and 'break-after' are
   defined in the sub-sections below. User Agents must apply these properties
   to boxes in the normal flow of the fragmentation root. User agents
   should also apply these properties to floated boxes whose containing block
   is in the normal flow of the root fragmented element. User agents may also
   apply these properties to other boxes.

 Generic Break Values

 These values have an effect regardless of the type of fragmented
   context containing the flow.

'auto'

 Neither force nor forbid a break before/after the principal
    box.

'avoid'

 Avoid a break before/after the principal
    box.

'always'

 Always force a break (of all possible types, through all
    fragmentation contexts) before/after the principal
    box.

'any'

 Force a break of any type, whichever is the type of the deepest
    fragmentation context, before/after the principal
    box.

 Page Break Values

 These values only have an effect in paginated contexts; if the flow is
   not paginated, they have no effect.

'avoid-page'

 Avoid a page break before/after the principal
    box.

'page'

 Always force a page break before/after the principal
    box.

'left'

 Force one or two page breaks before/after the principal
    box so that the next page is formatted as a left page.

'right'

 Force one or two page breaks before/after the principal
    box so that the next page is formatted as a right page.

'recto'

 Force one or two page breaks before/after the principal
    box so that the next page is formatted as either a left page or a
    right page, whichever is second (according to the page progression) in a
    page spread.

'verso'

 Force one or two page breaks before/after the principal
    box so that the next page is formatted as either a left page or a
    right page, whichever is first (according to the page progression) in a
    page spread.

 Column Break Values

 These values only have an effect in multi-column contexts; if the flow
   is not within a multi-column context, they have no effect.

'avoid-column'

 Avoid a column break before/after the principal
    box.

'column'

 Always force a column break before/after the principal
    box.

 Region Break Values

 These values only have an effect in multi-region contexts; if the flow
   is not linked across multiple regions, these values have no effect.

'avoid-region'

 Avoid a region break before/after the principal
    box.

'region'

 Always force a region break before/after the principal
    box.

3.2.  Breaks Within Boxes: the
   'break-inside'
   property

     Name:

     <dfn id=break-inside>break-inside</dfn>

     Value:

     auto | avoid | avoid-page | avoid-column | avoid-region

     Initial:

     auto

     Applies to:

     elements in the normal flow that that establish formatting contexts,
      or are block containers, table row groups, or table rows

     Inherited:

     no

     Percentages:

     N/A

     Media:

     visual

     Computed value:

     specified value

 This property specifies page/column/region break behavior within the
   element's principal box. Values have the following meanings:

'auto'

 Impose no additional breaking constraints within the box.

'avoid'

 Avoid breaks within the box.

'avoid-page'

 Avoid a page break within the box.

'avoid-column'

 Avoid a column break within the box.

'avoid-region'

 Avoid a region break within the box.

3.3.  Breaks Between Lines:
   'orphans', 'widows'

     Name:

     <dfn id=orphans>orphans</dfn>, <dfn id=widows>widows</dfn>

     Value:

     <integer>

     Initial:

     2

     Applies to:

     block containers

     Inherited:

     yes

     Percentages:

     N/A

     Media:

     visual

     Computed value:

     specified value

 The 'orphans'
   property specifies the minimum number of line boxes in a block container
   that must be left in a fragment before a
   fragment break. The 'widows' property specifies the minimum number
   of line boxes of a block container that must be left in a fragment after a break. Examples of how they
   are used to control fragmentation breaks are given below.

 Only positive integers are allowed as values of 'orphans' and 'widows'. Negative values
   and zero are invalid and must cause the declaration to be ignored.

 If a block contains fewer lines than the value of 'widows' or 'orphans', the rule
   simply becomes that all lines in the block must be kept together.

3.4.  Page Break
   Aliases: the 'page-break-before', 'page-break-after', and 'page-break-inside' properties

For compatibility with CSS Level 2, UAs that
   conform to [CSS21] must alias the 'page-break-before', 'page-break-after', and 'page-break-inside' properties to 'break-before',
   'break-after',
   and 'break-inside' by treating the 'page-break-*' properties as shorthands for the 'break-*' properties with the following value mappings:

     Shorthand ('page-break-*') Values

     Longhand ('break-*') Values

     'auto | left | right | avoid'

     'auto | left | right | avoid'

     'always'

     'page'

4.  Rules for Breaking

 A fragmented flow may be broken across fragmentainers at a number of possible break points. In the case of forced breaks, the UA is required to break the
   flow at that point. In the case of unforced
   breaks, the UA has to choose among the possible breaks that are
   allowed.

 Some content is not fragmentable, for example many types of replaced
   elements [CSS21] (such as images or video),
   scrollable elements, or a single line of text content. Such content is
   considered <dfn id=monolithic>monolithic</dfn>: it contains no possible
   break points. In addition to any content which is not fragmentable, UAs
   may consider as monolithic any elements
   with 'overflow' set to 'auto' or 'scroll' and any
   elements with 'overflow: hidden' and a
   non-'auto' logical height
   (and no specified maximum logical height).

 To guarantee progress, fragmentainers are assumend to have a minimum
   extent of 1px regardless of their used size.

4.1.  Possible Break Points

 Fragmentation splits boxes in the block flow dimension. In
   block-and-inline flow, breaks may occur at the following places:

Class A

 Between sibling boxes of the following types:

Block-parallel Fragmentation

 When the block flow direction of the siblings' containing block is
      parallel to that of the fragmentation context: in-flow block-level
      boxes, a float and an immediately-adjacent in-flow or floated box,
      table row group boxes, table row boxes, multi-column column row boxes.

Block-perpendicular Fragmentation

 When the block flow direction of the siblings' containing block is
      perpendicular to that of the fragmentation context: table column group
      boxes, table column boxes, multi-column column boxes.

Class B

 Between line boxes inside a block container box.

Class C

 Between the content edge of a block container box and the outer edges
    of its child content (margin edges of block-level children or line box
    edges for inline-level children) if there is a (non-zero) gap
    between them.

 There is no inherent prioritization among these classes of
   break points. However, individual break points may be prioritized or
   de-prioritized by using the breaking
   controls.

 The UA is not required to fragment the contents
   of monolithic elements, and may instead
   either slice the element's graphical representation as necessary to
   fragment it or treat its box as unbreakable and overflow the
   fragmentainer. In both cases it must treat the element as having 'break-inside: avoid', i.e. only slice or overflow at
   the fragmentainer edge if there are no possible
   break points on the fragmentainer.

 When paginating, if there are no possible break points below the top of
   the page, and not all the content fits, the UA may break anywhere in order
   to avoid losing content off the edge of the page.

 Other layout models may add breakpoints to the above
   classes. For example, [CSS3-FLEXBOX] adds certain
   points within a flex formatting context to classes A and C.

4.2.  Types of Breaks

 There are different types of breaks in CSS, defined based on the type
   of fragmentainers they span:

<dfn id=page-break>page break</dfn>

 A break between two page boxes. [CSS3PAGE]

<dfn id=spread-break>spread break</dfn>

 A break between two page boxes that are not associated with facing pages. A
    spread break is always also a page break. [CSS3PAGE]

<dfn id=column-break>column break</dfn>

 A break between two column boxes.
    Note that if the column boxes are on different pages, then the break is
    also a page break. Similarly, if the
    column boxes are in different regions, then the break is also a region break. [CSS3COL]

<dfn id=region-break>region break</dfn>

 A break between two regions. Note that
    if the region boxes are on different pages, then the break is also a page break. [CSS3-REGIONS]

 A fifth type of break is the <dfn id=line-break>line
   break</dfn>, which is a break between two line boxes.
   These are not covered in this specification; see [CSS21] [CSS3TEXT].

4.3.  Forced Breaks

 A <dfn id=forced-break>forced break</dfn> is one explicitly indicated
   by the style sheet author. A forced
   break occurs at a class A break point
   if, among the 'break-after' properties specified on or
   propagated to the earlier sibling box and the 'break-before'
   properties specified on or propagated to the later sibling box there is at
   least one with a forced break value. (Thus a forced break
   value effectively overrides any avoid break value that also
   applies at that break point.)

 When multiple forced break
   values apply to a single break point, they combine such that all
   types of break are honored. When 'left',
   'right', 'recto',
   and/or 'verso' are combined, the value
   specified on the latest element in the flow wins.

 A page break must also occur at a class A break point if the last line box above this
   margin and the first one below it do not have the same value for 'page'. See [CSS3PAGE]

 When a forced break occurs, it forces ensuing content into the next
   fragmentainer of the type associated with the break, breaking through as
   many fragmentation contexts as necessary until the specified break types
   are all satisfied. If the forced break is not contained within a matching
   type of fragmentation context, then the forced break has no effect.

4.4.  Unforced Breaks

 While breaking controls can force
   breaks, they can also discourage them. An <dfn id=unforced-break>unforced
   break</dfn> is one that is inserted automatically by the UA in order to
   prevent content from overflowing the fragmentainer. The following rules
   control whether unforced breaking at a possible
   break point is allowed:

Rule 1

 A fragmented flow may break at a class A break
    point only if all the 'break-after' and 'break-before'
    values applicable to this break point allow it, which is when at least
    one of them forces a break or when all of them are 'auto'.

Rule 2

 However, if all of them are 'auto' and a
    common ancestor of all the elements has a 'break-inside'
    value of 'avoid', then breaking here is not
    allowed.

Rule 3

 Breaking at a class B break point is allowed
    only if the number of line boxes between the break and the start of the
    enclosing block box is the value of 'orphans' or more, and the number of line
    boxes between the break and the end of the box is the value of 'widows' or more.

Rule 4

 Additionally, breaking at class B or class C break points is allowed only if the 'break-inside'
    property of all ancestors is 'auto'.

 If the above doesn't provide enough break points to keep content from
   overflowing the fragmentainer, then
   rules 1, 2 and 4 are dropped in order to find additional breakpoints. In
   this case the UA may use the 'avoid's that are
   in effect at those points to weigh the appropriateness of the new
   breakpoints; however, this specification does not suggest a precise
   algorithm.

 If that still does not lead to sufficient break points, rule 3 is
   dropped as well, to find still more break points.

4.5.  Optimizing Unforced
   Breaks

While CSS3 requires that a fragmented flow must break at allowed break
   points in order to avoid overflowing the fragmentainers in its
   fragmentation context, it does not define whether content breaks at a
   particular allowed break. However, it is
   recommended that user agents observe the following guidelines (while
   recognizing that they are sometimes contradictory):

Break as few times as possible.

Make all fragmentainers that don't end with a forced break appear to
    be equally filled with content.

Avoid breaking inside a replaced element.

 Suppose, for example, that the style sheet contains 'orphans : 4', 'widows : 2',
    and there is space for 20 lines (line boxes) available at the bottom of
    the current page, and the next block in normal flow is considered for
    placement:

 If the block contains 20 line boxes or fewer, it should be placed on
     the current page.

 If the block contains 21 or 22 line boxes, the second fragment of
     the paragraph must not violate the 'widows' constraint, and so the second
     fragment must contain at least two line boxes; likewise the first
     fragment must contain at least four line boxes.

 If the block contains 23 line boxes or more, the first fragment
     should contain 20 lines and the second fragment the remaining lines. But
     if any fragment of the block is placed on the current page, that
     fragment must contain at least four line boxes and the second fragment
     at least two line boxes.

 Now suppose that 'orphans' is '10',
    'widows' is
    '20', and there are 8 lines available at the
    bottom of the current page:

 If the block contains 8 lines or fewer, it should be placed on the
     current page.

 If the block contains 9 lines or more, it must NOT be split (that
     would violate the 'orphans' constraint), so it must move as a
     block to the next page.

5.  Box Model for Breaking

 The sizing terminology used in this section is defined in [CSS3-SIZING].

5.1.  Breaking into
   Varying-size Fragmentainers

 When a flow is fragmented into varying-size fragmentainers, the
   following rules are observed for adapting layout:

 Intrinsic sizes are calculated and maintained across the entire
    element. Where an initial containing block size is needed to resolve an
    intrinsic size, assume the size of the first fragmentainer defining a
    fragmentation context.

 Layout is performed per-fragmentainer, with each fragmentainer
    continuing progress from the breakpoint on the previous, but
    recalculating sizes and positions using its own size as if the entire
    element were fragmented across fragmentainers of this size. Progress is
    measured in percentages (not absolute lengths) of used/remaining
    fragmentainer extent and in amount of used/remaining content. However,
    when laying out monolithic elements, the
    UA may instead maintain a consistent measure and resolved extent across
    fragmentainers.

 Fragments of boxes that began on a previous fragmentainer must obey
    placement rules with the additional constraint that fragments must not be
    positioned above the before edge of the fragmentainer. If this results in
    a box's continuation fragment shifting away from the before edge of the
    fragmentainer, then 'box-decoration-break:
    clone', if specified, wraps the fragment with the box's margin
    in addition to its padding and border.

First page
+----------------------------------+
|########### ......... ############|
|#         # .....     #          #|
|#  left   # .......   #   right  #|
|#  float  # ......... #   float  #|
|#         # ........  #          #|
|#         # ......... #          #|
|#         # ........  #          #|
|#,,,,,,,,,# ......... #,,,,,,,,,,#|
+----------------------------------+

Second page

+-----------------+
|#`````````# .... |
<!--    -->|#  left   # ...  |
<!--    -->|#  float  # .... |
<!--    -->|#  cont.  # .... |
<!--    -->|########### ...  |
<!--    -->|.... #``````````#|
|...  #  right   #|
|.... #  float   #|
|.... #  cont.   #|
|.... ############|
|...............  |
|.......          |

 Since document order of elements doesn't change during
   fragmentation, fragments are processed following the same rules that apply
   to continuous media. In particular, the order of floats is preserved
   across all fragments and follows the same rules as defined in CSS 2.1 9.5.

Below are listed (informatively) some implications of these rules:

 Boxes (including tables) fullfilling layout constraints at their
    fill-available or percentage-based size may change measure across
    pages.

 Boxes (including tables) fulfilling layout constraints at their
    min-content, max-content, or absolute-length size will
    maintain their measure across pages.

 A block-level continuation fragment may be placed below the top of
    the page if, e.g. it establishes a block formatting context and is placed
    beside a float and both it and the float continue onto a narrower page
    that is too narrow to hold both of them side-by-side.

 An element adjacent to a preceding float on one page may wind up
    above the float's continuation on the next page if, e.g. that float is
    pushed down because it no longer fits side-by-side with an earlier float
    that also continues onto this narrower page.

 A left float may appear on a page before the remaining
    fragments of a preceding right float if that right float does not fit on
    the earlier page. However another right float will be forced down until
    the preceding right float's remaining fragment can be placed.

Here is an example that shows the use of percentage-based progress:
    Suppose we have an absolutely-positioned element that is positioned
    'top: calc(150% + 30px)' and has 'height: calc(100% - 10px)'. If it is placed into a
    paginated context with a first page height of 400px, a second page of
    200px, and a third page of 600px, its layout progresses as follows:

First, the top position is resolved against the height of the first
     page. This results in 630px. Since the first page has a height of only
     400px, layout moves to the second page, recording progress of 400/630 =
     63.49% with 36.51% left to go.

Now on the second page, the top position is again resolved, this time
     against the height of the second page. This results in 330px. The
     remaining 36.51% of progress thus resolves to 120.5px, placing the top
     edge of the element 120.5px down the second page.

Now the height is resolved against the second page; it resolves to
     190px. Since there are only 79.5px left on the page, layout moves to the
     third page, recording progress of 79.5/190 = 41.84%, with 58.16% left to
     go.

On the third page, the height resolves to 590px. The remaining 58.16%
     of progress thus resolves to 343.1px, which fits on this page and
     completes the element.

5.2.  Adjoining Margins at
   Breaks

 When an unforced break occurs between block-level boxes, any margins
   adjoining the break truncate to the remaining fragmentainer
   extent. When a forced break occurs there, adjoining margins before
   the break are truncated, but margins after the break are preserved.

5.3.  Splitting Boxes

 When a box breaks, its content box extends to fill any remaining fragmentainer
   extent (leaving room for any margins/borders/padding applied by
   'box-decoration-break: clone') before the
   content resumes on the next fragmentainer. (A fragmentation break that pushes
   content to the next fragmentainer
   effectively increases the extent of a box's contents.)

 The extra extent contributed by fragmenting the box (i.e.
   the distance from the break point to the edge of the fragmentainer) contributes progress
   towards any specified limits on the box's extent.

 The diagrams below illustrate filling the remaining fragmentainer
    extent.

+-----------------+  +-----------------+
| ............... |  | ............... |
| ..............  |  | ..............  |
| ............... |  | ............... |
| ..............  |  | ..............  |
| ............    |  | ............    |
| ############### |  | ############### |
| #  this box   # |  | #  this box   # |
| #  is         # |  | #  is         # |  << auto-height block
| #  fragmented # |  | #  fragmented # |
| #             # |  | #             # |  <-+
| #             # |  | #             # |    | remaining
| #             # |  | #             # |    | blank
| #             # |  | ############### |    | space
+-----------------+  +-----------------+  <-+

5.4.  Fragmented Borders
   and Backgrounds: the 'box-decoration-break' property

     Name:

     <dfn id=box-decoration-break>box-decoration-break</dfn>

     Value:

     slice | clone

     Initial:

     slice

     Applies to:

     all elements

     Inherited:

     no

     Percentages:

     N/A

     Media:

     visual

     Computed value:

     as specified

     Animatable:

     no

 When a break (page/column/region/line) splits a box,
   the 'box-decoration-break' property controls

whether the box's margins, borders, padding, and other decorations
    wrap the broken edges of the box fragments

how the background
    positioning area [CSS3BG] is derived from the box
    fragments and how the element's background is drawn within them.

 Values have the following meanings:

<dfn id=clone>'clone'</dfn>

 Each box fragment is independently wrapped with the border and
    padding. The 'border-radius' and 'border-image' and 'box-shadow', if any, are applied to each fragment
    independently. The background is drawn independently in each fragment of
    the element. A no-repeat background image will thus be rendered once in
    each fragment of the element.

<dfn id=slice>'slice'</dfn>

No border and no padding are inserted at a break; no box-shadow is
     drawn at a broken edge; 'border-radius'
     does not apply to its corners; and backgrounds and the 'border-image' are rendered for the whole box as
     if the box were unbroken. The effect is as though the element were
     rendered with no breaks present, and then sliced by the breaks
     afterward.

Two possibilities for 'box-decoration-break': on the left, the value
    'slice', on the right the
    value 'clone'.

UAs may also apply 'box-decoration-break' to control rendering at
   bidi-imposed breaks, i.e. when bidi reordering causes an inline to split
   into non-contiguous fragments. Otherwise such breaks are always handled as
   'slice'.

 For inline elements, which side of a fragment is considered
   the broken edge is determined by the parent element's inline progression
   direction. For example, if an inline element whose parent has 'direction: rtl' breaks across two lines, the
   left edge of the fragment on the first line will be the broken
   edge. (Note in particular that neither the element's own 'direction' nor its containing block's 'direction' is used.) See [CSS3-WRITING-MODES].

5.4.1.  Joining Boxes for
   'slice'

For 'box-decoration: slice', backgrounds (and
   'border-image') are drawn as if applied to
   a composite box consisting of all of the box's fragments reassembled in
   visual order. This theoretical assembly occurs after the element has been
   laid out (including any justification, bidi reordering, page breaks,
   etc.). To assemble the composite box...

For boxes broken across lines

 First, fragments on the same line are connected in visual order.
    Then, fragments on subsequent lines are ordered according to the
    element's inline base direction and aligned on the element's
    dominant baseline. For example, in a left-to-right containing block
    ('direction' is 'ltr'), the first fragment is the leftmost fragment on
    the first line and fragments from subsequent lines are put to the right
    of it. In a right-to-left containing block, the first fragment is the
    rightmost on the first line and subsequent fragments are put to the left
    of it.

For boxes broken across columns

 Fragments are connected as if the column boxes were glued together in
    the block flow direction of the multi-column element.

For boxes broken across pages

 Fragments are connected as if page content areas were glued together
    in the block flow direction of the root element.

For boxes broken across regions

 Fragments are connected as if region content areas were glued
    together in the block flow direction of the principal writing
    mode of the region chain.

If the box fragments have different widths (heights, if the fragments
   are joined horizontally), then each piece draws its portion of the
   background assuming that the whole element has the same width (height) as
   this piece. However, if the used height (width) of an image is derived
   from the width (height) of the box, then it is calculated using the widest
   fragment's width and maintained as a fixed size. This ensures that
   right-aligned images stay aligned to the right edge, left-aligned images
   stay aligned to the left edge, centered images stay centered, and
   stretched images cover the background area as intended while preserving
   continuity across fragments.

5.5.  Transforms, Positioning,
   and Pagination

 Fragmentation interacts with layout, and thus occurs before
   relative positioning [CSS21], transforms [CSS3-TRANSFORMS], and any
   other graphical effects. Such effects are applied per fragment: for
   example, rotation applied to a fragmented box will calculate a rotation
   origin for each fragment and independently rotate that fragment around its
   origin. However, the separation and transfer of page boxes should
   occur last; thus a transformed fragment that spans pages should
   be sliced at the page breaks and print in its entirety rather than being
   clipped by its originating page.

 There's an issue of how to handle fragments consisting
   entirely of overflowing content. See discussion.

 Absolute positioning affects layout and thus interacts with
   fragmentation. Both the coordinate system and absolutely-positioned boxes
   belonging to a containing block will fragment across pages in the same
   fragmentation flow as the containing block.

 UAs are not required to correctly position boxes that span a fragmentation break and whose
   before edge position depends on where the box's content fragments.
   UAs with memory constraints that prevent them from manipulating an entire
   document in memory are not required to correctly position
   absolutely-positioned elements that end up on a previously-rendered page.

6.  Conformance

6.1.  Document Conventions

 Conformance requirements are expressed with a combination of
   descriptive assertions and RFC 2119 terminology. The key words "must",
   "must NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "should", "should NOT", "RECOMMENDED", "may", and
   "OPTIONAL" in the normative parts of this document are to be
   interpreted as described in RFC 2119. However, for readability, these
   words do not appear in all uppercase letters in this specification.

 All of the text of this specification is normative except sections
   explicitly marked as non-normative, examples, and notes. [RFC2119]

 Examples in this specification are introduced with the words "for
   example" or are set apart from the normative text with
   class="example", like this:

This is an example of an informative example.

 Informative notes begin with the word "Note" and are set apart from
   the normative text with class="note", like this:

Note, this is an informative note.

6.2. Conformance
   Classes

Conformance to CSS Fragmentation is defined for three conformance
   classes:

<dfn id=style-sheet title="style sheet!!as conformance class">style
    sheet</dfn>

 A CSS
    style sheet.

<dfn id=renderer>renderer</dfn>

 A UA
    that interprets the semantics of a style sheet and renders documents that
    use them.

<dfn id=authoring-tool>authoring tool</dfn>

 A UA
    that writes a style sheet.

 A style sheet is conformant to CSS Fragmentation if all of its
   declarations that use properties defined in this module have values that
   are valid according to the generic CSS grammar and the individual grammars
   of each property as given in this module.

 A renderer is conformant to CSS Fragmentation if, in addition to
   interpreting the style sheet as defined by the appropriate specifications,
   it supports all the features defined by CSS Fragmentation by parsing them
   correctly and rendering the document accordingly. However, the inability
   of a UA to correctly render a document due to limitations of the device
   does not make the UA non-conformant. (For example, a UA is not required to
   render color on a monochrome monitor.)

 An authoring tool is conformant to CSS Fragmentation if it writes style
   sheets that are syntactically correct according to the generic CSS grammar
   and the individual grammars of each feature in this module, and meet all
   other conformance requirements of style sheets as described in this
   module.

6.3.  Partial Implementations

 So that authors can exploit the forward-compatible parsing rules to
   assign fallback values, CSS renderers must treat as
   invalid (and
   ignore as appropriate) any at-rules, properties, property values,
   keywords, and other syntactic constructs for which they have no usable
   level of support. In particular, user agents must not
   selectively ignore unsupported component values and honor supported values
   in a single multi-value property declaration: if any value is considered
   invalid (as unsupported values must be), CSS requires that the entire
   declaration be ignored.

6.4.  Experimental
   Implementations

 To avoid clashes with future CSS features, the CSS2.1 specification
   reserves a prefixed
   syntax for proprietary and experimental extensions to CSS.

 Prior to a specification reaching the Candidate Recommendation stage in
   the W3C process, all implementations of a CSS feature are considered
   experimental. The CSS Working Group recommends that implementations use a
   vendor-prefixed syntax for such features, including those in W3C Working
   Drafts. This avoids incompatibilities with future changes in the draft.

6.5.  Non-Experimental
   Implementations

 Once a specification reaches the Candidate Recommendation stage,
   non-experimental implementations are possible, and implementors should
   release an unprefixed implementation of any CR-level feature they can
   demonstrate to be correctly implemented according to spec.

 To establish and maintain the interoperability of CSS across
   implementations, the CSS Working Group requests that non-experimental CSS
   renderers submit an implementation report (and, if necessary, the
   testcases used for that implementation report) to the W3C before releasing
   an unprefixed implementation of any CSS features. Testcases submitted to
   W3C are subject to review and correction by the CSS Working Group.

 Further information on submitting testcases and implementation reports
   can be found from on the CSS Working Group's website at
   http://www.w3.org/Style/CSS/Test/. Questions should be directed to the

   public-css-testsuite@w3.org mailing list.

6.6.  CR Exit Criteria

 For this specification to be advanced to Proposed Recommendation, there
   must be at least two independent, interoperable implementations of each
   feature. Each feature may be implemented by a different set of products,
   there is no requirement that all features be implemented by a single
   product. For the purposes of this criterion, we define the following
   terms:

independent

 each implementation must be developed by a different party and cannot
    share, reuse, or derive from code used by another qualifying
    implementation. Sections of code that have no bearing on the
    implementation of this specification are exempt from this requirement.

interoperable

 passing the respective test case(s) in the official CSS test suite,
    or, if the implementation is not a Web browser, an equivalent test. Every
    relevant test in the test suite should have an equivalent test created if
    such a user agent (UA) is to be used to claim interoperability. In
    addition if such a UA is to be used to claim interoperability, then there
    must one or more additional UAs which can also pass those equivalent
    tests in the same way for the purpose of interoperability. The equivalent
    tests must be made publicly available for the purposes of peer review.

implementation

 a user agent which:

implements the specification.

is available to the general public. The implementation may be a
      shipping product or other publicly available version (i.e., beta
      version, preview release, or "nightly build"). Non-shipping product
      releases must have implemented the feature(s) for a period of at least
      one month in order to demonstrate stability.

is not experimental (i.e., a version specifically designed to pass
      the test suite and is not intended for normal usage going forward).

 The specification will remain Candidate Recommendation for at least six
   months.

 Changes

The following significant changes were made since the 29 August 2012
   Working Draft:

Added definition of 'box-decoration-break' (moved from [CSS3BG]) and
    defined better handling of aspect-ratio-sized images in variable-sized
    fragments.

Added 'any' value to 'break-before' and
    'break-after'.

Defined that boxes extend to the bottom of
    the page when broken.

Defined breaking of transformed/positioned
    content.

Defined 1px minimum extent of fragmentainers to ensure progress.

Clarified fragmentation of parallel
    flows.

Defined handling of overflowing content (as parallel content).

Clarified float fragmentation in
    varying-size fragmentainers.

Various other clarifications.

 Acknowledgments

 The editors would like to thank Mihai Balan, Michael Day, Alex
   Mogilevsky, Shinyu Murakami, Florian Rivoal, and Alan Stearns for their
   contributions to this module. Special thanks go to the former [CSS3PAGE]
   editors Jim Bigelow (HP), Melinda Grant (HP), Håkon Wium Lie (Opera), and
   Jacob Refstrup (HP) for their contributions to this specification, which
   is a successor of their work there.

References

Normative references

[CSS21]

Bert Bos; et al. Cascading Style
    Sheets Level 2 Revision 1 (CSS 2.1) Specification. 7 June
    2011. W3C Recommendation. URL: http://www.w3.org/TR/2011/REC-CSS2-20110607

[CSS3-REGIONS]

Vincent Hardy; Rossen Atanassov; Alan Stearns. CSS
    Regions Module Level 1. 28 May 2013. W3C Working Draft. (Work
    in progress.) URL: http://www.w3.org/TR/2013/WD-css3-regions-20130528/

[CSS3-TRANSFORMS]

Simon Fraser; et al. CSS
    Transforms Module Level 1. 26 November 2013. W3C Working
    Draft. (Work in progress.) URL: http://www.w3.org/TR/2013/WD-css-transforms-1-20131126/

[CSS3BG]

Bert Bos; Elika J. Etemad; Brad Kemper. CSS
    Backgrounds and Borders Module Level 3. 24 July 2012. W3C
    Candidate Recommendation. (Work in progress.) URL: http://www.w3.org/TR/2012/CR-css3-background-20120724/

[CSS3COL]

Håkon Wium Lie. CSS
    Multi-column Layout Module. 12 April 2011. W3C Candidate
    Recommendation. (Work in progress.) URL: http://www.w3.org/TR/2011/CR-css3-multicol-20110412

[CSS3PAGE]

Melinda Grant; et al. CSS Paged
    Media Module Level 3. 14 March 2013. W3C Working Draft. (Work
    in progress.) URL: http://www.w3.org/TR/2013/WD-css3-page-20130314/

[RFC2119]

S. Bradner. Key
    words for use in RFCs to Indicate Requirement Levels. Internet
    RFC 2119. URL: http://www.ietf.org/rfc/rfc2119.txt

Other references

[CSS3-FLEXBOX]

Tab Atkins Jr.; Elika J. Etemad; Alex Mogilevsky. CSS
    Flexible Box Layout Module. 18 September 2012. W3C Candidate
    Recommendation. (Work in progress.) URL: http://www.w3.org/TR/2012/CR-css3-flexbox-20120918/

[CSS3-SIZING]

Tab Atkins Jr.; Elika J. Etemad. CSS
    Intrinsic & Extrinsic Sizing Module Level 3. 27 September
    2012. W3C Working Draft. (Work in progress.) URL: http://www.w3.org/TR/2012/WD-css3-sizing-20120927/

[CSS3-WRITING-MODES]

Elika J. Etemad; Koji Ishii. CSS
    Writing Modes Module Level 3. 15 November 2012. W3C Working
    Draft. (Work in progress.) URL: http://www.w3.org/TR/2012/WD-css3-writing-modes-20121115/

[CSS3TEXT]

Elika J. Etemad; Koji Ishii. CSS Text
    Module Level 3. 13 November 2012. W3C Working Draft. (Work in
    progress.) URL: http://www.w3.org/TR/2012/WD-css3-text-20121113/

[CSS3VAL]

Håkon Wium Lie; Tab Atkins; Elika J. Etemad. CSS
    Values and Units Module Level 3. 30 July 2013. W3C Candidate
    Recommendation. (Work in progress.) URL: http://www.w3.org/TR/2013/CR-css3-values-20130730/

Index

authoring tool, 6.2.

avoid break values, 3.1.

box-decoration-break, 5.4.

box fragment, 2.

break, 2.

break-after, 3.1.

break-before, 3.1.

break-inside, 3.2.

'clone', 5.4.

column break, 4.2.

forced break, 4.3.

forced break values, 3.1.

fragment, 2.

fragmentainer, 2.

fragmentation, 1., 2.

fragmentation break, 2.

fragmentation container, 2.

fragmentation context, 2.

fragmentation direction, 2.

fragmentation root, 2.

fragmented flow, 2.

line break, 4.2.

monolithic, 4.

orphans, 3.3.

page break, 4.2.

pagination, 1.

region break, 4.2.

remaining fragmentainer extent, 2.

renderer, 6.2.

'slice', 5.4.

spread break, 4.2.

style sheet

as conformance class, 6.2.

unforced break, 4.4.

widows, 3.3.

Property index

     Property

     Values

     Initial

     Applies to

     Inh.

     Percentages

     Media

     box-decoration-break

     slice | clone

     slice

     all elements

     no

     N/A

     visual

     break-after

     auto | avoid | always | any | avoid-page | page | left | right |
      recto | verso | avoid-column | column | avoid-region | region

     auto

     block-level elements, table row groups, table rows (but see prose)

     no

     N/A

     visual

     break-before

     auto | avoid | always | any | avoid-page | page | left | right |
      recto | verso | avoid-column | column | avoid-region | region

     auto

     block-level elements, table row groups, table rows (but see prose)

     no

     N/A

     visual

     break-inside

     auto | avoid | avoid-page | avoid-column | avoid-region

     auto

     elements in the normal flow that that establish formatting contexts,
      or are block containers, table row groups, or table rows

     no

     N/A

     visual

     orphans

     <integer>

     2

     block containers

     yes

     N/A

     visual

     widows

     <integer>

     2

     block containers

     yes

     N/A

     visual


text:
Arrangements for PP-7 by-polls finalised
Islamabad - The arrangements for holding free, fair and transparent by-elections in PP-07 Taxila (Rawalpindi-VII) on Monday (today) have been finalised by the Election Commission of Pakistan (ECP).
The seat had been fallen vacant due to the death of Muhammad Siddique Khan, a member of Punjab Assembly of Pakistan Tehreek-e-Insaf. In general election of 2013, Siddique Khan had defeated Interior Minister Chaudhry Nisar Ali Khan by a thin margin.
The district coordination officer has already announced local holiday in Taxila and adjacent areas to enable voters to use their right to franchise in hassle-free manner. The government and private educational institutes would remain closed in the district; however district courts would remain open on Monday.
According to the schedule, polling will start at 8:00am on Monday and will continue till 5:00 pm without any break. As many as 167 polling stations have been set up in the constituency. A total of 2,000 police officers will be deployed in the constituency to provide security to voters. The contingents of Elite force will also be deployed to ensure free, fair and transparent elections. The training of polling staff has already been completed. Haji Malik Muhammad Umer Farooq of Pakistan Muslim League Nawaz (PML-N) and Ammar Siddique Khan of Pakistan Tehreek-e-Insaf (PTI) and Chaudhary Kamran Aslam of Pakistan People's Party are in the run.
Arrangements for matches finalised
Security arrangements finalised for Eid prayers
Ahead of local polls, PTI struggles to come out of internal mess
Arrangements for Marathon 2020 reviewed


The holidays are here and they're just as packed with stress as they are with family time and delicious food. While we definitely advocate responsible drinking, a cocktail or glass of whiskey is known to help ease the tension between your conspiracy theory-loving uncle and your easy-to-anger cousin and every other uncomfortable interaction bound to happen during the holidays. Plus, booze makes a great gift.
But, if you're a booze novice, you might feel a little bit overwhelmed when it comes to gift shopping. Fear not, we at Mandatory are here to help. We've scoured the internets to find the best and greatest gifts for the booze-lover in your life. Check out all of our favorite boozy gifts below.
If you have a friend or family member on your gift list who enjoys making cocktails at home, this is the perfect gift. The kit includes a hammered shaker, wood banded jigger, strainer, and a bar spoon. Once you give this gift, they can start cranking out bar-quality cocktails as this is the only barware set they'll need. Get it here for $78.
For the craft beer fan in your life: Microbrewed Beer of the Month Club. A membership to the club will give your friend or family member 12 full-sized bottles of difficult-to-find, delicious, craft beer every months from breweries all over the country. Get it here for $479.40.
This Double Gold Medal winner at the 2018 San Francisco Spirits Awards is the bolder, higher-ABV brother of the Bulleit Bourbon we all know and love. It's not for the whiskey novice as it's barrel-strength, uncut, and unfiltered. It's the perfect gift for the bourbon aficionado on your list. Get it here for $59.99.
Flying is tough and full of stress. You just spent hours sitting in a crowded airport, you deserve a cocktail. Cocktail Carry On puts everything you need to make high-quality cocktails (except for the booze) in an easy-to-carry tin. Just order a mini bottle of bourbon on your flight. The kit already contains a recipe card, spoon/muddler, aromatic bitters, can sugar, and a linen coaster. Get it here for $18.
This cognac is exclusive to the U.S. market. It's limited-edition and the perfect gift for the cognac fan in your life and the first creations from Cognac's new eighth generation master blender Renaud Fillioux de Gironde. It's blended from a single batch and sits at 86 proof. Get it here fo $110.
This limited-edition whisky from Speyburn is one of the best value whiskies currently available. Winner of multiple awards, it's made from whisky aged in first fill American Oak ex-bourbon casks. It's rich, smooth, and a great whisky for the Scotch fan in your life. Get it here for $44.
If you've seen the news lately, you've heard of the panic surrounding Japanese whisky. Experts are claiming that there isn't enough supply to keep up with the demand. We guess that now is the perfect time to stock up. Buy a Bottle of Toki for a friend or family member and keep one for yourself. The perfect whisky for a highball or slow sipping, Toki is a great gateway whisky someone hoping to branch out a bit. Get it here for $39.99.
When drinkers think of Scotland, we usually think of Scotch whisky. But, in the last few years, gin has become huge in the country. One of the best is Botanist. Made by whisky-makers Bruichladdich, Botanist features 22 hand-foraged botanicals from the island of Islay where it's produced. Get it here for $39.99.
This set of four whiskey glasses is a Huckberry exclusive. The perfect gift for whiskey fans, each glass features a different topographical impression of a different American mountain. They include Half Dome, Denali, Mount Rainer and Mount Whitney. Get it here for $65.
The second book from Alex Day, David Kaplan, and Nick Fauchald, Cocktail Codex is the must-have book for home mixologists and professional bartenders alike. Just like the name describes, it's a guide to creating some of the most well-known cocktails as well as numerous originals. Get it here for $40.


Smashwords – Books Tagged "fidelity"
These results show books which have been specifically tagged with this keyword. You can also try doing a general search for the term "fidelity" .
Betty is a young and loving wife, so slim and fertile, willing to go into the workforce and do whatever is necessary to succeed.
Le noveli yathola uMklomelo wesiThathu emcintiswaneni wokubhalwa kwezincwadiowawuhlelwe nguMnyango Wezobuciko, Amasiko Nezokuvakasha wesiFundazwesaKwazulu-Natali ngokubambisana nabashicileli bakwa-Nasou Via Afrika ngonyaka we-2007.
The best advice on a plethora of issues anyone could ask for.
Short fiction. In all the decades they had been married, he had never cheated on her, nothing so banal. Yet his fixation on a long-departed younger model at last became more than she could stand.
Take three women and listen to the stories they tell here for the first time. Hear how unremarkable lives can become quite remarkable when they strip away the hair, the clothes, the makeup, the smile and reveal themselves for who they really are. Mixing their laughter with tears, each one struggles, each one wrestles with the past and fears the future. But which one of them has true hope?
The American democratic experience is about preserving government "of the people, by the people, for the people". Politicking mores has always been a strategy until the ocean floors scum is burning the bedfellow and the train station for invitations to jail. The half of it finds you innocent. Am I dam with you seeking His "end times",blood money & crypt flowers like it was the end of the world.
Meet the Pierces, a middle-aged mixed-race couple who've staked their ground in suburbia, with careers, SUV, dog and 2.1 children. Stir in a dash of fatigue and a pinch of cynicism, and you have a recipe for domestic disaster. Enter Liane, young, white, beautiful. Elton Pierce, an ad exec who has devoted his working life to the manipulation of desire, finds himself helpless in Liane's presence.


Description Las Posadas is an annual holiday program presented at the Eugene and Marylyn Glick Indiana History Center by the Indiana Historical Society, Eiteljorg Museum, and several other community organizations. Featured here are congregants of Christ Church Cathedral performing a "pastorela" (shepherd's play).
Notes Use of this image is restricted to projects related to Destination Indiana. Bicentennial Train image.


text:
Michael Jackson Documentary Shocks Fans
In the #MeToo era, Leaving Neverland publicizes sexual assault allegations against the King of Pop.
Alondra Bravo and Adriana Nicole Hernandez, Staff Writer
Adriana Nicole Hernandez
Home Box Office (HBO)'s new documentary Leaving Neverland details allegations that pop icon Michael Jackson sexually assaulted multiple young boys during the '80s and '90s, raising a new controversy in the #MeToo movement.
The four-hour documentary, directed by Dan Reed, was released on January 25, 2019 and tells the story of Wade Robson and James Safechuck, two young men who were allegedly abused by Jackson. Leaving Neverland shocked a number of Jackson's fans, including Mary Murton.
"I thought it was a bunch of B.S.," Murton stated. "[I thought it was just] another person trying to exploit and cash in on Michael after his death, especially since one of the men already testified in favor of Michael."
Anastacia Musante, a Middle College student at Canada College, takes an opposite perspective. She notes that the events described in the documentary might be true.
"I think that the things said in the documentary could be true because of how detailed and intensive the accusations were," Musante explained.
For long-time fans, the documentary might have been an eye-opener of who their idol truly was.
"I already heard about all the rumors on him being a child molester… so I have always been a little bit skeptical on if he's a good person," stated Andrew Johnson, a senior at Woodside High School.
Aliyah Brambila, a junior from American High School, is also unsurprised.
"Over the years of there has been rumors… so, at this point, it's like, 'Okay, this has to be true,'" Brambila added.
When HBO released the first part of the two-part documentary, people on social media, especially on Twitter, expressed their strong opinions.
"No matter how beloved the abuser, it is imperative to believe survivors," a user from Twitter wrote.
Since the release, radio stations have removed Jackson's music, clothing lines such as Louis Vuitton have dropped Jackson's items, and even musicals based on Jackson's music have been canceled.
"I'll always be a fan of Michael's music and what he produced," Murton said. "His musicality is like no other, and there will be no one like him again. But [looking beyond music], I personally lost respect for him."


text:
Q: The tag "tags" is incredibly redundant I've noticed there's about 1000 questions on Stack Overflow with the tag tags. This is (in my opinion) a pretty useless tag, as it's kind of used for everything. I've seen it on all sorts of things:

*

*Tagging friends

*Miscellaneous markup language (XML, HTML, etc.) tags

*Image tags

*DICOM tags

*MySQL Tag Tables

*Various other software's "tag" systems (WordPress, Stack Overflow, etc.)

The word "tag" and ultimately the word "tags" is so generic that it as a tag itself seems completely useless. Understandably it IS useful here on Meta Stack Overflow, as there are discussions about the Tagging system implemented on the Stack Overflow sites. Is there any way to mass remove it and block it from being recreated? I realize that ultimately the tags and even the posts are owned and maintained by the community at large, but... this one just doesn't seem that it should exist without at least a prefix ("friend-tags", "XML-tags", "image-tags", etc.).
Thoughts? Ideas?

A: The tag "tags" (or "tagging" or similar) seems a reasonable tag to add if your question is about how to implement a database design / UI for users to tag content.
It maybe used incorrectly sometimes, but I don't think that the tag itself is useless.

A: To me this depends on whether you feel the tag defines the context of a question on its own. In some situations I think it is inevitable that a tag will have different meanings depending on the context it is used.
Just changing the tag to be more specific isn't going to help because when someone is in a context, they don't necessarily realise that they need to be aware of other contexts. So to them, at that moment, tag means image-tag not XML-tag and even if they knew it could be mixed up with XML-tag, they may not know that image-tag is the more specific version they want.
To that end, a tag cannot be enough in all circumstances to give a question its entire context or in fact, to give the tag itself its entire context. Instead it is the group of tags collectively and the question content that give the overall context.


text:
Tag Archives: South America
Br4zil
It's a knockout. And, as the canopy of shade creeps diagonally across pitches from Manaus in the north to Porto Alegre in the south, we have borne witness to the birth of the "cooling break", whose very name refreshes those of us at home, where temperatures are not in the thirties and humidity a lot less than 66%. The hallucinations constantly threatened if the players don't rehydrate are all happening to us, the armchair spectators. With the group stages over and my Guardian World Cup Guide fastidiously spidered with numbers, we're at that point where every match counts. Even, on a low level, Costa Rica Greece, which I forewent last night in order to catch up on Glastonbury, but turned out to have gone to dratted penalties (5-3 to Costa Rica). Aside from the sight of Adrian Chiles in tight shorts with his legs wide apart under the garden table last night on ITV, during the channel's unique on-the-patio bit before the game (he dresses to the left, cock fans), there's little to complain about. Suárez is long gone – subsequently joined, connectedly, by Uruguay, after a sound thrashing by Colombia. The narrative (and I love a narrative, as has been pointed out to me on Twitter) is that one superstar is gone, and another is born: 22-year-old striker James Rodriguez, whose 29th-minute volley is being talked about as the goal of the tournament – and that's with stiff competition.
As already established, the post-England phase of any international cup is always my favourite part. No more residual stress about whether or not "our boys" can prove, or improve, their world ranking, and the sheer joy of being able to cheer on whichever team I like, switching allegiance mid-game if I fancy. I do not blame the whole of Uruguay for the developmental and denial issues of Suárez, although the shine did come off them as a result of his toothmanship and when Colombia went one up with That Goal, I pinned my allegiance to their yellow shirts, perhaps in subliminal solidarity with the hickey-marked Italy, or with Gloria from Modern Family.
Either way, poster boy Rodriguez, who's now scored in all four of his World Cup games, delivered a magic moment when he chested, then left-footed a 25-yarder past the Uruguay goalie. To quote from the write-up by the BBC's Phil McNulty, who will have seen and described more goals than I ever will do, "It was the most perfect combination of technique and talent, drawing gasps from around this iconic stadium when it was replayed on the four giant screens that hang from the roof of the vast bowl."
What a game Brazil Colombia will be on Friday (Colombia's first ever quarter final). Another serious South American derby, especially now that Brazil have recovered their mojo. Their victory against Chile in the first knockout match may have been decided on penalties – just checking: nobody wants a World Cup match to go to penalties do they? – but it was no kickabout in the 120 minutes preceding.
A goal apiece from Brazil's Alan Davies-haired David Luis and Chile's Sanchez evened things out in the first half-hour, but the turning point came in the second half: a disallowed goal from Hulk, who appeared to use his bicep before getting one past Claudio Bravo, an anatomical subtlety identified and penalised by brave British ref Howard Webb, whose shiny head always makes me think of my last editor at the NME, and my own Uncle Phil, who was a professional referee in his prime, which seemed supercool to me as a boy. (We witnessed him spraying the medicinal-smelling Ralgex onto his legs before a game, which was an eye-opener. It was like he operated in another world and yet he was Uncle Phil.) Webb was at least balanced: he denied a penalty appeal by both sides. Much for the pundits to unpick at half-time.
Those penalties. It was hot out there and even those used to the stifling humidity and wilting temperatures didn't really want to play on for another 30 minutes. But there it was. Somebody must always go home empty handed from now on. Or empty-armed in Hulk's case. If this game had been blocked and written in a writers' room, then Hulk, so ambiguously denied his second, would-be-decisive goal, would have scored Brazil's winning penalty, thus redeeming himself, and allowing Howard Webb to get home from work safely and sleep more easily. As it was, Hulk's shot was saved by the estimable Bravo – bravo! – but it was Julio Cesar's denial of Sanchez's penalty kick – hail, Cesar! – that sealed it at 3-2 for the hosts. Tense, yes, a ridiculous in-out way to decide a match so steeped in chance and subtlety, but the shootout was not without nuance: Neymar's mindfuck shuffle was quality entertainment.
In our house, we're still unable to get over the image of Holland's star striker as a character in Game Of Thrones: Iron Robin. But this is a minor impediment to the enjoyment of watching him lead a seriously below-par team to a squeaked victory against my favourites Mexico. I decided they were my favourites during the first half, when they gave as good as they got and their first quarter final in 28 years seemed a delicious possibility. I love to watch Holland pass, but they couldn't break the Mexican wall. If I had more analytical skills, I'd tell you precisely why like Glenn Hoddle did at half-time when it was still 0-0, but I find it difficult to follow him. It was 38.8C out there, and fans unlucky enough to be sat in the sun literally abandoned their seats. If both teams had agreed only to play in the shade throughout, I would have taken my hat off to them, and then put it back on again for protection. It may have explained the Dutch failure to convert. The Netherlands is not a hot country, and the orangemen (sorry) who aren't bald, have shaggy dog hair – neither ideal in a bake-off.
I know this much, Mexico's keeper Guillermo Ochoa was the man of the match. Commentator Sam Matterface may have mocked him for looking like something out of an "80s fitness video" (he favours a thick headband to keep his head looking like a tied-up bunch of fresh carrots), but his quick-witted ability saw a parade of Dutch chances punched, slapped or body-bounced off the line. When Mexico's Dos Santos put them one-up at the start of the second half from the fabled 25 yards (I don't even know what a yard looks like), things really hotted up. Holland didn't equalise until the 88th minute – despite Iron Robin's repeated attempts to lie down in the penalty area and feign injury – but the man we call V2 Schneider (but is actually called Wesley Sneijder) turned it around in style. Hallucinatory extra time seemed inevitable, but Robin finally had his way, earned a penalty after a Marquez trip-up, and Easter Island-browed substitute Klaas Jan Huntelaar scored the winner from the spot. As you will see from this picture, the wrong player is called Hulk.
Because I remained a loyal Mexico supporter to the end, telling anyone who'd listen, including our cat, that they deserved to go through, I was crestfallen by Holland's zero-hour comeback, as juicy and dramatic as it was. Also, as with the Oscars, I like surprises and dislike sure things. But with whole sections of the crowd burnt to a crisp like extras in Threads and welded to their plastic seats like puddles of face paint, Holland celebrated not just getting through to the quarter finals, but to a potentially comfy tie against either Costa Rica or Greece (it turned out to be the former).
On with the games.
Posted in World Cup | Tagged Brazil, football, Game of Thrones, Holland, ITV, South America, sport, TV, TV commentary, World Cup, World Cup 2014 | 7 Replies