fix pushing to github

config/wsgi.py

@@ -22,19 +22,14 @@ except ImportError:
 
 os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'config.settings')
 
-# Patch for WeasyPrint libraries
+# Patch for WeasyPrint libraries (libgobject-2.0, pango, cairo, etc.)
-try:
+for lib_name in ['gobject-2.0', 'pango-1.0', 'cairo', 'harfbuzz', 'fontconfig']:
-    import ctypes
+    try:
-    import ctypes.util
+        path = ctypes.util.find_library(lib_name)
-    for lib in ['gobject-2.0', 'pango-1.0', 'cairo', 'harfbuzz', 'fontconfig']:
-        path = ctypes.util.find_library(lib)
         if path:
-            try:
+            ctypes.CDLL(path)
-                ctypes.CDLL(path)
+    except Exception:
-            except OSError:
+        pass
-                pass
-except Exception:
-    pass
 
 from django.core.wsgi import get_wsgi_application
 

manage.py

@@ -16,19 +16,16 @@ def main():
 
     os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'config.settings')
     
-    # Patch for WeasyPrint libraries
+    # Patch for WeasyPrint libraries (libgobject-2.0, pango, cairo, etc.)
-    try:
+    import ctypes
-        import ctypes
+    import ctypes.util
-        import ctypes.util
+    for lib_name in ['gobject-2.0', 'pango-1.0', 'cairo', 'harfbuzz', 'fontconfig']:
-        for lib in ['gobject-2.0', 'pango-1.0', 'cairo', 'harfbuzz', 'fontconfig']:
+        try:
-            path = ctypes.util.find_library(lib)
+            path = ctypes.util.find_library(lib_name)
             if path:
-                try:
+                ctypes.CDLL(path)
-                    ctypes.CDLL(path)
+        except Exception:
-                except OSError:
+            pass
-                    pass
-    except Exception:
-        pass
 
     try:
         from django.core.management import execute_from_command_line

staticfiles/@popperjs/core/LICENSE.md

@@ -1,20 +0,0 @@
-The MIT License (MIT)
-
-Copyright (c) 2019 Federico Zivolo
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of
-this software and associated documentation files (the "Software"), to deal in
-the Software without restriction, including without limitation the rights to
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
-the Software, and to permit persons to whom the Software is furnished to do so,
-subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
-FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
-COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
-IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
-CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

staticfiles/@popperjs/core/README.md

@@ -1,376 +0,0 @@
-<!-- <HEADER> // IGNORE IT -->
-<p align="center">
-  <img src="https://rawcdn.githack.com/popperjs/popper-core/8805a5d7599e14619c9e7ac19a3713285d8e5d7f/docs/src/images/popper-logo-outlined.svg" alt="Popper" height="300px"/>
-</p>
-
-<div align="center">
-  <h1>Tooltip & Popover Positioning Engine</h1>
-</div>
-
-<p align="center">
-  <a href="https://www.npmjs.com/package/@popperjs/core">
-    <img src="https://img.shields.io/npm/v/@popperjs/core?style=for-the-badge" alt="npm version" />
-  </a>
-  <a href="https://www.npmjs.com/package/@popperjs/core">
-    <img src="https://img.shields.io/endpoint?style=for-the-badge&url=https://runkit.io/fezvrasta/combined-npm-downloads/1.0.0?packages=popper.js,@popperjs/core" alt="npm downloads per month (popper.js + @popperjs/core)" />
-  </a>
-  <a href="https://rollingversions.com/popperjs/popper-core">
-    <img src="https://img.shields.io/badge/Rolling%20Versions-Enabled-brightgreen?style=for-the-badge" alt="Rolling Versions" />
-  </a>
-</p>
-
-<br />
-<!-- </HEADER> // NOW BEGINS THE README -->
-
-**Positioning tooltips and popovers is difficult. Popper is here to help!**
-
-Given an element, such as a button, and a tooltip element describing it, Popper
-will automatically put the tooltip in the right place near the button.
-
-It will position _any_ UI element that "pops out" from the flow of your document
-and floats near a target element. The most common example is a tooltip, but it
-also includes popovers, drop-downs, and more. All of these can be generically
-described as a "popper" element.
-
-## Demo
-
-[![Popper visualized](https://i.imgur.com/F7qWsmV.jpg)](https://popper.js.org)
-
-## Docs
-
-- [v2.x (latest)](https://popper.js.org/docs/v2/)
-- [v1.x](https://popper.js.org/docs/v1/)
-
-We've created a
-[Migration Guide](https://popper.js.org/docs/v2/migration-guide/) to help you
-migrate from Popper 1 to Popper 2.
-
-To contribute to the Popper website and documentation, please visit the
-[dedicated repository](https://github.com/popperjs/website).
-
-## Why not use pure CSS?
-
-- **Clipping and overflow issues**: Pure CSS poppers will not be prevented from
-  overflowing clipping boundaries, such as the viewport. It will get partially
-  cut off or overflows if it's near the edge since there is no dynamic
-  positioning logic. When using Popper, your popper will always be positioned in
-  the right place without needing manual adjustments.
-- **No flipping**: CSS poppers will not flip to a different placement to fit
-  better in view if necessary. While you can manually adjust for the main axis
-  overflow, this feature cannot be achieved via CSS alone. Popper automatically
-  flips the tooltip to make it fit in view as best as possible for the user.
-- **No virtual positioning**: CSS poppers cannot follow the mouse cursor or be
-  used as a context menu. Popper allows you to position your tooltip relative to
-  any coordinates you desire.
-- **Slower development cycle**: When pure CSS is used to position popper
-  elements, the lack of dynamic positioning means they must be carefully placed
-  to consider overflow on all screen sizes. In reusable component libraries,
-  this means a developer can't just add the component anywhere on the page,
-  because these issues need to be considered and adjusted for every time. With
-  Popper, you can place your elements anywhere and they will be positioned
-  correctly, without needing to consider different screen sizes, layouts, etc.
-  This massively speeds up development time because this work is automatically
-  offloaded to Popper.
-- **Lack of extensibility**: CSS poppers cannot be easily extended to fit any
-  arbitrary use case you may need to adjust for. Popper is built with
-  extensibility in mind.
-
-## Why Popper?
-
-With the CSS drawbacks out of the way, we now move on to Popper in the
-JavaScript space itself.
-
-Naive JavaScript tooltip implementations usually have the following problems:
-
-- **Scrolling containers**: They don't ensure the tooltip stays with the
-  reference element while scrolling when inside any number of scrolling
-  containers.
-- **DOM context**: They often require the tooltip move outside of its original
-  DOM context because they don't handle `offsetParent` contexts.
-- **Compatibility**: Popper handles an incredible number of edge cases regarding
-  different browsers and environments (mobile viewports, RTL, scrollbars enabled
-  or disabled, etc.). Popper is a popular and well-maintained library, so you
-  can be confident positioning will work for your users on any device.
-- **Configurability**: They often lack advanced configurability to suit any
-  possible use case.
-- **Size**: They are usually relatively large in size, or require an ancient
-  jQuery dependency.
-- **Performance**: They often have runtime performance issues and update the
-  tooltip position too slowly.
-
-**Popper solves all of these key problems in an elegant, performant manner.** It
-is a lightweight ~3 kB library that aims to provide a reliable and extensible
-positioning engine you can use to ensure all your popper elements are positioned
-in the right place.
-
-When you start writing your own popper implementation, you'll quickly run into
-all of the problems mentioned above. These widgets are incredibly common in our
-UIs; we've done the hard work figuring this out so you don't need to spend hours
-fixing and handling numerous edge cases that we already ran into while building
-the library!
-
-Popper is used in popular libraries like Bootstrap, Foundation, Material UI, and
-more. It's likely you've already used popper elements on the web positioned by
-Popper at some point in the past few years.
-
-Since we write UIs using powerful abstraction libraries such as React or Angular
-nowadays, you'll also be glad to know Popper can fully integrate with them and
-be a good citizen together with your other components. Check out `react-popper`
-for the official Popper wrapper for React.
-
-## Installation
-
-### 1. Package Manager
-
-```bash
-# With npm
-npm i @popperjs/core
-
-# With Yarn
-yarn add @popperjs/core
-```
-
-### 2. CDN
-
-```html
-<!-- Development version -->
-<script src="https://unpkg.com/@popperjs/core@2/dist/umd/popper.js"></script>
-
-<!-- Production version -->
-<script src="https://unpkg.com/@popperjs/core@2"></script>
-```
-
-### 3. Direct Download?
-
-Managing dependencies by "directly downloading" them and placing them into your
-source code is not recommended for a variety of reasons, including missing out
-on feat/fix updates easily. Please use a versioning management system like a CDN
-or npm/Yarn.
-
-## Usage
-
-The most straightforward way to get started is to import Popper from the `unpkg`
-CDN, which includes all of its features. You can call the `Popper.createPopper`
-constructor to create new popper instances.
-
-Here is a complete example:
-
-```html
-<!DOCTYPE html>
-<title>Popper example</title>
-
-<style>
-  #tooltip {
-    background-color: #333;
-    color: white;
-    padding: 5px 10px;
-    border-radius: 4px;
-    font-size: 13px;
-  }
-</style>
-
-<button id="button" aria-describedby="tooltip">I'm a button</button>
-<div id="tooltip" role="tooltip">I'm a tooltip</div>
-
-<script src="https://unpkg.com/@popperjs/core@^2.0.0"></script>
-<script>
-  const button = document.querySelector('#button');
-  const tooltip = document.querySelector('#tooltip');
-
-  // Pass the button, the tooltip, and some options, and Popper will do the
-  // magic positioning for you:
-  Popper.createPopper(button, tooltip, {
-    placement: 'right',
-  });
-</script>
-```
-
-Visit the [tutorial](https://popper.js.org/docs/v2/tutorial/) for an example of
-how to build your own tooltip from scratch using Popper.
-
-### Module bundlers
-
-You can import the `createPopper` constructor from the fully-featured file:
-
-```js
-import { createPopper } from '@popperjs/core';
-
-const button = document.querySelector('#button');
-const tooltip = document.querySelector('#tooltip');
-
-// Pass the button, the tooltip, and some options, and Popper will do the
-// magic positioning for you:
-createPopper(button, tooltip, {
-  placement: 'right',
-});
-```
-
-All the modifiers listed in the docs menu will be enabled and "just work", so
-you don't need to think about setting Popper up. The size of Popper including
-all of its features is about 5 kB minzipped, but it may grow a bit in the
-future.
-
-#### Popper Lite (tree-shaking)
-
-If bundle size is important, you'll want to take advantage of tree-shaking. The
-library is built in a modular way to allow to import only the parts you really
-need.
-
-```js
-import { createPopperLite as createPopper } from '@popperjs/core';
-```
-
-The Lite version includes the most necessary modifiers that will compute the
-offsets of the popper, compute and add the positioning styles, and add event
-listeners. This is close in bundle size to pure CSS tooltip libraries, and
-behaves somewhat similarly.
-
-However, this does not include the features that makes Popper truly useful.
-
-The two most useful modifiers not included in Lite are `preventOverflow` and
-`flip`:
-
-```js
-import {
-  createPopperLite as createPopper,
-  preventOverflow,
-  flip,
-} from '@popperjs/core';
-
-const button = document.querySelector('#button');
-const tooltip = document.querySelector('#tooltip');
-
-createPopper(button, tooltip, {
-  modifiers: [preventOverflow, flip],
-});
-```
-
-As you make more poppers, you may be finding yourself needing other modifiers
-provided by the library.
-
-See [tree-shaking](https://popper.js.org/docs/v2/performance/#tree-shaking) for more
-information.
-
-## Distribution targets
-
-Popper is distributed in 3 different versions, in 3 different file formats.
-
-The 3 file formats are:
-
-- `esm` (works with `import` syntax — **recommended**)
-- `umd` (works with `<script>` tags or RequireJS)
-- `cjs` (works with `require()` syntax)
-
-There are two different `esm` builds, one for bundler consumers (e.g. webpack,
-Rollup, etc..), which is located under `/lib`, and one for browsers with native
-support for ES Modules, under `/dist/esm`. The only difference within the two,
-is that the browser-compatible version doesn't make use of
-`process.env.NODE_ENV` to run development checks.
-
-The 3 versions are:
-
-- `popper`: includes all the modifiers (features) in one file (**default**);
-- `popper-lite`: includes only the minimum amount of modifiers to provide the
-  basic functionality;
-- `popper-base`: doesn't include any modifier, you must import them separately;
-
-Below you can find the size of each version, minified and compressed with the
-[Brotli compression algorithm](https://medium.com/groww-engineering/enable-brotli-compression-in-webpack-with-fallback-to-gzip-397a57cf9fc6):
-
-<!-- Don't change the labels to use hyphens, it breaks, even when encoded -->
-
-![](https://badge-size.now.sh/https://unpkg.com/@popperjs/core/dist/umd/popper.min.js?compression=brotli&label=popper)
-![](https://badge-size.now.sh/https://unpkg.com/@popperjs/core/dist/umd/popper-lite.min.js?compression=brotli&label=popper%20lite)
-![](https://badge-size.now.sh/https://unpkg.com/@popperjs/core/dist/umd/popper-base.min.js?compression=brotli&label=popper%20base)
-
-## Hacking the library
-
-If you want to play with the library, implement new features, fix a bug you
-found, or simply experiment with it, this section is for you!
-
-First of all, make sure to have
-[Yarn installed](https://yarnpkg.com/lang/en/docs/install).
-
-Install the development dependencies:
-
-```bash
-yarn install
-```
-
-And run the development environment:
-
-```bash
-yarn dev
-```
-
-Then, simply open one the development server web page:
-
-```bash
-# macOS and Linux
-open localhost:5000
-
-# Windows
-start localhost:5000
-```
-
-From there, you can open any of the examples (`.html` files) to fiddle with
-them.
-
-Now any change you will made to the source code, will be automatically compiled,
-you just need to refresh the page.
-
-If the page is not working properly, try to go in _"Developer Tools >
-Application > Clear storage"_ and click on "_Clear site data_".  
-To run the examples you need a browser with
-[JavaScript modules via script tag support](https://caniuse.com/#feat=es6-module).
-
-## Test Suite
-
-Popper is currently tested with unit tests, and functional tests. Both of them
-are run by Jest.
-
-### Unit Tests
-
-The unit tests use JSDOM to provide a primitive document object API, they are
-used to ensure the utility functions behave as expected in isolation.
-
-### Functional Tests
-
-The functional tests run with Puppeteer, to take advantage of a complete browser
-environment. They are currently running on Chromium, and Firefox.
-
-You can run them with `yarn test:functional`. Set the `PUPPETEER_BROWSER`
-environment variable to `firefox` to run them on the Mozilla browser.
-
-The assertions are written in form of image snapshots, so that it's easy to
-assert for the correct Popper behavior without having to write a lot of offsets
-comparisons manually.
-
-You can mark a `*.test.js` file to run in the Puppeteer environment by
-prepending a `@jest-environment puppeteer` JSDoc comment to the interested file.
-
-Here's an example of a basic functional test:
-
-```js
-/**
- * @jest-environment puppeteer
- * @flow
- */
-import { screenshot } from '../utils/puppeteer.js';
-
-it('should position the popper on the right', async () => {
-  const page = await browser.newPage();
-  await page.goto(`${TEST_URL}/basic.html`);
-
-  expect(await screenshot(page)).toMatchImageSnapshot();
-});
-```
-
-You can find the complete
-[`jest-puppeteer` documentation here](https://github.com/smooth-code/jest-puppeteer#api),
-and the
-[`jest-image-snapshot` documentation here](https://github.com/americanexpress/jest-image-snapshot#%EF%B8%8F-api).
-
-## License
-
-MIT

staticfiles/@popperjs/core/dist/cjs/enums.js

@@ -1,65 +0,0 @@
-/**
- * @popperjs/core v2.11.8 - MIT License
- */
-
-'use strict';
-
-Object.defineProperty(exports, '__esModule', { value: true });
-
-var top = 'top';
-var bottom = 'bottom';
-var right = 'right';
-var left = 'left';
-var auto = 'auto';
-var basePlacements = [top, bottom, right, left];
-var start = 'start';
-var end = 'end';
-var clippingParents = 'clippingParents';
-var viewport = 'viewport';
-var popper = 'popper';
-var reference = 'reference';
-var variationPlacements = /*#__PURE__*/basePlacements.reduce(function (acc, placement) {
-  return acc.concat([placement + "-" + start, placement + "-" + end]);
-}, []);
-var placements = /*#__PURE__*/[].concat(basePlacements, [auto]).reduce(function (acc, placement) {
-  return acc.concat([placement, placement + "-" + start, placement + "-" + end]);
-}, []); // modifiers that need to read the DOM
-
-var beforeRead = 'beforeRead';
-var read = 'read';
-var afterRead = 'afterRead'; // pure-logic modifiers
-
-var beforeMain = 'beforeMain';
-var main = 'main';
-var afterMain = 'afterMain'; // modifier with the purpose to write to the DOM (or write into a framework state)
-
-var beforeWrite = 'beforeWrite';
-var write = 'write';
-var afterWrite = 'afterWrite';
-var modifierPhases = [beforeRead, read, afterRead, beforeMain, main, afterMain, beforeWrite, write, afterWrite];
-
-exports.afterMain = afterMain;
-exports.afterRead = afterRead;
-exports.afterWrite = afterWrite;
-exports.auto = auto;
-exports.basePlacements = basePlacements;
-exports.beforeMain = beforeMain;
-exports.beforeRead = beforeRead;
-exports.beforeWrite = beforeWrite;
-exports.bottom = bottom;
-exports.clippingParents = clippingParents;
-exports.end = end;
-exports.left = left;
-exports.main = main;
-exports.modifierPhases = modifierPhases;
-exports.placements = placements;
-exports.popper = popper;
-exports.read = read;
-exports.reference = reference;
-exports.right = right;
-exports.start = start;
-exports.top = top;
-exports.variationPlacements = variationPlacements;
-exports.viewport = viewport;
-exports.write = write;
-//# sourceMappingURL=enums.js.map

staticfiles/@popperjs/core/dist/cjs/enums.js.flow

@@ -1,3 +0,0 @@
-// @flow
-
-export * from '../../lib/enums.js'

staticfiles/@popperjs/core/dist/cjs/enums.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"enums.js","sources":["../../src/enums.js"],"sourcesContent":["// @flow\nexport const top: 'top' = 'top';\nexport const bottom: 'bottom' = 'bottom';\nexport const right: 'right' = 'right';\nexport const left: 'left' = 'left';\nexport const auto: 'auto' = 'auto';\nexport type BasePlacement =\n  | typeof top\n  | typeof bottom\n  | typeof right\n  | typeof left;\nexport const basePlacements: Array<BasePlacement> = [top, bottom, right, left];\n\nexport const start: 'start' = 'start';\nexport const end: 'end' = 'end';\nexport type Variation = typeof start | typeof end;\n\nexport const clippingParents: 'clippingParents' = 'clippingParents';\nexport const viewport: 'viewport' = 'viewport';\nexport type Boundary = Element | Array<Element> | typeof clippingParents;\nexport type RootBoundary = typeof viewport | 'document';\n\nexport const popper: 'popper' = 'popper';\nexport const reference: 'reference' = 'reference';\nexport type Context = typeof popper | typeof reference;\n\nexport type VariationPlacement =\n  | 'top-start'\n  | 'top-end'\n  | 'bottom-start'\n  | 'bottom-end'\n  | 'right-start'\n  | 'right-end'\n  | 'left-start'\n  | 'left-end';\nexport type AutoPlacement = 'auto' | 'auto-start' | 'auto-end';\nexport type ComputedPlacement = VariationPlacement | BasePlacement;\nexport type Placement = AutoPlacement | BasePlacement | VariationPlacement;\n\nexport const variationPlacements: Array<VariationPlacement> = basePlacements.reduce(\n  (acc: Array<VariationPlacement>, placement: BasePlacement) =>\n    acc.concat([(`${placement}-${start}`: any), (`${placement}-${end}`: any)]),\n  []\n);\nexport const placements: Array<Placement> = [...basePlacements, auto].reduce(\n  (\n    acc: Array<Placement>,\n    placement: BasePlacement | typeof auto\n  ): Array<Placement> =>\n    acc.concat([\n      placement,\n      (`${placement}-${start}`: any),\n      (`${placement}-${end}`: any),\n    ]),\n  []\n);\n\n// modifiers that need to read the DOM\nexport const beforeRead: 'beforeRead' = 'beforeRead';\nexport const read: 'read' = 'read';\nexport const afterRead: 'afterRead' = 'afterRead';\n// pure-logic modifiers\nexport const beforeMain: 'beforeMain' = 'beforeMain';\nexport const main: 'main' = 'main';\nexport const afterMain: 'afterMain' = 'afterMain';\n// modifier with the purpose to write to the DOM (or write into a framework state)\nexport const beforeWrite: 'beforeWrite' = 'beforeWrite';\nexport const write: 'write' = 'write';\nexport const afterWrite: 'afterWrite' = 'afterWrite';\nexport const modifierPhases: Array<ModifierPhases> = [\n  beforeRead,\n  read,\n  afterRead,\n  beforeMain,\n  main,\n  afterMain,\n  beforeWrite,\n  write,\n  afterWrite,\n];\n\nexport type ModifierPhases =\n  | typeof beforeRead\n  | typeof read\n  | typeof afterRead\n  | typeof beforeMain\n  | typeof main\n  | typeof afterMain\n  | typeof beforeWrite\n  | typeof write\n  | typeof afterWrite;\n"],"names":["top","bottom","right","left","auto","basePlacements","start","end","clippingParents","viewport","popper","reference","variationPlacements","reduce","acc","placement","concat","placements","beforeRead","read","afterRead","beforeMain","main","afterMain","beforeWrite","write","afterWrite","modifierPhases"],"mappings":";;;;;;;;IACaA,GAAU,GAAG;IACbC,MAAgB,GAAG;IACnBC,KAAc,GAAG;IACjBC,IAAY,GAAG;IACfC,IAAY,GAAG;IAMfC,cAAoC,GAAG,CAACL,GAAD,EAAMC,MAAN,EAAcC,KAAd,EAAqBC,IAArB;IAEvCG,KAAc,GAAG;IACjBC,GAAU,GAAG;IAGbC,eAAkC,GAAG;IACrCC,QAAoB,GAAG;IAIvBC,MAAgB,GAAG;IACnBC,SAAsB,GAAG;IAgBzBC,mBAA8C,gBAAGP,cAAc,CAACQ,MAAf,CAC5D,UAACC,GAAD,EAAiCC,SAAjC;AAAA,SACED,GAAG,CAACE,MAAJ,CAAW,CAAKD,SAAL,SAAkBT,KAAlB,EAAqCS,SAArC,SAAkDR,GAAlD,CAAX,CADF;AAAA,CAD4D,EAG5D,EAH4D;IAKjDU,UAA4B,gBAAG,UAAIZ,cAAJ,GAAoBD,IAApB,GAA0BS,MAA1B,CAC1C,UACEC,GADF,EAEEC,SAFF;AAAA,SAIED,GAAG,CAACE,MAAJ,CAAW,CACTD,SADS,EAELA,SAFK,SAEQT,KAFR,EAGLS,SAHK,SAGQR,GAHR,CAAX,CAJF;AAAA,CAD0C,EAU1C,EAV0C;;IAc/BW,UAAwB,GAAG;IAC3BC,IAAY,GAAG;IACfC,SAAsB,GAAG;;IAEzBC,UAAwB,GAAG;IAC3BC,IAAY,GAAG;IACfC,SAAsB,GAAG;;IAEzBC,WAA0B,GAAG;IAC7BC,KAAc,GAAG;IACjBC,UAAwB,GAAG;IAC3BC,cAAqC,GAAG,CACnDT,UADmD,EAEnDC,IAFmD,EAGnDC,SAHmD,EAInDC,UAJmD,EAKnDC,IALmD,EAMnDC,SANmD,EAOnDC,WAPmD,EAQnDC,KARmD,EASnDC,UATmD;;;;;;;;;;;;;;;;;;;;;;;;;"}