text:
While I stay far away from American fast food chains abroad (as I would at home), I'm not the type of traveler to feverishly stick to a diet of food only from the local culture when I travel. I get a kick out of seeing how a restaurant in Ghana might make a Chinese dish or what a beach side restaurant in France considers to be an "American" sandwich. I've had many laughs, some nice surprises, and only a few stomach aches from experiencing the ways people of one culture reinterpret food of a completely different culture.
A recurring theme of this kind of food exploration is an often masochistic quest to find a great San Francisco burrito abroad. As a misguided youth, I was once anti-burrito, but somewhere along the way, I realized what I was missing. Now I love being based in the best place to find them and on the road, burritos have become an elusive taste of home that can't seem to be recreated too far beyond.
But that hasn't stopped me from trying. On Cat Ba Island in Vietnam's Halong Bay and in Aguas Calientes, Peru, I ordered burritos that were tasty enough, but beyond the incorporation of tortilla-like component, probably didn't deserve to be called burritos. In Oaxaca, curiosity led me to order a "burrita" and I ended up with with something that resembled an oversized rolled taco with beans. I won't even get started on the Tex-Mex restaurant in Salvador, Brazil where the salsa was actually marinara sauce.
One day in Berlin as I thumbed through my guidebook, I saw something that looked promising — a restaurant called Dolores, directly inspired by San Francisco's Mission District where burritos as the world often knows them first rose to popularity (while the burrito originated in Northern Mexico and the flavors are certainly of the country, you'll be hard pressed to find the kind of internationally known burrito you're looking for in most of Mexico). I had to check out.
I ventured out on a rainy evening to walk to the Dolores in Mitte, quickly realizing it was much further from my hostel than it looked on the map. I got pretty soaked on the way and I was happy to take refuge in the cheery and brightly colored restaurant.
But I was immediately wary when I looked up at the menu. Tofu was featured prominently. Sorry vegetarians and vegans… it's not that I don't think there should be options for you, but that's just not what you expect to see first on the list of protein choices at a burrito establishment. They also had a salsa entitled "smoky peanut" which just confused me. I did have to give them props for carrying Anchor Steam beer, a San Francisco-made brew that you wouldn't expect to see in Germany.
I decided to keep things simple and try a classic chicken burrito. To wash it down, I ordered a glass of tamarind-strawberry juice. It was thicker than what I would've expected of an agua fresca, but tasty nonetheless. I sat down at a table in the next room and enjoyed looking at the outdated but easily recognizable MUNI map of the Mission District that was turned into wallpaper.
The burrito came with the tortilla loosely wrapped and it was covered in paper. Strike one, it was not tightly wrapped in foil. This is important, especially when it comes to eating a burrito with grace with your hands rather than a fork and knife. Strike two, the flavor of the chicken was way off. It tasted like there were hints of curry in the seasoning! Strike three, a lot of effort was put into making it healthy. While great Mission burritos aren't necessarily greasy, they're a whole lot more moist and a whole lot less self conscious. If you want a healthy burrito, you eat half and save the other half for another time.
Based on some of choices there, I suspect Dolores's downfall was likely finding inspiration from a more yuppified San Francisco taqueria like Papalote rather than the more basic taquerias that often produce better flavors with less hype. And I'm sure recipes were created to cater to a more local taste rather a visitor from San Francisco seeking nostalgia or a challenge.
As you may have guessed, my opinion on this place was dictated by a fair amount of burrito snobbery, a smug side affect that can be picked up from spending an indeterminate amount of time in San Francisco. I loved the restaurant's name and clear influence, but unfortunately those aspects raised my expectations. If nothing else, it was fun to see an attempt to recreate a part of my city abroad. It was more of a entertaining adventure in "What did you expect?" than a disappointment. So once again, I ended up with a highly edible burrito-inspired wrap, but not exactly a burrito. The quest continues.
Is there a taste of home that you crave more on the road in part because you can't find it? Do you have a funny story of trying a non-local food while traveling and getting a plate of something strange?


text:
|Message view
|« Date » · « Thread »
|« Date » · « Thread »
|Gopal Sharma <Gopal.Sha...@Sun.COM>
|Re: Forrest (a.k.a. xml.apache.org 2.0)
|Mon, 17 Dec 2001 13:58:08 GMT
Hi, I thought it worth mentioning it here once guys are going to start the great job of making the apache.org alive. We have suggested a heading *committer info*, but we also need one more header *info for new committers* on the top level. Gopal ----------------------- SUN Microsystems, India Stefano Mazzocchi wrote: > [sorry for cross-post: this is a general issue, but I'd like the cocoon > people to know what I'm doing so that they might give me a hand :)] > > I started the effort that will, hopefully, bring us a much more useful > documentation system for xml.apache.org and, hopefully, to the entire > ASF, even if political and ego obstacles will get in the way. > > I personally don't care: this effort is mainly to create a better > documentation infrastructure following the goals outlined below. I > started the Cocoon project three years ago exactly for this reason and > now that has all the features I needed, I think I can attack the problem > from a very wide angle. > > The site building system will be targetted toward xml.apache.org, but > I'll keep a very broad perspective, making it possible to adapt the > system to other apache.org projects with very few changes. > > BIG DISCLAIMER: however, whether this happens or not, I personally don't > care. For sure, don't count on me wasting my time on fighting about 'my > DTD is better than yours' or 'my system is > faster/smaller/cleaner/easier-to-use/more-extensible than yours'. > > I'll come up with a system that works and then you guys will vote on > what to do. I consider this an exercise to present full Cocoon > potentials (that, objectively, beat the pants out of all the other > systems used around Apache) but nothing more than this. > > - o - > > Ok, now that I stated this, let's get into the effort goals. > > GOALS > ----- > > 1) Speed: current xml.apache.org is slow. Empirical studies on learning > processes indicate that if a page takes more than 10 seconds on a 56Kbs > modem, the cognitive experience is degrated. > > 2) Coherence: current xml.apache.org is extremely incoherent. Again, > it's easy to understand that lack of coherence between subprojects docs > is perceived (and sometimes reflects!) lack of cooperation. > > 3) Navigation: the navigation experience on current xml.apache.org is a > nightmare. There is no way to perceive the basic elements of spatial > navigation: where am I? where can I go? how do I go back? how do I go > there? > > 4) Depth: the current xml.apache.org page layout forces a flat hierarchy > of levels. The current Cocoon documentation somewhat extends this, but > the visual look doesn't reflect the notion. Visual codes are extremely > important to allow a easy and immediate navigation even at the deepest > level. > > 5) Usefulness: xml.apache.org contains powerful software but it's not > powerful in itself. It should be a window on the information useful for > both users and developers, along with friendly behavior, such as > print-friendly versions of the single pages and of the whole > per-subproject documentation, pagination of long articles, > site-restricted search, graphs of project-related data and so on. > > 6) Simplicity: xml.apache.org is done by volunteers, on all levels. > Nobody is directly paid to do this. Not even myself. So, if the above > goals are met, but the system is not simple and immediate to use for > those who have to maintain and update the information, the result is > void over a short period of time. > > 7) Extensibility, Flexibility, Modularity: web sites, just as software, > are living entities that adapt on their environment. The build system > must not restrict the ability to evolutionary extend the information > architecture. > > 8) URI Solidity and Future Compatibility: URIs are contracts between the > publisher and the user. Human users have the ability to estimate the > long-term validity of these contracts and 'route around' eventual broken > links, while machine users do not. The goal is to come up with a system > that allows to generate a web site with strong URIs. > > > Design Decisions > ---------------- > > staticity: even if I think that the availability of a dynamic publishing > system would be beneficial, considering the web site load, the load of > the apache machines and the state of the JVM for FreeBSD and the > political problems behind all this, it's *must* easier (at least for > now) to have a static version of the site batch-produced and then placed > into the web-serving space. > > automaticity: the site will be automatically generated out of files > stored into CVS. The idea is to have GUMP-like nagging features that > send email to the various mail lists using XML validation to estimate > the 'integrity' of the docs placed. > > For this reason, in honor of Sam Ruby's great work, and for the > resonation with 'forest', thus a huge number of trees (i.e. XML files), > I call this effort "Forrest". > > I believe that together, Forrest and Gump, will help bringing apache > quality one step up (moreover, as in the name, forrest wraps gump and > will publish its generated data, providing more overall coherence) > > - o - > > separation of concerns > ---------------------- > > There are three concern islands, here is a list of their duties. > > subproject > ========== > > each subproject should provide: > > 3.a) a 'description' file that includes information on the codebase, its > description, its released versions, its CVS modules, its CVS tags, its > mail lists and its documentations (yes, a subproject might have more > than one, think of Xerces1/Xerces2, Xalan1/Xalan2, Cocoon1/Cocoon2). > [proposed filename: /description.xml] > > 3.b) a 'committers info' file that includes information on the > committers, along with a short bio, an email address and a picture of > them. [proposed filename: /committers.xml] > > 3.c) a 'change log' file that includes information on changes and > software relases [proposed filename: /changes.xml] > > 3.d) a 'todo list' file that includes the information on things to do > and who volunteered for doing it [proposed filename: /todo.xml] > > 3.e) a 'news' file that includes events and useful information that > should be made available to the general public. > > then, for each documentation (location is get from the description > file): > > 3.f) a 'table of content' that indicates the hierarchical sequence of > the files and where to find them into the CVS repository (for each > documentation). This is kept as a single file to allow document writers > to maintain 'coherence' and visualize the entire part. This is > equivalent to the stylebook book.xml file but with full nesting > capabilities. > > 3.e) the pages that componse the documentation (their location is get > from the ToC file) > > Log scanner > =========== > > The log scanner is a set of scripts that scan the logs from the CVS, the > mail lists and the web site to gather information on: > > 1) mail list activity (subscribers and messages) > 2) web site activity (hits and downloads) > 3) CVS activity (general commits, commits per person) > > This scanner provides this information in a simple format that can be > easily fed into the documentation building system. > > Build system > ============ > > The build system will: > > 1) aggregate, filter and otherwise adapt the information collected from > the various subprojects CVS modules, from the log scanner and from the > GUMP run into static HTML files (for the browser pages), static PDF > files (for print-friendly versions) and JPEG images (for graphs). > > 2) generate navigation information in all the pages > > 3) check validation of all the required XML files and send nag messages > to the mail lists if failure occurs. > > 4) generate httpd-related corollary files (.htaccess, header.html, > footer.html and so on). > > 5) upload the parts that didn't have failures online. > > The goal is to have the system running completely autonomous: this > follows the Gump approach. [Sam, I'll need your help here, since I don't > have an account on nagoya] > > - o - > > Things to decide > ================ > > 1) DTDs > ------- > > The Cocoon project already has DTDs for 'documentation','change > logs','todo list' and 'specifications'. They mainly use XHTML tags and > are very easy to learn (they are an expansion of the original stylebook > DTDs, so it's pretty easy to automatically adapt existing stylebook > documents to this improved DTD, still keeping the simplicity we had > before). > > The rest of the required DTDs (description, news and ToC) must be agreed > upon (i'll work on them in the next days) > > 2) URIs > ------- > > In order to achieve the future-compatible goal, we must come up with a > guideline for URIs. > > For example, the Cocoon project had /cocoon and /cocoon2, then Cocoon > 2.0 was released final and we moved /cocoon2 into /cocoon and /cocoon > into /cocoon1, creating a shit-load of broken links. > > Two solutions where proposed (add your own if you have more) > > a) use version specific information and use mod_rewrite to adapt. for > example > > xml.apache.org/cocoon/1.8.2/index.html > xml.apache.org/cocoon/2.0b1/index.html > xml.apache.org/cocoon/2.0b2/index.html > xml.apache.org/cocoon/2.0rc1/index.html > xml.apache.org/cocoon/2.0rc2/index.html > xml.apache.org/cocoon/2.0/index.html > > then > > xml.apache.org/cocoon/ -> xml.apache.org/cocoon/2.0/index.hml > > Problem is that while those versioned URI are never broken, the > version-less redirected URI is changed for each release and doesn't > reduce broken links. Also, it's probably easier to download the required > version and look into the shipped docs and results in unnecessary big > web sites. > > b) use semantic-meaningful yet version-less URIs > > xml.apache.org/cocoon/previous/ -> points to the previous generation > docs > xml.apache.org/cocoon/ -> points to the latest docs > xml.apache.org/cocoon/next/ -> points to the next generation docs > > which removes the need to have keep all the docs versions online, yet > provides the ability to have both versions the latest one and the > previous generation (for Cocoon would be Cocoon 1.8.2, Cocoon 2.0, > Cocoon 2.1-dev today). > > The problem of broken links isn't solved since everytime there is a > transition, there is a chance of breaking previously established links > if the docs ToC changes from one generation to the next. > > 3) layout > --------- > > The layout previously proposed on this list was a solution to the speed > problem but I couldn't adapt it to the depth needs identified in the > rest of the goals. > > So, I resurrected my rusty web design skills and came up with the layout > you find attached. I've tested it on IE 5.5, NS 4.78 and Moz 0.9.5 on > win2k. > > Feedback, suggestions and criticisms are appreciated. > > 4) CVS location and mail list discussions > ----------------------------------------- > > Just like Gump which is not a subproject on its own, Forrest doesn't > deserve that status neither as long as it remains a single-man show (and > my experience tells me it will very likely remain so if the above goals > are met) > > At the same time, just like Gump, it requires a CVS space. > > Possible places are: > > 1) xml-site > 2) xml-forrest > 3) xml-site2 > > for mail list discussions, solutions are: > > 1) email@example.com > 2) firstname.lastname@example.com > 3) firstname.lastname@example.com > 4) email@example.com > > Please, add your comments/suggestions and your votes where a decision is > required. > > Thank you. > > -- > Stefano Mazzocchi One must still have chaos in oneself to be > able to give birth to a dancing star. > <firstname.lastname@example.com> Friedrich Nietzsche > -------------------------------------------------------------------- --------------------------------------------------------------------- In case of troubles, e-mail: firstname.lastname@example.com To unsubscribe, e-mail: firstname.lastname@example.com For additional commands, e-mail: firstname.lastname@example.com
|View raw message

subset: commoncrawl


text:
A simple yet significant luxury in one's wardrobe, jewelry is meant to be effortlessly worn and celebrated, not be tucked away in a box. Each Sethi Couture design is purposefully imagined with the intention of elevating everyday life while embodying heirloom quality that can be cherished and passed down for generations to come.
Sethi Couture is designed by both Pratima and Prerna Sethi, using natural color diamonds, alongside beautiful white rose, briolette, and old mine cuts. Elegant jewels are created with lively hues and unexpected cuts. Our signature style depicts an old world charm yet contemporary glamour, evoking a rich history and timelessness. Set upon the backdrop of 18kt gold, the captivating pieces transcend time, place, and occasion.
Christine K's jewelry is clean, simple, feminine with a touch of modern flair. Christine K's custom diamond rings gives you the option to create your own unique jewelry. The perfect piece is waiting for you to design from our pre-order section. Christine's jewelry is perfect for celebrating achievements, love, and life itself.
Radiant jewelry is the perfect way to remind yourself of the beauty in life and of great memories. Christine K's jewelry line is inspired from simple, modern, and feminine style. Browse our excellent selection of designs, and you will find something to fall in love with in minutes.
Deutsch & Deutsch offering a wide selection of Jewelry, Watches, Wedding Rings, Necklaces, Diamond, Engagement Rings & Earrings. Our stores are located in El Paso, Houston, Laredo and McAllen, Texas.
The Deutsch & Deutsch tradition of hard work and ingenuity has been the driving force behind its evolution from a modest 1920's tourist shop in Mexico into becoming respected as one of the most prominent jewelers in Texas and the United States. Our stores are located in El Paso, Houston, Laredo and McAllen, Texas.
Deutsch & Deutsch is not only a jewelry and watch store, it is a company that bases its ideology on the principle of being closely involved with its customers and on becoming part of their special life moments. Our slogan "Where Life Happens" expresses our interest in becoming a proactive element in the community and the effort we put in becoming an important element in our customers' lives. We have perfect gifts for every special life occasion.
Timeless Timepieces
At Deutsch & Deutsch we pride ourselves in offering a wide selection of premium timepieces from the most respected watch makers on the planet. As official jeweler of brands like Rolex, Tag Heuer, Cartier, Bvlgari, Hublot, Officine Panerai, IWC and TechnoMarine, we can find a watch to suit even the most particular of clients.
The dinosaur Gallery is a museum with many items that are millions of years old. Located in Del Mar, California the shop sells unique and hard to find fossils, crystals, minerals and items from all over the world. A must stop by shop museum attraction in San Diego, N. County.
At Dinosaur Gallery we supply a one of a kind experience in displaying and selling unique items and rarities, such as, fossils, minerals, corals, crystals, opals, sculptures,


text:
Is there any way to set a bold font for page menu bar?
Couldn't find it at Theme options
Click here to register or to donate.
Auto self-registration is not available here - far too many spammers. This forum has many, many backlinks and because of that there is an intense desire among spammers to drop their links here.
« [SOLVED] different templates for "each" pages | Create a Page Template that displays Only One Page Menu Item »


text:
Three... Extremes (2004)
Three…Extremes is a compilation horror film comprised of short versions of feature films by master directors from the HKSAR, Korea and Japan.
Edited to about 40 minutes from its feature length, Dumplings is a deliciously creepy, thought provoking piece from one of Hong Kong's best directors, Fruit Chan Goh. If you can imagine that the beautiful Bai Ling could look in the mirror and see Hau Woon-Ling in her reflection, then you have an idea of the nature of the secret ingredient of Aunt Mei's famous dumplings. Director Chan's master stroke of genius is the casting of Miriam Yeung Chin-Wah. I never would have thought, from all her romantic comedy work, that she had this performance in her.
From Korea, comes Cut, directed by Park Chan-Wook, a quite gruesome work that is very unique. Internationally acclaimed master director Miike Takashi's Box is the third short film from Japan.


text: The Department of Environmental Sciences at Emory University, Atlanta, GA, seeks applicants for a full-time lecture-track position (Lecturer) with a focus on field teaching, beginning Fall 2017. We are open to a wide range of disciplinary or interdisciplinary academic backgrounds relevant to field teaching in environmental sciences, geosciences, ecology, or related fields. The successful candidate will have a Ph.D. granted by the time of the offer letter and demonstrate a commitment to excellence in undergraduate teaching in an innovative interdisciplinary environment. The successful applicant will advise students and teach introductory and upper-level undergraduate courses with a focus on teaching outdoor-based courses. Such courses could take place in and around the Emory campus—which has excellent resources for field teaching—as well as further afield, from the state of Georgia to around the world. We particularly welcome applicants with field-based research experience with undergraduate students, and interest or experience in community engagement and/or discipline-based education research. We also encourage applications from candidates with a strong track record of teaching and mentoring students from under-represented groups. The initial appointment will be made for a period of three years with potential for promotion to Senior Lecturer after 6 years (in exceptional cases candidates could be considered at this rank). Please see: http://college.emory.edu/home/administration/policy/lecturer.html for details about lecture-track appointments at Emory. The successful candidate will join a friendly and cohesive faculty group of tenure-track and lecture-track faculty (http://www.emory.edu/ENVS/) and will be expected to contribute to the academic life of the department, the College of Arts and Sciences, and the University through service and academic committees. Applicants should submit a cover letter; CV; two-page teaching statement; and the names and contact information of three references. Submit all application materials via Interfolio (http://apply.interfolio.com/37109). Evaluation of candidates will begin on November 14, 2016 and will continue until the position is filled; applications received up to 30 days after review begins will be given full consideration. Questions related to the position (but not application materials) should be addressed to: envs.search at emory.edu. Geoscience-focused applicants may also be interested to apply to a different position in Environmental Sciences / Geosciences at Emory University's Oxford campus, 40 miles east of Atlanta: https://sjobs.brassring.com/1033/ASP/TG/cim_jobdetail.asp?partnerid=25066&siteid=5449&areq=65862br. Emory is an Equal Opportunity/Affirmative Action/Disability/Veteran employer. Women, minorities, persons with disabilities and veterans are particularly encouraged to apply. ----------------------------------------------------------- Berry J. Brosi, Ph.D. Winship Distinguished Associate Professor Department of Environmental Sciences Emory University brosilab.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ucar.edu/pipermail/es_jobs_net/attachments/20161017/2583a418/attachment.html