This commit is contained in:
Rafael Tavares Juliani 2025-09-04 16:07:07 -03:00
commit f269aace6b
4722 changed files with 512564 additions and 0 deletions

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

View File

@ -0,0 +1,4 @@
div.cookie-consent-footer {
font-size: 0.8em;
text-decoration: none;
}

File diff suppressed because one or more lines are too long

1
.quarto/cites/index.json Executable file
View File

@ -0,0 +1 @@
{"agradecimentos.qmd":[],"aplicacoes.qmd":[],"apresentacao.qmd":[],"funcoes-trigonometricas-circulares.qmd":[],"funcoes-trigonometricas-hiperbolicas.qmd":[],"funcoes_trigonometricas_circulares.qmd":[],"funcoes_trigonometricas_hiperbolicas.qmd":[],"igualdades-exponenciais-e-logaritmicas.qmd":[],"igualdades_exponenciais_e_logaritmicas.qmd":[],"index.qmd":[],"indice-remissivo.qmd":[],"indice_remissivo.qmd":[],"referencias.qmd":[],"teste.qmd":[]}

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

1
.quarto/xref/0b8f7ef8 Executable file
View File

@ -0,0 +1 @@
{"entries":[],"headings":["SECTION001000000000000000000"],"options":{"chapter-id":"SECTION001000000000000000000","chapters":true}}

1
.quarto/xref/18ece635 Executable file
View File

@ -0,0 +1 @@
{"entries":[],"headings":["SECTION00710000000000000000","SECTION00720000000000000000","SECTION00730000000000000000","SECTION00740000000000000000","SECTION00750000000000000000","SECTION00760000000000000000"],"options":{"chapters":true}}

1
.quarto/xref/1dcbfd0b Normal file
View File

@ -0,0 +1 @@
{"entries":[],"headings":["SECTION00510000000000000000","SECTION00520000000000000000","SECTION00530000000000000000","SECTION00540000000000000000","SECTION00550000000000000000","SECTION00560000000000000000","SECTION00570000000000000000"],"options":{"chapters":true}}

1
.quarto/xref/460be21c Executable file
View File

@ -0,0 +1 @@
{"entries":[],"headings":["SECTION00610000000000000000","SECTION00620000000000000000","SECTION00630000000000000000","SECTION00640000000000000000","SECTION00650000000000000000","SECTION00660000000000000000","SECTION00670000000000000000","SECTION00680000000000000000","SECTION00600000000000000000"],"options":{"chapter-id":"SECTION00600000000000000000","chapters":true}}

1
.quarto/xref/4fffaab4 Executable file
View File

@ -0,0 +1 @@
{"entries":[],"headings":[],"options":{"chapters":true}}

1
.quarto/xref/5307b9e1 Executable file
View File

@ -0,0 +1 @@
{"entries":[],"headings":["metadados","como-citar","versão-impressa","direitos-autorais"],"options":{"chapters":true}}

1
.quarto/xref/78c64aad Normal file
View File

@ -0,0 +1 @@
{"entries":[],"headings":["SECTION001000000000000000000"],"options":{"chapter-id":"SECTION001000000000000000000","chapters":true}}

1
.quarto/xref/7cb1188c Normal file
View File

@ -0,0 +1 @@
{"entries":[],"headings":["SECTION00610000000000000000","SECTION00620000000000000000","SECTION00630000000000000000","SECTION00640000000000000000","SECTION00650000000000000000","SECTION00660000000000000000","SECTION00670000000000000000","SECTION00680000000000000000","SECTION00600000000000000000"],"options":{"chapter-id":"SECTION00600000000000000000","chapters":true}}

1
.quarto/xref/8174a0ab Executable file
View File

@ -0,0 +1 @@
{"entries":[],"headings":[],"options":{"chapters":true}}

1
.quarto/xref/82bf74d1 Executable file
View File

@ -0,0 +1 @@
{"entries":[],"headings":["SECTION00900000000000000000"],"options":{"chapter-id":"SECTION00900000000000000000","chapters":true}}

44
.quarto/xref/INDEX Executable file
View File

@ -0,0 +1,44 @@
{
"index.qmd": {
"index.html": "5307b9e1"
},
"apresentacao.qmd": {
"apresentacao.html": "8174a0ab"
},
"agradecimentos.qmd": {
"agradecimentos.html": "4fffaab4"
},
"funcoes-trigonometricas-circulares.qmd": {
"funcoes-trigonometricas-circulares.html": "d905b7b4"
},
"igualdades-exponenciais-e-logaritmicas.qmd": {
"igualdades-exponenciais-e-logaritmicas.html": "18ece635"
},
"teste.qmd": {
"teste.html": "b93f9b0b"
},
"funcoes-trigonometricas-hiperbolicas.qmd": {
"funcoes-trigonometricas-hiperbolicas.html": "460be21c"
},
"aplicacoes.qmd": {
"aplicacoes.html": "b3847cd7"
},
"referencias.qmd": {
"referencias.html": "82bf74d1"
},
"indice-remissivo.qmd": {
"indice-remissivo.html": "0b8f7ef8"
},
"funcoes_trigonometricas_circulares.qmd": {
"funcoes_trigonometricas_circulares.html": "1dcbfd0b"
},
"funcoes_trigonometricas_hiperbolicas.qmd": {
"funcoes_trigonometricas_hiperbolicas.html": "7cb1188c"
},
"igualdades_exponenciais_e_logaritmicas.qmd": {
"igualdades_exponenciais_e_logaritmicas.html": "c0777df9"
},
"indice_remissivo.qmd": {
"indice_remissivo.html": "78c64aad"
}
}

1
.quarto/xref/b3847cd7 Executable file
View File

@ -0,0 +1 @@
{"entries":[],"headings":["SECTION00810000000000000000","SECTION00820000000000000000","SECTION00830000000000000000","SECTION00840000000000000000","SECTION00850000000000000000","SECTION00860000000000000000","SECTION00870000000000000000","SECTION00800000000000000000"],"options":{"chapter-id":"SECTION00800000000000000000","chapters":true}}

1
.quarto/xref/b93f9b0b Executable file
View File

@ -0,0 +1 @@
{"entries":[],"options":{"chapters":true},"headings":[]}

1
.quarto/xref/c0777df9 Normal file
View File

@ -0,0 +1 @@
{"entries":[],"headings":["SECTION00710000000000000000","SECTION00720000000000000000","SECTION00730000000000000000","SECTION00740000000000000000","SECTION00750000000000000000","SECTION00760000000000000000"],"options":{"chapters":true}}

1
.quarto/xref/d905b7b4 Executable file
View File

@ -0,0 +1 @@
{"entries":[],"headings":["SECTION00510000000000000000","SECTION00520000000000000000","SECTION00530000000000000000","SECTION00540000000000000000","SECTION00550000000000000000","SECTION00560000000000000000","SECTION00570000000000000000"],"options":{"chapters":true}}

12
README.md Normal file
View File

@ -0,0 +1,12 @@
# Sobre
Repositório do livro online "As funções trigonométricas circulares e hiperbólicas".
# Direitos autorais
© Sandro Marcos Guzzo e a Editora Moan, 2021.
# Licença
Todos os direitos reservados. A reprodução, cópia ou distribuição desta obra, seja em parte ou no todo, só poderá ser realizada mediante autorização, sob pena de violação da [lei de direitos autorais. (Lei 9.610/98)](https://www.planalto.gov.br/ccivil_03/leis/l9610.htm)

View File

@ -0,0 +1,17 @@
title: Moan-livro
author: Rafael Tavares Juliani
version: 1.0.0
quarto-required: ">=1.4.0"
lang: pt-BR
contributes:
formats:
html:
mainfont: Source Sans Pro
lang: pt-BR
citation: true
google-scholar: true
smooth-scroll: true
theme:
light: [cosmo, custom.scss]
dark: [superhero, custom.scss]

View File

@ -0,0 +1,154 @@
/*-- scss:defaults --*/
/* TODO: Customize html appearance by setting SCSS variables */
/* See https://quarto.org/docs/output-formats/html-themes.html#theme-options */
/*-- scss:rules --*/
/* TODO: Provide custom CSS rules */
/*-- scss:defaults --*/
$h2-font-size: 1.6rem !default;
$headings-font-weight: 500 !default;
$font-size-base: 1.1rem !default;
/*-- scss:rules --*/
main p, main li {
text-align: left;
hyphens: auto;
-webkit-hyphens: auto;
font-kerning: auto;
}
.verso, .exemplo
{
display: block;
margin: 15px auto;
width: 300px;
}
#como-citar-bibtex, #como-citar-atribuicao {
border: 1px solid #dedede;
border-radius: 2px;
padding: 10px;
margin-bottom: 1rem;
}
#como-citar-atribuicao p {
text-indent: -20px;
margin-left: 20px;
}
#como-citar p {
margin-bottom: 5px;
}
.verso {
text-indent: -15px;
}
main li {
margin-bottom: 15px;
}
h1{
margin-bottom: 18px !important;
text-align: center;
}
h2#toc-title {
box-shadow:none;
}
h1, h2 {
margin-top: 50px;
}
#TOC .small_h2{
font-size: inherit;
}
#TOC a {
word-break: normal;
}
.subtitle {
text-align: center;
}
div.autores{
margin-bottom: 30px;
margin-top: -15px;
font-size: 0.8em;
}
div.autores p {
text-align: right;
}
#direitos-autorais p {
text-align: center;
}
blockquote{
text-align: left;
hyphens: auto;
font-kerning: auto;
margin-top: 30px;
}
blockquote+p span div {
text-align: left;
font-weight: normal;
font-size: unset;
}
.references div{
text-indent: -20px;
margin-left: 20px;
text-align: justify;
}
.citation div {
text-align: justify;
}
.figure-caption {
text-align: center;
}
.contador-figura{
font-weight: bold;
font-variant: small-caps;
}
mjx-container {
overflow-x: auto;
overflow-y: hidden;
}
@media (max-width: 991.98px){
body .page-columns, body.fullcontent:not(.floating):not(.docked) .page-columns, body.slimcontent:not(.floating):not(.docked) .page-columns, body.docked .page-columns, body.docked.slimcontent .page-columns, body.docked.fullcontent .page-columns, body.floating .page-columns, body.floating.slimcontent .page-columns, body.floating.fullcontent .page-columns {
display: grid;
gap: 0;
grid-template-columns: [screen-start] 1.5em [screen-start-inset page-start page-start-inset body-start-outset body-start body-content-start] minmax(0px, 1fr) [body-content-end body-end body-end-outset page-end-inset page-end screen-end-inset] 1.5em [screen-end];
}
#quarto-margin-sidebar {
display: none;
}
#quarto-content {
max-width: 768px;
margin: auto;
}
}

View File

@ -0,0 +1,242 @@
import os
import yaml
from bs4 import BeautifulSoup
import json
import copy
import shutil
# Caminho para o arquivo _quarto.yml
quarto_config_file = "_quarto.yml"
with open(quarto_config_file) as f:
quarto_config = yaml.safe_load(f)
# Extrair as informações do arquivo _quarto.yml
# funcao para iterar os capítulos
def extrair_arquivos_qmd(objeto, capitulos_arquivos_html):
if isinstance(objeto, list):
for elemento in objeto:
extrair_arquivos_qmd(elemento, capitulos_arquivos_html)
elif isinstance(objeto, dict):
if 'part' in objeto:
extrair_arquivos_qmd(objeto['part'], capitulos_arquivos_html)
if 'chapters' in objeto:
extrair_arquivos_qmd(objeto['chapters'], capitulos_arquivos_html)
elif isinstance(objeto, str) and objeto.endswith('.qmd'):
capitulos_arquivos_html.append(objeto[:-4])
# pegando o local dos arquivos html
pasta_livro_renderizado = quarto_config["project"]["output-dir"]
# pegando o campo controle-moan para verificar se é um dicionário
é_dicionário = quarto_config["controle-moan"]["dicionario"]
# pegando os capítulos
capitulos = quarto_config["book"]["chapters"]
capitulos_arquivo_html = []
extrair_arquivos_qmd(capitulos, capitulos_arquivo_html)
# altera os arquivos html
for index, output_file in enumerate(capitulos_arquivo_html):
# Caminho completo para o arquivo HTML
arquivo_html = os.path.join(pasta_livro_renderizado, output_file + ".html")
# conta os elementos que serão uma referencia / Ele começa em 0 na abertura de um novo capítulo
ref_num = 0
# Abre o arquivo HTML
with open(arquivo_html, "r", encoding="utf-8") as f:
content = f.read()
# Cria um objeto BeautifulSoup
soup = BeautifulSoup(content, "html.parser")
# Encontre a tag 'main' no documento
main_tag = soup.find("main")
# Crie o elemento script com os metadados
script_tag = soup.new_tag('script', data="moan-metadados")
#pegar apenas a url do livro
url_livro = os.path.basename(pasta_livro_renderizado)
script_tag.string = f'var metadados = {{livroUrl: "{url_livro}"}};'
script_tag.string += f'var modelo_antigo = true;'
# Adicione o script ao cabeçalho (head) do HTML
soup.head.append(script_tag)
# Se existir o ark, colocar os dados nas tags object do primeiro capítulo do livro
if "ark" in quarto_config["moan-dados"] and index == 0:
ark = quarto_config["moan-dados"]["ark"]
# Substitua "." por "_p_" e "/" por "_b_" em 'ark'
ark = ark.replace(".", "_p_").replace("/", "_b_")
# Adicione "ark_dp_" ao início de 'ark'
ark = "ark_dp_" + ark
# Encontre as tags object com id "metadados_livro_yml" e "metadados_livro_json"
obj_metadados_yml = main_tag.find("object", {"id": "metadados_livro_yml"})
obj_metadados_json = main_tag.find("object", {"id": "metadados_livro_json"})
if obj_metadados_yml and obj_metadados_json:
# Defina o atributo "data" das tags object
obj_metadados_yml["data"] = "https://ark.livro.online/yaml/" + ark + ".yml"
obj_metadados_json["data"] = "https://ark.livro.online/json/" + ark + ".json"
# Verifique se o arquivo "postos-de-venda.json" existe
json_file_path = "postos-de-venda.json"
if os.path.exists(json_file_path) and index == 0:
# O arquivo JSON existe, abra-o e extraia as chaves e valores
with open(json_file_path, "r", encoding="utf-8") as json_file:
postos_de_venda = json.load(json_file)
# Crie uma nova lista não ordenada para armazenar os links
ul = soup.new_tag("ul", id="postos-de-venda")
for key, value in postos_de_venda.items():
li = soup.new_tag("li")
# Verifica se "@" está presente no valor
if "@" in value:
# Se "@" estiver presente, crie um link de e-mail (mailto)
link = soup.new_tag("a", href=f"mailto:{value}")
link.string = f"{key}: {value}" # Texto do link é a chave seguida de dois pontos e o valor
else:
# Se "@" não estiver presente, crie um link normal
link = soup.new_tag("a", href=value)
link.string = key # Texto do link é a chave
li.append(link)
ul.append(li)
# Encontre a tag "section" com ID "versão-impressa"
section_versao_impressa = main_tag.find("section", id="versão-impressa")
if section_versao_impressa:
# Adicione a lista não ordenada de links à seção "versão-impressa"
section_versao_impressa.append(ul)
# Copie o arquivo JSON para a pasta especificada em "pasta_livro_renderizado"
dest_file = os.path.join(pasta_livro_renderizado, "postos-de-venda.json")
shutil.copy(json_file_path, dest_file)
# Copiar a imagem og.jpg que está na pasta img e serve para usar no open graph
# Pasta onde o arquivo og.jpg está localizado
pasta_img = "img"
# Caminho completo para o arquivo og.jpg
caminho_original = os.path.join(pasta_img, "og.jpg")
# Verifica se o arquivo og.jpg existe na pasta img
if os.path.exists(caminho_original):
# Caminho completo para a pasta de destino na pasta livro_renderizado
caminho_destino = os.path.join(pasta_livro_renderizado, "img")
# Certifica-se de que a pasta de destino exista
os.makedirs(caminho_destino, exist_ok=True)
# Copia o arquivo og.jpg para a pasta de destino
shutil.copy(caminho_original, caminho_destino)
print("Arquivo og.jpg foi copiado com sucesso.")
else:
print("O arquivo og.jpg não foi encontrado na pasta img.")
# Coloca o conteudo dentro de uma div com id chamado de papel, substituindo o conteudo original da tag main pela div papel
# Crie uma div com id "papel"
div_papel = soup.new_tag('div', id='papel')
# Copie a tag main
main_content_copy = copy.copy(main_tag.contents)
# Limpe o conteúdo da tag <main>
main_tag.clear()
# Adicione a cópia do conteúdo à div "papel"
for item_copy in main_content_copy:
div_papel.append(item_copy)
# Acrescentar a div_papel na tag main
main_tag.append(div_papel)
# Salva o arquivo HTML modificado
with open(arquivo_html, "w", encoding="utf-8") as f:
f.write(str(soup))
# Nos livros antigos que já possuía referencias, o arquivo com as referencias será copiado para a pasta do livro renderizado.
origem = "ref_capitulos.json"
destino = os.path.join(pasta_livro_renderizado, "ref_capitulos.json")
# Copia o arquivo para a pasta de destino
shutil.copy(origem, destino)

View File

@ -0,0 +1,744 @@
<?xml version="1.0" encoding="utf-8"?>
<style xmlns="http://purl.org/net/xbiblio/csl" version="1.0" class="in-text" initialize="false" demote-non-dropping-particle="never" default-locale="pt-BR">
<info>
<!-- ESTE ESTILO FOI CONSTRUÍDO A PARTIR DO MODELO DA ABNT (com diversos ajustes, mas os créditos permanecem aos autores originais) -->
<title>Universidade Estadual de Alagoas - UNEAL [ABNT] (Portuguese - Brazil)</title>
<title-short>UNEAL-ABNT</title-short>
<id>http://www.zotero.org/styles/universidade-estadual-de-alagoas-abnt</id>
<link href="http://www.zotero.org/styles/universidade-estadual-de-alagoas-abnt" rel="self"/>
<link href="http://www.zotero.org/styles/associacao-brasileira-de-normas-tecnicas" rel="template"/>
<link href="https://www.abntcatalogo.com.br/norma.aspx?ID=408006" rel="documentation"/>
<author>
<name>Wellyngton Chaves Monteiro da Silva</name>
<email>wellyngton@uneal.edu.br</email>
<uri>http://www.uneal.edu.br</uri>
</author>
<category citation-format="author-date"/>
<category field="generic-base"/>
<summary>De acordo com ABNT-NBR 10520.2002 e ABNT-NBR 6023.2018</summary>
<updated>2022-06-26T01:48:46+00:00</updated>
<rights license="http://creativecommons.org/licenses/by-sa/3.0/">This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 License</rights>
</info>
<locale xml:lang="pt-BR">
<!--
UTILITÁRIOS (para serem inseridos no campo EXTRA do Zotero):
publisher-place: quando não existir espaço para LUGAR da publicação (ex.: publisher-place: Maceió OU QUANDO NECESSÁRIO, publisher-place: Maceió, AL)
-->
<terms>
<!--Abreviações dos meses do ano -->
<term name="month-01" form="short">jan.</term>
<term name="month-02" form="short">fev.</term>
<term name="month-03" form="short">mar.</term>
<term name="month-04" form="short">abr.</term>
<term name="month-05" form="short">maio</term>
<term name="month-06" form="short">jun.</term>
<term name="month-07" form="short">jul.</term>
<term name="month-08" form="short">ago.</term>
<term name="month-09" form="short">set.</term>
<term name="month-10" form="short">out.</term>
<term name="month-11" form="short">nov.</term>
<term name="month-12" form="short">dez.</term>
<!--Os termos abaixo serao utilizados quando houverem nomes de editores. Apos a citacao dos nomes, eles irao aparecer entre parenteses.-->
<term name="and">e</term>
<term name="editor" form="short">
<single>ed</single>
<multiple>eds</multiple>
</term>
<term name="editor" form="short">
<single>org</single>
<multiple>org</multiple>
</term>
<term name="container-author" form="short">
<single>ed</single>
<multiple>eds</multiple>
</term>
<term name="collection-editor" form="short">
<single>org</single>
<multiple>org</multiple>
</term>
</terms>
</locale>
<!--A macro 'container-contributor' mostra os nomes dos editores, SOBRENOME, INICIAIS PRENOMES, sendo as inicias separadas por ponto -->
<macro name="container-contributors">
<choose>
<if type="chapter">
<names variable="container-author" delimiter=", ">
<name name-as-sort-order="all" sort-separator=", " initialize-with=". " delimiter="; " delimiter-precedes-last="always">
<name-part name="family" text-case="uppercase"/>
<name-part name="given" text-case="capitalize-first"/>
</name>
<label form="short" prefix=" (" suffix=".)"/>
<substitute>
<names variable="editor"/>
<names variable="collection-editor"/>
</substitute>
</names>
</if>
</choose>
</macro>
<!--A macro 'secondary-contributors' mostra os nomes dos organizadores, SOBRENOME, INICIAIS PRENOMES, sendo as inicias separadas por ponto -->
<macro name="secondary-contributors">
<choose>
<if type="chapter" match="none">
<names variable="editor" delimiter="; " prefix=" (" suffix=")">
<name initialize-with=". " delimiter=", "/>
<label form="short" prefix=", " text-case="capitalize-first" suffix="."/>
</names>
</if>
</choose>
</macro>
<!--A macro 'translator' mostra os nomes dos tradutores, conforme a NBR 6023, de 2018 -->
<macro name="translator">
<text value="Tradução "/>
<names variable="translator" delimiter=", ">
<name delimiter=", " sort-separator=" " delimiter-precedes-last="always">
<name-part name="given"/>
<name-part name="family" text-case="capitalize-first"/>
</name>
<et-al font-style="normal"/>
</names>
</macro>
<!--A macro 'author' mostra os nomes dos autores na bibliografia, SOBRENOME, INICIAIS PRENOMES, sendo as iniciais
separadas por ponto. Quando houver mais de três autores, somente o primeiro será exibido e no lugar dos outros
aparecera a expessão 'et al.'. Na regra da ABNT essa expressão deve aparecer em fonte normal -->
<macro name="author">
<names variable="author">
<name name-as-sort-order="all" sort-separator=", " initialize-with=". " delimiter="; " delimiter-precedes-last="always">
<name-part name="family" text-case="uppercase"/>
<name-part name="given" text-case="capitalize-first"/>
</name>
<label form="short" prefix=" (" suffix=".)" text-case="uppercase"/>
<substitute>
<names variable="editor"/>
<text macro="title"/>
</substitute>
</names>
</macro>
<!--A macro 'author-short' mostra os nomes dos autores na citação (no meio do texto). Nela aparecera apenas o último nome
do autor. Na regra da ABNT o sobrenome deve aparecer com todas as letras em caixa alta -->
<macro name="author-short">
<names variable="author">
<name form="short" name-as-sort-order="all" sort-separator=", " initialize-with=". " delimiter="; " delimiter-precedes-last="never">
<name-part name="family" text-case="uppercase"/>
<name-part name="given" text-case="uppercase"/>
</name>
<substitute>
<names variable="editor"/>
<choose>
<if type="book">
<text variable="title" form="short"/>
</if>
<else>
<text variable="title" form="short" text-case="uppercase" quotes="false"/>
</else>
</choose>
</substitute>
</names>
</macro>
<macro name="director">
<names variable="author">
<name sort-separator=", " initialize-with=". " delimiter="; " delimiter-precedes-last="always">
<name-part name="given" text-case="capitalize-first"/>
<name-part name="family" text-case="capitalize-first"/>
</name>
</names>
</macro>
<!--A macro 'access' é utilizada em arquivos de páginas da web. Ela é responsável por exibir a URL do site pesquisado e a data do acesso, além do DOI -->
<macro name="access">
<text variable="ISSN" prefix=" ISSN: " suffix="."/>
<text variable="ISBN" prefix=" ISBN: " suffix="."/>
<text variable="DOI" prefix=" DOI: " suffix="."/>
<!-- <text variable="URL" prefix=" Disponível em: &lt;" suffix="&gt;."/> RETIREI AS ENTRADAS DAS URLs, CONFORME ABNT -->
<text variable="URL" prefix=" Disponível em: " suffix="."/>
<date variable="accessed" prefix=". Acesso em: " suffix=".">
<date-part name="day" suffix=" "/>
<date-part name="month" form="short" suffix=". " text-case="lowercase"/>
<date-part name="year"/>
</date>
</macro>
<!--A macro 'title' mostra o título principal do arquivo. Em todos os tipos ele aparecerá em negrito logo após os nomes dos autores,
exceto em arquivos do tipo 'artigo de jornal, artigo de revista, artigo de periódico', nesses arquivos eles irão aparecer em fonte normal -->
<macro name="title">
<choose>
<if type="chapter article-newspaper legislation article-magazine article-journal bill entry-encyclopedia paper-conference" match="any">
<text variable="title"/>
</if>
<else-if type="book thesis patent report" match="any">
<text variable="title" font-weight="bold"/>
</else-if>
<else-if type="dataset" match="any">
<text variable="title" suffix=". "/>
</else-if>
<else-if type="broadcast motion_picture" match="any">
<text variable="title" text-case="uppercase"/>
</else-if>
<else>
<text variable="title" font-weight="bold"/>
</else>
</choose>
<text value=""/>
</macro>
<!-- Titulo dos Anais-->
<macro name="container-title">
<choose>
<if type="paper-conference" match="any">
<text variable="container-title" text-case="uppercase"/>
<text variable="number" prefix=", " suffix=", "/>
<text macro="issued-year" prefix=" " suffix=", "/>
<text variable="publisher-place" suffix=". "/>
<text value="Anais" font-weight="bold"/>
<text value=" [...]. "/>
</if>
<else>
<text variable="container-title" font-weight="bold"/>
</else>
</choose>
</macro>
<!--A macro 'publisher' mostra o nome da editora responsável pela publicação-->
<macro name="publisher">
<choose>
<if match="any" variable="publisher-place publisher">
<choose>
<if variable="publisher-place">
<text variable="publisher-place"/>
</if>
<else-if type="entry-encyclopedia thesis" match="any"/>
<else-if type="paper-conference" match="any">
<text variable="publisher-place" suffix=". "/>
</else-if>
<else>
<text value="[s.l.] "/>
</else>
</choose>
<choose>
<if variable="publisher">
<text variable="publisher" prefix=": " suffix=","/>
<text macro="issued"/>
</if>
</choose>
</if>
<else>
<text value="[s.l.: s.n.]"/>
</else>
</choose>
</macro>
<!--A macro 'event' sera utilizada em arquivos do tipo Evento/Conferencia. Ela e responsavel por mostrar o nome da conferencia, que tera formatacao
em caixa alta. Utiliza-se antes do nome da conferencia a expressao "In". Segundo a regra da ABNT ela deve ser em fonte normal-->
<macro name="event">
<choose>
<if variable="event">
<choose>
<if variable="genre" match="none">
<text term="in" font-style="italic" text-case="capitalize-first" suffix=": "/>
<text variable="event" text-case="uppercase"/>
</if>
<else>
<group delimiter=" ">
<text variable="genre" text-case="capitalize-first"/>
<text term="presented at"/>
<text variable="event"/>
</group>
</else>
</choose>
</if>
<else-if type="paper-conference" match="any"/>
</choose>
</macro>
<!--A macro 'issued' e utilizada quando devemos mostrar a data completa exemplo: 03 mar. 2011.-->
<macro name="issued">
<choose>
<if variable="issued" match="any">
<group>
<date variable="issued">
<date-part name="year" prefix=" " suffix=""/>
<!-- RETIREI O PONTO DO suffix PARA FICAR 2017a, 2017b, COM PONTO FICA 2017. a., 2017. b. -->
</date>
</group>
</if>
<else-if type="patent" match="any">
<date form="numeric" variable="issued" suffix="."/>
</else-if>
<else>
<text value="[s.d.]"/>
</else>
</choose>
</macro>
<!--A macro 'issued-year' e utilizada quando desejamos que apareca apenas o ano-->
<macro name="issued-year">
<choose>
<if variable="issued" match="any">
<date variable="issued">
<date-part name="year"/>
</date>
</if>
<else-if type="paper-conference" match="all">
<date date-parts="year" form="numeric" variable="issued">
<date-part name="year"/>
</date>
</else-if>
<else>
<text value="[s.d.]"/>
</else>
</choose>
</macro>
<macro name="issued-legislation">
<date variable="issued">
<date-part name="day" suffix=" "/>
<date-part name="month" form="short" suffix=". " text-case="lowercase"/>
<date-part name="year"/>
</date>
</macro>
<!--A macro 'edition' e responsavel por mostrar o numero da edicao.-->
<macro name="edition">
<choose>
<!--Se for capitulo de livro aparecera somente o numero-->
<if type="book chapter" match="any">
<choose>
<if is-numeric="edition">
<group delimiter=" ">
<number variable="edition" form="numeric" suffix="."/>
<text term="edition" form="short" suffix="."/>
</group>
</if>
<else>
<!--Se for outro tipo de documento aparecera o numero e depois a descricao "ed."-->
<text variable="edition" suffix=" ed."/>
</else>
</choose>
</if>
</choose>
</macro>
<!--A macro 'locators' tem como funcao mostrar os dados complementares do arquivo (paginas, secao, volume, etc)-->
<macro name="locators">
<choose>
<!--Se for projeto de lei mostrara o dia, mes "forma curta", ano, secao "Sec." e pagina "p."-->
<if type="bill">
<group prefix=". " delimiter=", ">
<date variable="issued">
<date-part name="day"/>
<date-part prefix=" " name="month" form="short"/>
<date-part prefix=" " name="year"/>
</date>
<text macro="section"/>
<text variable="page" prefix="p. " suffix="."/>
</group>
</if>
<!--Se for artigos de jornal, revista, etc. Aparecera o volume "v.", edicao "n." e a pagina do artigo "p."-->
<else-if match="any" type="article-journal article-magazine article-newspaper">
<group delimiter=", ">
<group delimiter=", ">
<text variable="volume" prefix="v. "/>
<text variable="issue" prefix="n. "/>
</group>
<text variable="collection-title"/>
<text variable="page" prefix="p. "/>
</group>
</else-if>
<!-- Capítulo de livro -->
<!--Se for capitulo de livro aparecera o volume "v." e a pagina "p."-->
<else-if match="any" type="book chapter">
<group delimiter=", ">
<group>
<text variable="volume" prefix="v. " suffix=". "/>
<text variable="page" prefix="p. "/>
<!--Inseri este campo 'extra' caso queira colocar alguma observacao, como 'nome da coleção', 'nome da série' etc. -->
<!-- <text variable="note" prefix=". " suffix=""/> -->
<text macro="collection-title" prefix=". (" suffix=")."/>
<!-- AQUI INSERE A COLEÇÃO OU SÉRIE DA OBRA -->
</group>
</group>
</else-if>
</choose>
</macro>
<macro name="collection-title">
<text variable="collection-title"/>
<text variable="collection-number" prefix=" "/>
</macro>
<macro name="genre">
<text variable="genre"/>
</macro>
<macro name="section">
<choose>
<if match="any" variable="section issue">
<text variable="section"/>
<text variable="issue"/>
</if>
</choose>
</macro>
<macro name="citation-locator">
<group>
<label variable="locator" form="short"/>
<text variable="locator" prefix=" "/>
</group>
</macro>
<macro name="place">
<choose>
<if variable="publisher-place" match="any">
<text variable="publisher-place" suffix=", "/>
</if>
<else-if type="paper-conference" variable="publisher-place">
<text variable="publisher-place" suffix=". "/>
</else-if>
<else>
<text value="[S. l.]" font-style="italic" suffix=", "/>
</else>
</choose>
</macro>
<macro name="archive">
<group>
<text variable="archive" prefix=" "/>
</group>
</macro>
<!--Citacao-->
<!--et al. aparece a partir de 04 autores-->
<citation et-al-min="4" et-al-use-first="1" collapse="year" disambiguate-add-year-suffix="true">
<sort>
<!--Puxa o autor primeiro-->
<key macro="author"/>
<!--Depois o ano-->
<key variable="issued"/>
</sort>
<layout prefix="(" suffix=")" delimiter="; ">
<group>
<text suffix=", " macro="author-short"/>
<text macro="issued-year"/>
<text prefix=", " macro="citation-locator"/>
</group>
</layout>
</citation>
<bibliography hanging-indent="false" et-al-min="10" et-al-use-first="1" entry-spacing="1">
<sort>
<key macro="author"/>
<key variable="issued"/>
</sort>
<layout>
<choose>
<!--Projeto de lei-->
<if type="bill">
<group>
<!--autor-->
<text macro="author" suffix=". "/>
<!--Numero da lei-->
<text variable="number" suffix=". "/>
<!--Titulo-->
<text macro="title" suffix=". "/>
<!--Historico em negrito-->
<text variable="references" font-weight="bold" suffix=". "/>
<!-- ESTE PONTO VEM ANTES DO 'EXTRA' COMO LOCAL NAS LEIS -->
<!--Campo 'extra' caso queira colocar alguma observacao-->
<text variable="note"/>
<!--Dados complementares "secao, pagina"-->
<text macro="locators" suffix=". "/>
</group>
</if>
<!--Mapa-->
<else-if type="map">
<group>
<!--autor-->
<text macro="author" suffix=". "/>
<!--Titulo-->
<text macro="title" suffix=", "/>
<!--data-->
<text macro="issued" suffix=". "/>
<!--Campo 'extra' caso queira colocar alguma observacao-->
<text variable="note" suffix=". "/>
</group>
</else-if>
<!--Livro-->
<else-if type="book">
<group>
<!--autor-->
<text macro="author" suffix=". "/>
<!--Titulo-->
<text macro="title" suffix=". "/>
<!--Traducao INSERI DA ABNT (ver como funciona)-->
<text macro="translator" suffix=". "/>
<!--Edicao-->
<text macro="edition" suffix="., "/>
<!-- ADICIONEI A VÍRGULA PARA SEPARAR A EDIÇÃO DO LOCAL DE PUBLICAÇÃO -->
<!--Local, data, etc-->
<text macro="publisher" suffix=". "/>
<text variable="number-of-pages" suffix=" p. "/>
<!-- ADICIONA A QUANTIDADE DE PÁGINAS NA OBRA -->
<!-- Inseri este campo 'extra' caso queira colocar alguma observacao -->
<text variable="note" suffix=". "/>
<text macro="collection-title" prefix="(" suffix=")."/>
<!-- AQUI INSERE A COLEÇÃO OU SÉRIE DA OBRA -->
<!--Dados complementares "pagina, volume"-->
<!--<text macro="locators"/>-->
<!-- REMOVIDO PARA EVITAR DUPLICIDADE DE INFORMAÇÃO SOBRE A SÉRIE OU COLEÇÃO DA OBRA -->
<text macro="access"/>
</group>
</else-if>
<!--Conferencia-->
<else-if type="chapter">
<group>
<!--autor-->
<text macro="author" suffix=". "/>
<!--Titulo-->
<text macro="title" suffix=". "/>
<!--INSERI DA ABNT (ver como funciona) -->
<text macro="secondary-contributors" suffix=". "/>
<!--In:-->
<text term="in" font-style="italic" text-case="capitalize-first" suffix=": "/>
<!--Nomes de editores-->
<text macro="container-contributors" suffix=". "/>
<!--Titulo da conferencia-->
<text macro="container-title" suffix=". "/>
<!--Traducao INSERI DA ABNT (ver como funciona) -->
<text macro="translator" suffix=". "/>
<!-- <text variable="collection-title" suffix=" "/> AQUI INSERIA A SÉRIE OU COLEÇÃO DENTRO DO TEXTO -->
<!--Edicao-->
<text macro="edition" suffix="., "/>
<!-- A VÍRGULA QUE SEPARA A EDIÇÃO DO LOCAL DA OBRA -->
<!--Local, data, etc-->
<text macro="publisher" suffix=". "/>
<!--Dados complementares "pagina, volume"-->
<text macro="locators" suffix=". "/>
<text macro="access"/>
</group>
</else-if>
<!--Artigo de revista, jornal, etc-->
<else-if type="article-newspaper article-magazine article-journal" match="any">
<group>
<!--Autor-->
<text macro="author" suffix=". "/>
<!--Titulo do artigo-->
<text macro="title" suffix=". "/>
<!--Titulo da publicacao-->
<text macro="container-title" suffix=", "/>
<!--Titulo da serie-->
<text macro="collection-title" suffix=". "/>
<text macro="place"/>
<!--Edicao-->
<text macro="edition" suffix=", "/>
<!--Dados complementares "pagina, volume"-->
<text macro="locators" suffix=", "/>
<!--Data-->
<text macro="issued" suffix=". "/>
<text macro="access"/>
</group>
</else-if>
<!--Tese-->
<else-if type="thesis">
<group>
<!--Autor-->
<text macro="author" suffix=". "/>
<!--Titulo-->
<text macro="title" suffix=". "/>
<text macro="issued-year" suffix=". "/>
<text variable="number-of-pages" suffix=" f. "/>
<!-- INSERINDO FOLHAS DE DISSERTAÇÕES E TESES -->
<!--Tipo-->
<text macro="genre" suffix=" - "/>
<!--Local, data, etc-->
<text variable="publisher" suffix=", "/>
<text macro="place"/>
<text macro="issued" suffix="."/>
<text macro="access"/>
</group>
</else-if>
<!-- Nao ha norma ABNT para manuscritos -->
<else-if type="manuscript">
<group>
<!--Autor-->
<text macro="author" suffix=". "/>
<!--Titulo-->
<text macro="title" suffix=". "/>
<!--Edicao-->
<text macro="edition" suffix=". "/>
<text macro="place"/>
<!-- RETIREI O suffix=", " pois não aparece na publicação -->
<!--Data-->
<text macro="issued" suffix=". "/>
<!--URL, data do acesso-->
<text macro="access" suffix=". "/>
<!--Arquive-->
<text macro="archive" suffix=". "/>
</group>
</else-if>
<!--Pagina da WEB-->
<else-if type="webpage">
<group>
<!--Autor-->
<text macro="author" suffix=". "/>
<!--Titulo-->
<text macro="title" suffix=". "/>
<text macro="genre" suffix=". "/>
<text macro="issued-year" suffix="."/>
<!--URL, data do acesso-->
<text macro="access" suffix=". "/>
</group>
</else-if>
<!--Relatorio-->
<else-if type="report">
<group>
<!--Autor-->
<text macro="author" suffix=". "/>
<!--Titulo-->
<text macro="title"/>
<!--Nomes de editores-->
<text macro="container-contributors"/>
<text macro="secondary-contributors"/>
<!--Titulo da publicacao-->
<text macro="container-title"/>
<text variable="collection-title" prefix=": "/>
<!--Dados complementares "pagina, volume"-->
<text macro="locators"/>
<!--Nome do evento, conferencia-->
<text macro="event"/>
<!--Local, data, etc-->
<text macro="publisher" prefix=". " suffix=". "/>
<!--URL, data do acesso-->
<text macro="access" suffix="."/>
</group>
</else-if>
<!--Texto para Discussao (Verbete de Dicionario)-->
<else-if type="entry-dictionary">
<group>
<!--Autor-->
<text macro="author" suffix=". "/>
<!--Titulo-->
<text macro="title"/>
<!--Nomes de editores-->
<text macro="container-contributors"/>
<text macro="secondary-contributors"/>
<!--Titulo da publicacao-->
<text macro="container-title"/>
<text variable="collection-title" prefix=": " suffix=". "/>
<!--Dados complementares "pagina, volume"-->
<text macro="locators"/>
<!--Nome do evento, conferencia-->
<text macro="event"/>
<!--Local, data, etc-->
<text macro="publisher" prefix=". " suffix=". "/>
<text macro="collection-title" prefix="(Texto para discussao, n. " suffix=")."/>
<!--URL, data do acesso-->
<text macro="access"/>
</group>
</else-if>
<!--Nota Tecnica (Verbete de Enciclopedia)-->
<else-if type="entry-encyclopedia">
<group>
<!--Autor-->
<text macro="author" suffix=". "/>
<!--Titulo-->
<text macro="title" suffix=". "/>
<text term="in" font-style="italic" text-case="capitalize-first" suffix=": "/>
<text macro="container-title" suffix="."/>
<!--Local-->
<text variable="publisher-place" prefix=". " suffix=": "/>
<!--Editor-->
<text variable="publisher"/>
<!--Data-->
<text macro="issued" prefix="," suffix=". "/>
</group>
</else-if>
<!--Publicacao em conferencia-->
<else-if type="paper-conference">
<!--Autor-->
<text macro="author" suffix=". "/>
<!--Titulo-->
<text macro="title" suffix="."/>
<text term="in" font-style="italic" text-case="capitalize-first" prefix=" " suffix=": "/>
<!--Nomes de editores -->
<text macro="container-contributors" text-case="uppercase"/>
<text macro="secondary-contributors"/>
<!--Titulo da publicacao-->
<text macro="container-title"/>
<!--Dados complementares "pagina, volume"-->
<text macro="locators"/>
<group delimiter=". " prefix=". " suffix=". ">
<!--Nome do evento, conferencia-->
<text macro="event"/>
</group>
<text macro="publisher"/>
<text variable="page" prefix=" p. " suffix="."/>
<text macro="access"/>
</else-if>
<else-if type="legislation legal_case" match="any">
<group>
<!--Autor-->
<text macro="author" suffix=". "/>
<!--Titulo-->
<text macro="title"/>
<text variable="abstract" prefix=". " suffix=". "/>
<!--Titulo da publicacao-->
<text macro="container-title" suffix=", "/>
<text variable="publisher-place" suffix=", "/>
<text macro="issued-legislation" suffix=". "/>
<text macro="section" prefix="Seção " suffix=", "/>
<text variable="page" prefix="p. " suffix="."/>
<text macro="access"/>
</group>
</else-if>
<else-if type="patent" match="any">
<group>
<text macro="author" suffix=". "/>
<text macro="title" prefix=" "/>
<text variable="number" prefix=", " suffix=", "/>
<text macro="issued" suffix=". "/>
</group>
</else-if>
<else-if type="interview song speech" match="any">
<group>
<text macro="author" suffix=". "/>
<text macro="title" suffix=". "/>
<text macro="publisher"/>
<text variable="medium"/>
</group>
</else-if>
<else-if type="broadcast motion_picture" match="any">
<group>
<text macro="title"/>
<text value="Direção" text-case="capitalize-first" prefix=". " suffix=": "/>
<text macro="director" suffix=". "/>
<text macro="publisher"/>
<text variable="medium"/>
<text macro="access"/>
</group>
</else-if>
<else-if type="dataset" match="any">
<group>
<text macro="author"/>
<text macro="title" suffix=". "/>
<text variable="version" prefix=". "/>
<text macro="publisher"/>
<text variable="medium"/>
<text macro="access"/>
</group>
</else-if>
<else>
<!-- Inserindo referências de Documentos -->
<text macro="author" suffix=". "/>
<text macro="title" suffix=". "/>
<text macro="container-contributors"/>
<text macro="secondary-contributors"/>
<text macro="container-title"/>
<text variable="collection-title" prefix=": " suffix="."/>
<text macro="locators"/>
<group delimiter=". " prefix=". " suffix=". ">
<!--Nome do evento, conferencia-->
<text macro="event"/>
</group>
<!--Local-->
<text variable="publisher-place" suffix=" "/>
<!--Editor-->
<text variable="publisher" suffix=", "/>
<!-- Neste campo 'extra' podemos inserir o local da publicação do documento -->
<text variable="note" suffix=""/>
<!--Data-->
<text macro="issued" suffix=". "/>
<!-- REMOVI O prefix=", " DO ORIGINAL -->
<text variable="number-of-pages" suffix=" p. "/>
<!-- INSERINDO PÁGINAS DO DOCUMENTO -->
<text macro="section" prefix="(" suffix=") "/>
<!-- INSERINDO INFORMAÇÕES ADICIONAIS SOBRE O DOCUMENTO, ENTRE PARÊNTESES -->
<!--URL, data do acesso-->
<text macro="access"/>
<text variable="medium"/>
</else>
</choose>
</layout>
</bibliography>
</style>

View File

@ -0,0 +1,7 @@
title: Lightbox
author: Posit Software, PBC
version: 0.1.9
quarto-required: ">=1.2.198"
contributes:
filters:
- lightbox.lua

View File

@ -0,0 +1,9 @@
body:not(.glightbox-mobile) div.gslide div.gslide-description,
body:not(.glightbox-mobile) div.gslide-description .gslide-title,
body:not(.glightbox-mobile) div.gslide-description .gslide-desc {
color: var(--quarto-body-color);
background-color: var(--quarto-body-bg);
}

View File

@ -0,0 +1,251 @@
-- whether we're automatically lightboxing
local auto = false
-- whether we need lightbox dependencies added
local needsLightbox = false
-- a counter used to ensure each image is in its own gallery
local imgCount = 0
-- attributes to forward from the image to the newly created link
local kDescription = "description"
local kForwardedAttr = {
"title", kDescription, "desc-position",
"type", "effect", "zoomable", "draggable"
}
local kLightboxClass = "lightbox"
local kNoLightboxClass = "nolightbox"
local kGalleryPrefix = "quarto-lightbox-gallery-"
-- A list of images already within links that we can use to filter
local imagesWithinLinks = pandoc.List({})
local function readAttrValue(el, attrName)
if attrName == kDescription then
local doc = pandoc.read(el.attr.attributes[attrName])
local attrInlines = doc.blocks[1].content
return pandoc.write(pandoc.Pandoc(attrInlines), "html")
else
return el[attrName]
end
end
return {
{
Meta = function(meta)
-- If the mode is auto, we need go ahead and
-- run if there are any images (ideally we would)
-- filter to images in the body, but that can be
-- left for future me to deal with
-- supports:
-- lightbox: auto
-- or
-- lightbox:
-- match: auto
local lbMeta = meta.lightbox
if lbMeta ~= nil and type(lbMeta) == 'table' then
if lbMeta[1] ~= nil then
if lbMeta[1]['text'] == "auto" then
auto = true
end
elseif lbMeta.match ~= nil and pandoc.utils.stringify(lbMeta.match) == 'auto' then
auto = true
elseif lbMeta == true then
auto = true
end
end
end,
-- Find images that are already within links
-- we'll use this to filter out these images if
-- the most is auto
Link = function(linkEl)
pandoc.walk_inline(linkEl, {
Image = function(imageEl)
imagesWithinLinks[#imagesWithinLinks + 1] = imageEl
end
})
end
},{
Div = function(div)
if div.classes:includes("cell") and div.attributes["lightbox"] ~= nil then
meta = quarto.json.decode(div.attributes["lightbox"])
local imgCount=0
div = div:walk({
Image = function(imgEl)
imgCount = imgCount + 1
if (type(meta) == "table" and meta[kNoLightboxClass] == true) or meta == false then
imgEl.classes:insert(kNoLightboxClass)
else
if not auto and ((type(meta) == "table" and not meta[kNoLightboxClass]) or meta == true) then
imgEl.classes:insert(kLightboxClass)
end
if (type(meta) == "table") then
if meta.group then
imgEl.attr.attributes.group = meta.group or imgEl.attr.attributes.group
end
for _, v in next, kForwardedAttr do
if type(meta[v]) == "table" and #meta[v] > 1 then
-- if list attributes it should be one per plot
if imgCount > #meta[v] then
quarto.log.warning("More plots than '" .. v .. "' passed in YAML chunk options.")
else
attrLb = meta[v][imgCount]
end
else
-- Otherwise reuse the single attributes
attrLb = meta[v]
end
imgEl.attr.attributes[v] = attrLb or imgEl.attr.attributes[v]
end
end
end
return imgEl
end
})
div.attributes["lightbox"] = nil
end
return div
end
},
{
Image = function(imgEl)
if quarto.doc.is_format("html:js") then
local isAlreadyLinked = imagesWithinLinks:includes(imgEl)
if (not isAlreadyLinked and auto and not imgEl.classes:includes(kNoLightboxClass))
or imgEl.classes:includes('lightbox') then
-- note that we need to include the dependency for lightbox
needsLightbox = true
imgCount = imgCount + 1
-- remove the class from the image
imgEl.attr.classes = imgEl.attr.classes:filter(function(clz)
return clz ~= kLightboxClass
end)
-- attributes for the link
local linkAttributes = {}
-- mark this image as a lightbox target
linkAttributes.class = kLightboxClass
-- get the alt text from image and use that as title
local title = nil
if imgEl.caption ~= nil and #imgEl.caption > 0 then
linkAttributes.title = pandoc.utils.stringify(imgEl.caption)
elseif imgEl.attributes['fig-alt'] ~= nil and #imgEl.attributes['fig-alt'] > 0 then
linkAttributes.title = pandoc.utils.stringify(imgEl.attributes['fig-alt'])
end
-- move a group attribute to the link, if present
if imgEl.attr.attributes.group ~= nil then
linkAttributes.gallery = imgEl.attr.attributes.group
imgEl.attr.attributes.group = nil
else
linkAttributes.gallery = kGalleryPrefix .. imgCount
end
-- forward any other known attributes
for i, v in ipairs(kForwardedAttr) do
if imgEl.attr.attributes[v] ~= nil then
-- forward the attribute
linkAttributes[v] = readAttrValue(imgEl, v)
-- clear the attribute
imgEl.attr.attributes[v] = nil
end
-- clear the title
if (imgEl.title == 'fig:') then
imgEl.title = ""
end
end
-- wrap decorated images in a link with appropriate attrs
local link = pandoc.Link({imgEl}, imgEl.src, nil, linkAttributes)
return link
end
end
end,
Meta = function(meta)
-- If we discovered lightbox-able images
-- we need to include the dependencies
if needsLightbox then
-- add the dependency
quarto.doc.add_html_dependency({
name = 'glightbox',
scripts = {'resources/js/glightbox.min.js'},
stylesheets = {'resources/css/glightbox.min.css', 'lightbox.css'}
})
-- read lightbox options
local lbMeta = meta.lightbox
local lbOptions = {}
local readEffect = function(el)
local val = pandoc.utils.stringify(el)
if val == "fade" or val == "zoom" or val == "none" then
return val
else
error("Invalid effect " + val)
end
end
-- permitted options include:
-- lightbox:
-- effect: zoom | fade | none
-- desc-position: top | bottom | left |right
-- loop: true | false
-- class: <class-name>
local effect = "zoom"
local descPosition = "bottom"
local loop = true
local skin = nil
-- The selector controls which elements are targeted.
-- currently, it always targets .lightbox elements
-- and there is no way for the user to change this
local selector = "." .. kLightboxClass
if lbMeta ~= nil and type(lbMeta) == 'table' then
if lbMeta.effect ~= nil then
effect = readEffect(lbMeta.effect)
end
if lbMeta['desc-position'] ~= nil then
descPosition = pandoc.utils.stringify(lbMeta['desc-position'])
end
if lbMeta['css-class'] ~= nil then
skin = pandoc.utils.stringify(lbMeta['css-class'])
end
if lbMeta.loop ~= nil then
loop = lbMeta.loop
end
end
-- Generate the options to configure lightbox
local options = {
selector = selector,
closeEffect = effect,
openEffect = effect,
descPosition = descPosition,
loop = loop,
}
if skin ~= nil then
options.skin = skin
end
local optionsJson = quarto.json.encode(options)
-- generate the initialization script with the correct options
local scriptTag = "<script>var lightboxQuarto = GLightbox(" .. optionsJson .. ");</script>"
-- inject the rendering code
quarto.doc.include_text("after-body", scriptTag)
end
end
}}

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

161
_quarto.yml Executable file
View File

@ -0,0 +1,161 @@
# Em navbar -> logo-href e navbar -> logo precisa colocar a url da capa animada e da capa estática, respectivamente. Assim como em sidebar -> logo colocar url da capa estática
project:
type: book # não altere
output-dir: trigonometria-hiperbolica # Escolha aqui a url do seu livro. O valor escolhido aqui resultará em algo como http://livro.online/url-do-seu-livro se essa url já não estiver sendo usada.
post-render:
- _extensions/moan-livro/preparacao-moan-ALTERADO.py # Não altere
- correcao.py
- correcao2.py
preview:
port: 4000 # não altere
browser: true # não altere
filters: # não altere
- lightbox
lightbox: auto # não altere
include-after-body: # não altere
text: |
<script src="https://leitorweb.livro.online/leitor-web.min.js"></script>
<link rel="stylesheet" href="https://leitorweb.livro.online/css/configuracoesleitor.min.css" type="text/css">
lang: pt-BR # não altere
language:
toc-title-document: "Neste capítulo" # não altere
# number-sections precisa existir (seja true ou false) para o script que cria as referencias funcione direito
number-sections: true # não altere
crossref:
chapters: true # não altere
# É OBRIGATÓRIO informar se é ou não é um dicionário para as referências serem criadas corretamente
# TB é OBRIGATÓRIO colocar uma div com as classes .hidden e .um_capitulo em todos os capítulos que nao sao verbetes em um dicionário. Se nao for dicionário, nao há necessidade
controle-moan:
dicionario: false
# Metadados da Editora Moan. Será usado para gerar o identificador ark e para os metadados que ficarão online
# Informações como Título (title), subtítulo (subtitle), descrição (description), autor (author), data (date), editor (editor), editora (publisher), cidade (publisher-place), isbn da versao impressa (isbn) devem aparecer aqui e na entrada book abaixo.
moan-dados:
ark: 68745/eMR8J
título: "As funções trigonométricas circulares e hiperbólicas"
formato: Livro Digital (online)
autor: Sandro Marcos Guzzo
apontamento: https://livro.online/trigonometria-hiperbolica # A editora moan depois altera isso
edição: 1
descrição: Esta obra trata da construção da trigonometria hiperbólica na hipérbole trigonométrica, fazendo a comparação com a trigonometria circular. São abordados aspectos das funções trigonométricas circulares e hiperbólicas, relacionados ao cálculo diferencial e integral.
editora: Editora Moan
local: Foz do Iguaçu - PR, Brasil
editor: Rafael Tavares Juliani
diagramador: Rafael Tavares Juliani
capista: Rafael Tavares Juliani
revisor: Sandra Maria Tieppo e Emerson Mário Boldo
palavras-chave: trigonometria,trigonometria hiperbólica,funções trigonométricas,matemática
área: Matemática
cdd: 516.24
bisac: MAT012000 e MAT032000
ano-publicação: 2021
data-publicação: 22/03/2021
idioma: Português do Brasil (pt-BR)
país: Brasil
faixa-etária: Acima de 12 anos
ark-versao-impressa: 68745/eMR8J.4N
isbn-versao-impressa: 9786599140440
direitos-autorais: © Sandro Marcos Guzzo e a Editora Moan, 2021
licenca: Todos os direitos reservados
licenca-link: https://www.planalto.gov.br/ccivil_03/leis/l9610.htm
# Abaixo, altere somente o título do seu livro, o subtítulo (se houver, caso contrário, deixe em branco, ou seja, apague o que está ali), o nome do autor e a descrição.
book:
isbn: 978-65-99140-44-0
google-analytics: G-G6VT93GC1X
cookie-consent:
palette: light
policy-url: "https://livro.online/politica-de-cookies-br"
language: pt
prefs-text: Preferências de cookie
search:
type: textbox
favicon: img/favicon.png # precisa ter esse nome e estar nessa pasta. Mas a Editora Moan vai gerar essa imagens para você, então não precisa alterar nada aqui.
open-graph:
image: img/og.jpg # precisa ter esse nome e estar nessa pasta. Mas a Editora Moan vai gerar essa imagens para você, então não precisa alterar nada aqui.
twitter-card:
image: img/og.jpg # precisa ter esse nome e estar nessa pasta. Mas a Editora Moan vai gerar essa imagens para você, então não precisa alterar nada aqui.
title: "As funções trigonométricas circulares e hiperbólicas"
subtitle: ""
description: "Esta obra trata da construção da trigonometria hiperbólica na hipérbole trigonométrica, fazendo a comparação com a trigonometria circular. São abordados aspectos das funções trigonométricas circulares e hiperbólicas, relacionados ao cálculo diferencial e integral."
author: Sandro Marcos Guzzo
#primeiro o mês, depois o dia e depois o ano
date: "03/22/2021"
editor: Rafael Tavares Juliani
publisher: Editora Moan
publisher-place: Foz do Iguaçu - PR, Brasil
page-navigation: true
reader-mode: true
sharing: [facebook, linkedin]
sidebar:
title: "As funções trigonométricas circulares e hiperbólicas"
logo: img/capa.webp # precisa ter esse nome e estar nessa pasta. Mas a Editora Moan vai gerar essa imagens para você, então não precisa alterar nada aqui.
tools:
- icon: card-image
text: Capa Animada
href: img/CapaAnim.webp # precisa ter esse nome e estar nessa pasta. Mas a Editora Moan vai gerar essa imagens para você, então não precisa alterar nada aqui.
- icon: bi bi-git
text: Alterações e Versões
href: https://gitea.livro.online/editoramoan/trigonometria-hiperbolica/commits/branch/main
- icon: envelope-open-heart
href: https://livro.online/doacao
text: Doar
- icon: printer-fill
href: index.html#versão-impressa
text: Versão Impressa
- icon: book-half
href: https://livro.online
text: Outros Livros
navbar:
logo: img/capa.webp # precisa ter esse nome e estar nessa pasta. Mas a Editora Moan vai gerar essa imagens para você, então não precisa alterar nada aqui.
logo-href: img/CapaAnim.webp # precisa ter esse nome e estar nessa pasta. Mas a Editora Moan vai gerar essa imagens para você, então não precisa alterar nada aqui.
comments:
hypothesis:
theme: clean
openSidebar: false
chapters:
- index.qmd
- agradecimentos.qmd
- apresentacao.qmd
- funcoes-trigonometricas-circulares.qmd
- funcoes-trigonometricas-hiperbolicas.qmd
- igualdades-exponenciais-e-logaritmicas.qmd
- aplicacoes.qmd
- referencias.qmd
- indice-remissivo.qmd
citation: true
bibliography: referencias.bib
csl: _extensions/moan-livro/universidade-estadual-de-alagoas-abnt.csl
google-scholar: true
format:
moan-livro-html:
theme:
light:
- cosmo
- _extensions/moan-livro/custom.scss
- estilos.css
dark:
- superhero
- _extensions/moan-livro/custom.scss
- estilos.css
format-links: false

File diff suppressed because it is too large Load Diff

3
_variables.yml Executable file
View File

@ -0,0 +1,3 @@
e-mail: "[editora@livro.online](mailto:editora@livro.online)"
whatsapp: "[+55 (45) 9 3505-0721](https://api.whatsapp.com/send?phone=5545935050721)"

13
agradecimentos.qmd Executable file
View File

@ -0,0 +1,13 @@
# Agradecimentos {.unnumbered}
```{=html}
<div id="conteudo-capitulo">
<p>Meus agradecimentos às pessoas que ajudaram na elaboração deste texto. Em especial:</p>
<p>À minha mulher Sandra Maria Tieppo pelo apoio constante e o primeiro trabalho de revisão e correção.</p>
<p>Ao professor Rogério Luis Rizzi pelo material bibliográfico que serviu de base para este texto.</p>
<p>Ao professor Ma To Fu pela ideia do capítulo com aplicações e ao professor Emerson Mário Boldo pela revisão desse mesmo capítulo.</p>
</div>
```

4582
aplicacoes.qmd Executable file

File diff suppressed because it is too large Load Diff

67
apresentacao.qmd Executable file
View File

@ -0,0 +1,67 @@
# Apresentação {.unnumbered}
```{=html}
<div id="conteudo-capitulo">
<p class="unidade" id="AP1" title="AP1">
As funções trigonométricas circulares e hiperbólicas fazem parte de qualquer curso de Cálculo Diferencial e Integral. A trigonometria circular, conhecida dos alunos desde o ensino fundamental e médio, é em geral bem fundamentada e organizada. São relações definidas e obtidas no triângulo retângulo ou na circunferência trigonométrica e todas as propriedades e identidades, envolvendo essas funções, são provadas a partir das propriedades da circunferência e dos triângulos.
</p>
<p class="unidade" id="AP2" title="AP2">
Esse fato já não ocorre com as funções trigonométricas hiperbólicas. Em geral, os livros de Cálculo Diferencial e Integral definem as funções trigonométricas hiperbólicas como soma de funções exponenciais. Para ser mais preciso,
<!-- MATH
\begin{displaymath}
{\mathrm{senh}}x = \frac{e^{x}-e^{-x}}{2} \qquad \text{e} \qquad \cosh x = \frac{e^{x} + e^{-x}}{2}.
\end{displaymath}
-->
</p>
<div class="mathdisplay unidade" id="AP3" title="AP3">
<img style="height: 4.72ex; vertical-align: -1.55ex; " src="img/img10.svg" alt="">&nbsp; &nbsp;e<img style="height: 4.72ex; vertical-align: -1.55ex; " src="img/img11.svg" alt="$\displaystyle \qquad \cosh x = \frac{e^{x} + e^{-x}}{2}. $">
</div>
<p class="unidade" id="AP4" title="AP4">
Todas as propriedades envolvendo as funções trigonométricas hiperbólicas são então deduzidas a partir dessas igualdades e de propriedades das funções exponenciais e logarítmicas. Também, as fórmulas de derivação são obtidas usando as fórmulas de derivação para a função exponencial.
</p>
<p class="unidade" id="AP5" title="AP5">
Assim como a trigonometria circular, a trigonometria hiperbólica é também construída e fundamentada. Não sobre a circunferência, mas sobre a hipérbole trigonométrica. As propriedades dessas funções são então consequências de propriedades algébricas e geométricas dessa hipérbole.
</p>
<p class="unidade" id="AP6" title="AP6">
Este assunto me deixou curioso por muito tempo até que resolvi procurar mais informações a esse respeito. Hoje, com essas informações localizadas e reunidas, faço este texto com o objetivo de compartilhar os conhecimentos adquiridos nesse assunto. Para tornar o estudo completo, neste texto é abordada também a trigonometria circular, que na maioria dos livros já está bem detalhada.
</p>
<p class="unidade" id="AP7" title="AP7">
A proposta deste texto é complementar um curso de Cálculo Diferencial e Integral com detalhamento no trato das funções trigonométricas. Do modo que este texto está preparado, esperamos que o leitor, em cada etapa, esteja familiarizado com os conceitos abordados, como por exemplo os conceitos de continuidade, derivação e função inversa.
</p>
<p class="unidade" id="AP8" title="AP8">
O primeiro capítulo tratará das funções trigonométricas circulares. Construiremos primeiramente a trigonometria
circular sobre o círculo trigonométrico com a dedução das principais identidades trigonométricas. Feito isto,
definiremos as funções trigonométricas circulares e estudaremos alguns de seus principais aspectos, como domínio, imagem, gráficos, continuidade e derivadas dessas funções. Para finalizar o primeiro capítulo, estudaremos as funções trigonométricas inversas e suas derivadas.
</p>
<p class="unidade" id="AP9" title="AP9">
No segundo capítulo, trataremos da trigonometria hiperbólica. Estudaremos a definição das funções trigonométricas hiperbólicas na hipérbole trigonométrica e as principais identidades trigonométricas hiperbólicas. Analisaremos as funções trigonométricas hiperbólicas, seus gráficos, continuidade e a derivada dessas funções. E por fim, estudaremos as funções trigonométricas hiperbólicas inversas e suas derivadas.
</p>
<p class="unidade" id="AP10" title="AP10">
O capítulo 3 é dedicado a mostrar que as identidades trigonométricas hiperbólicas envolvendo as funções exponenciais são verdadeiras. Obteremos, ainda, identidades logarítmicas para as funções trigonométricas hiperbólicas inversas e com o auxílio da álgebra de números complexos, obteremos identidades similares para as funções trigonométricas circulares.
</p>
<p class="unidade" id="AP11" title="AP11">
No capítulo 4, são apresentadas algumas aplicações das funções trigonométricas, tanto as circulares quanto as
hiperbólicas. Para melhor compreensão deste capítulo, recomendamos ao leitor o conhecimento de alguns conceitos
físicos.
</p>
<p class="unidade" id="AP12" title="AP12">
Ao final de cada seção, apresentaremos uma tabela resumida com os principais resultados obtidos naquela seção. Essas tabelas tem o objetivo de facilitar a busca de informações desejadas por parte do leitor.
</p>
<br />
<table style="width:227; text-align: right; ">
<tbody><tr><td style="text-align: right;">
<div class="centerline" id="par22439">
27. Abril 2021</div>
<div class="centerline" id="par22440">
Sandro Marcos Guzzo</div>
</td></tr>
</tbody></table>
</div>
```

34
correcao.py Executable file
View File

@ -0,0 +1,34 @@
import os
import shutil
import yaml
def copiar_pasta(origem, destino):
try:
shutil.copytree(origem, destino, dirs_exist_ok=True)
print(f'Conteúdos de "{origem}" copiados para "{destino}" com sucesso.')
except Exception as e:
print(f'Ocorreu um erro ao copiar os conteúdos de "{origem}" para "{destino}": {e}')
def main():
# Ler o arquivo _quarto.yml
with open('_quarto.yml', 'r') as yml_file:
config = yaml.load(yml_file, Loader=yaml.FullLoader)
# Verificar se as chaves necessárias estão presentes no arquivo
if 'project' in config and 'output-dir' in config['project']:
output_dir = config['project']['output-dir']
else:
print('Chaves ausentes no arquivo _quarto.yml. Certifique-se de que as chaves project e output-dir estão presentes.')
return
# Lista de pastas a serem copiadas
pastas_a_copiar = ['scripts', 'gfs_artemisia', 'oswald', 'suez', 'img', 'interativo']
# Copiar o conteúdo das pastas para o diretório de saída
for pasta in pastas_a_copiar:
origem = os.path.join(os.getcwd(), pasta)
destino = os.path.join(os.getcwd(), output_dir, pasta)
copiar_pasta(origem, destino)
if __name__ == "__main__":
main()

37
correcao2.py Executable file
View File

@ -0,0 +1,37 @@
import os
import yaml
from bs4 import BeautifulSoup
def adicionar_div_correcao(html_path):
with open(html_path, 'r', encoding='utf-8') as file:
soup = BeautifulSoup(file, 'html.parser')
for div_tag in soup.find_all('div', class_='raw_html'):
code_tag = div_tag.find('code')
if code_tag:
codigo = code_tag.decode_contents()
nova_div = soup.new_tag('div', **{'class': 'correcao'})
nova_div.append(BeautifulSoup(codigo, 'html.parser'))
div_tag.replace_with(nova_div)
with open(html_path, 'w', encoding='utf-8') as file:
file.write(str(soup.prettify(formatter=None)))
def processar_htmls(diretorio):
for root, dirs, files in os.walk(diretorio):
for file_name in files:
if file_name.endswith('.html'):
html_path = os.path.join(root, file_name)
adicionar_div_correcao(html_path)
def obter_output_dir_from_yaml():
quarto_yaml_path = "_quarto.yml"
with open(quarto_yaml_path, 'r', encoding='utf-8') as file:
config = yaml.safe_load(file)
return config['project']['output-dir']
if __name__ == "__main__":
output_dir = obter_output_dir_from_yaml()
pasta_htmls = os.path.join(os.path.dirname(__file__), output_dir)
processar_htmls(pasta_htmls)

329
estilos.css Executable file
View File

@ -0,0 +1,329 @@
/*-- scss:defaults --*/
/* TODO: Customize html appearance by setting SCSS variables */
/* See https://quarto.org/docs/output-formats/html-themes.html#theme-options */
/*-- scss:rules --*/
/* TODO: Provide custom CSS rules */
/*-- scss:defaults --*/
/*-- scss:rules --*/
#conteudo-capitulo, h1.title {
font-family: gfs_artemisia !important;
line-height: 1.5 !important;
-webkit-hyphens: auto;
hyphens: auto;
}
#conteudo-capitulo {margin-top: 45px;}
.tabela { display: table; }
.tablinha { display: table-row; }
.tabcel { display: table-cell; }
.tabcorpo {display: table-header-group;}
img {
image-rendering: -moz-crisp-edges; /* Firefox */
image-rendering: -o-crisp-edges; /* Opera */
image-rendering: -webkit-optimize-contrast; /* Webkit (non-standard naming) */
image-rendering: crisp-edges;
-ms-interpolation-mode: nearest-neighbor; /* IE (non-standard property) */
}
.mjx-container .mjx-math {
white-space: normal;
}
.container-fch {
max-width: 1060px;
margin: 0 auto;
}
@media(max-width:768px){
.wide {display:none;}
.mobilefont {font-size:0.8em;}
iframe.graficos {
height: 265px;
}
}
@media(min-width:768px){
.tight {display:none;}
}
@media(min-width:1300px){
iframe.graficos {
height: 305px !important;
}
}
.figura {
position: relative;
font-family: gfs_artemisia;
text-align: center;
padding: 0 !important;
overflow: hidden;
margin-top: 20px;
width: 100%;
display: block;
-webkit-column-break-inside: avoid;
page-break-inside: avoid;
break-inside: avoid;
line-height: 1.2;
}
span.legenda {
display: block;
margin-top: 22px;
margin-bottom: 30px;;
}
.figura a {text-align: center;}
.figura img {
text-align: center;
width: 75%;
max-width: 320px;
height: auto;
}
.interativo {
position: relative;
overflow: hidden;
margin-top: 20px;
display: block;
height: fit-content;
-webkit-column-break-inside: avoid;
page-break-inside: avoid;
break-inside: avoid;
}
.controles_interatividade {
text-align: center;
}
iframe.graficos {
overflow: hidden;
position: relative;
border: none;
display: block;
width: 100%;
margin: 0 auto;
height: 290px;
min-width: 280px;
max-width: 540px;
break-inside: avoid-column;
}
p.unidade {
text-align: justify;
text-indent: 35px !important;
margin-bottom: 13px !important;
font-size: 1.1em;
}
span.centro {
display: block;
text-align: center;
margin: 10px 0px
}
@font-face {
font-family: 'gfs_artemisia';
src: url('./gfs_artemisia/GFSArtemisia.otf') format('opentype'),
url('./gfs_artemisia/GFSArtemisia.ttf') format('trutype');
}
@font-face {
font-family: 'oswald';
src: url('./oswald/Oswald-Bold.otf') format('opentype'),
url('./oswald/Oswald-Bold.ttf') format('trutype');
}
h1 {
font-size: 28pt;
text-align: left;
margin-bottom: 43px;
}
#conteudo-capitulo h2 {
font-size: 15pt;
text-align: left;
margin-top: 30px;
font-weight: bold;
}
ul.item{
list-style: disc inside;
}
ul.item li {
margin-bottom: 12px;
line-height: 1.5 !important;
}
ul.listaLimpa {
margin-top: 20px;
}
table.equation {
display: inline;
}
.mathdisplay {
margin: 25px auto;
text-align: center;
}
td {
padding-bottom: 15px;
}
.CENTER {
margin: 20px auto;
text-align: center;
}
div.CENTER table div.CENTER img {
width: 80%;
max-width: 550px;
height: auto;
}
table {
margin: 0 auto;
}
.BOTTOM {
caption-side: bottom;
}
caption {
caption-side: bottom;
}
div.unidade {
margin-top: 30px;
margin-bottom: 30px;
}
DIV.equation { text-align-last:justify; white-space: nowrap; } /* place eq nos */
TABLE.PAD TD { padding:3px; }
TABLE.BORDER TR:first-child { border-top:1px solid black; border-bottom:1px solid black; font-weight: bold;}
TABLE.BORDER TR:last-child { border-bottom:1px solid black;}
TABLE.BORDER TD {padding-left: 10px; padding-right: 10px;}
TABLE.BORDER TR:hover {background: #5fade4}
TABLE.BORDER { width: 100%;}
TABLE.equation { margin:auto; } /* place eq nos at right/left edge */
TABLE.equation > * { vertical-align:baseline; }
TABLE.equation TD { white-space:nowrap; }
TABLE { border-collapse: collapse; }
.mathdisplay {
margin: 25px auto;
text-align: center; /* Centraliza o conteúdo da tabela */
position: relative;
}
.mathdisplay table {
display: inline-block; /* Faz a tabela se comportar como um bloco em linha */
text-align: initial; /* Reseta o alinhamento de texto */
}
td.eqno {
position: absolute;
right: 0;
} /* equation-number cells */
.referencia {
cursor: pointer;
}

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

Binary file not shown.

BIN
gfs_artemisia/GFSArtemisia.otf Executable file

Binary file not shown.

BIN
gfs_artemisia/GFSArtemisia.ttf Executable file

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

BIN
gfs_artemisia/GFSArtemisiaIt.otf Executable file

Binary file not shown.

Binary file not shown.

225
gfs_artemisia/OFL-FAQ.txt Executable file
View File

@ -0,0 +1,225 @@
OFL FAQ - Frequently Asked Questions about the SIL Open Font License (OFL)
Version 1.1 - 26 February 2007
(See http://scripts.sil.org/OFL for updates)
1 ABOUT USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL
1.1 Can I use the fonts in any publication, even embedded in the file?
Yes. You may use them like most other fonts, but unlike some fonts you may include an embedded subset of the fonts in your document. Such use does not require you to include this license or other files (listed in OFL condition 2), nor does it require any type of acknowledgement within the publication. Some mention of the font name within the publication information (such as in a colophon) is usually appreciated. If you wish to include the complete font as a separate file, you should distribute the full font package, including all existing acknowledgements, and comply with the OFL conditions. Of course, referencing or embedding an OFL font in any document does not change the license of the document itself. The requirement for fonts to remain under the OFL does not apply to any document created using the fonts and their derivatives. Similarly, creating any kind of graphic using a font under OFL does not make the resulting artwork subject to the OFL.
1.2 Can I make web pages using these fonts?
Yes! Go ahead! Using CSS (Cascading Style Sheets) is recommended.
1.3 Can I make the fonts available to others from my web site?
Yes, as long as you meet the conditions of the license (do not sell by itself, include the necessary files, rename Modified Versions, do not abuse the Author(s)' name(s) and do not sublicense).
1.4 Can the fonts be included with Free/Libre and Open Source Software collections such as GNU/Linux and BSD distributions?
Yes! Fonts licensed under the OFL can be freely aggregated with software under FLOSS (Free/Libre and Open Source Software) licenses. Since fonts are much more useful aggregated to than merged with existing software, possible incompatibility with existing software licenses is not a problem. You can also repackage the fonts and the accompanying components in a .rpm or .deb package and include them in distro CD/DVDs and online repositories.
1.5 I want to distribute the fonts with my program. Does this mean my program also has to be free and open source software?
No. Only the portions based on the font software are required to be released under the OFL. The intent of the license is to allow aggregation or bundling with software under restricted licensing as well.
1.6 Can I include the fonts on a CD of freeware or commercial fonts?
Yes, as long some other font or software is also on the disk, so the OFL font is not sold by itself.
1.7 Can I sell a software package that includes these fonts?
Yes, you can do this with both the Original Version and a Modified Version. Examples of bundling made possible by the OFL would include: word processors, design and publishing applications, training and educational software, edutainment software, etc.
1.8 Why won't the OFL let me sell the fonts alone?
The intent is to keep people from making money by simply redistributing the fonts. The only people who ought to profit directly from the fonts should be the original authors, and those authors have kindly given up potential direct income to distribute their fonts under the OFL. Please honor and respect their contribution!
1.9 I've come across a font released under the OFL. How can I easily get more information about the Original Version? How can I know where it stands compared to the Original Version or other Modified Versions?
Consult the copyright statement(s) in the license for ways to contact the original authors. Consult the FONTLOG for information on how the font differs from the Original Version, and get in touch with the various contributors via the information in the acknowledgment section. Please consider using the Original Versions of the fonts whenever possible.
1.10 What do you mean in condition 4? Can you provide examples of abusive promotion / endorsement / advertisement vs. normal acknowledgement?
The intent is that the goodwill and reputation of the author(s) should not be used in a way that makes it sound like the original author(s) endorse or approve of a specific Modified Version or software bundle. For example, it would not be right to advertise a word processor by naming the author(s) in a listing of software features, or to promote a Modified Version on a web site by saying "designed by ...". However, it would be appropriate to acknowledge the author(s) if your software package has a list of people who deserve thanks. We realize that this can seem to be a gray area, but the standard used to judge an acknowledgement is that if the acknowledgement benefits the author(s) it is allowed, but if it primarily benefits other parties, or could reflect poorly on the author(s), then it is not.
2 ABOUT MODIFYING OFL LICENSED FONTS
2.1 Can I change the fonts? Are there any limitations to what things I can and cannot change?
You are allowed to change anything, as long as such changes do not violate the terms of the license. In other words, you are not allowed to remove the copyright statement(s) from the font, but you could add additional information into it that covers your contribution.
2.2 I have a font that needs a few extra glyphs - can I take them from an OFL licensed font and copy them into mine?
Yes, but if you distribute that font to others it must be under the OFL, and include the information mentioned in condition 2 of the license.
2.3 Can I charge people for my additional work? In other words, if I add a bunch of special glyphs and/or OpenType/Graphite code, can I sell the enhanced font?
Not by itself. Derivative fonts must be released under the OFL and cannot be sold by themselves. It is permitted, however, to include them in a larger software package (such as text editors, office suites or operating systems), even if the larger package is sold. In that case, you are strongly encouraged, but not required, to also make that derived font easily and freely available outside of the larger package.
2.4 Can I pay someone to enhance the fonts for my use and distribution?
Yes. This is a good way to fund the further development of the fonts. Keep in mind, however, that if the font is distributed to others it must be under the OFL. You won't be able to recover your investment by exclusively selling the font, but you will be making a valuable contribution to the community. Please remember how you have benefitted from the contributions of others.
2.5 I need to make substantial revisions to the font to make it work with my program. It will be a lot of work, and a big investment, and I want to be sure that it can only be distributed with my program. Can I restrict its use?
No. If you redistribute a Modified Version of the font it must be under the OFL. You may not restrict it in any way. This is intended to ensure that all released improvements to the fonts become available to everyone. But you will likely get an edge over competitors by being the first to distribute a bundle with the enhancements. Again, please remember how you have benefitted from the contributions of others.
2.6 Do I have to make any derivative fonts (including source files, build scripts, documentation, etc.) publicly available?
No, but please do share your improvements with others. You may find that you receive more than what you gave in return.
2.7 Why can't I use the Reserved Font Name(s) in my derivative font names? I'd like people to know where the design came from.
The best way to acknowledge the source of the design is to thank the original authors and any other contributors in the files that are distributed with your revised font (although no acknowledgement is required). The FONTLOG is a natural place to do this. Reserved Font Name(s) ensure that the only fonts that have the original names are the unmodified Original Versions. This allows designers to maintain artistic integrity while allowing collaboration to happen. It eliminates potential confusion and name conflicts. When choosing a name be creative and avoid names that reuse almost all the same letters in the same order or sound like the original. Keep in mind that the Copyright Holder(s) can allow a specific trusted partner to use Reserved Font Name(s) through a separate written agreement.
2.8 What do you mean by "primary name as presented to the user"? Are you referring to the font menu name?
Yes, the requirement to change the visible name used to differentiate the font from others applies to the font menu name and other mechanisms to specify a font in a document. It would be fine, for example, to keep a text reference to the original fonts in the description field, in your modified source file or in documentation provided alongside your derivative as long as no one could be confused that your modified source is the original. But you cannot use the Reserved Font Names in any way to identify the font to the user (unless the Copyright Holder(s) allow(s) it through a separate agreement; see section 2.7). Users who install derivatives ("Modified Versions") on their systems should not see any of the original names ("Reserved Font Names") in their font menus, for example. Again, this is to ensure that users are not confused and do not mistake a font for another and so expect features only another derivative or the Original Version can actually offer. Ultimately, creating name conflicts will cause many problems for the users as well as for the designer of both the Original and Modified versions, so please think ahead and find a good name for your own derivative. Font substitution systems like fontconfig, or application-level font fallback configuration within OpenOffice.org or Scribus, will also get very confused if the name of the font they are configured to substitute to actually refers to another physical font on the user's hard drive. It will help everyone if Original Versions and Modified Versions can easily be distinguished from one another and from other derivatives. The substitution mechanism itself is outside the scope of the license. Users can always manually change a font reference in a document or set up some kind of substitution at a higher level but at the lower level the fonts themselves have to respect the Reserved Font Name(s) requirement to prevent ambiguity. If a substitution is currently active the user should be aware of it.
2.9 Am I not allowed to use any part of the Reserved Font Names?
You may not use the words of the font names, but you would be allowed to use parts of words, as long as you do not use any word from the Reserved Font Names entirely. We do not recommend using parts of words because of potential confusion, but it is allowed. For example, if "Foobar" was a Reserved Font Name, you would be allowed to use "Foo" or "bar", although we would not recommend it. Such an unfortunate choice would confuse the users of your fonts as well as make it harder for other designers to contribute.
2.10 So what should I, as an author, identify as Reserved Font Names?
Original authors are encouraged to name their fonts using clear, distinct names, and only declare the unique parts of the name as Reserved Font Names. For example, the author of a font called "Foobar Sans" would declare "Foobar" as a Reserved Font Name, but not "Sans", as that is a common typographical term, and may be a useful word to use in a derivative font name. Reserved Font Names should also be single words. A font called "Flowing River" should have Reserved Font Names "Flowing" and "River", not "Flowing River".
2.11 Do I, as an author, have to identify any Reserved Font Names?
No, but we strongly encourage you to do so. This is to avoid confusion between your work and Modified versions. You may, however, give certain trusted parties the right to use any of your Reserved Font Names through separate written agreements. For example, even if "Foobar" is a RFN, you could write up an agreement to give company "XYZ" the right to distribute a modified version with a name that includes "Foobar". This allows for freedom without confusion.
2.12 Are any names (such as the main font name) reserved by default?
No. That is a change to the license as of version 1.1. If you want any names to be Reserved Font Names, they must be specified after the copyright statement(s).
2.13 What is this FONTLOG thing exactly?
It has three purposes: 1) to provide basic information on the font to users and other developers, 2) to document changes that have been made to the font or accompanying files, either by the original authors or others, and 3) to provide a place to acknowledge the authors and other contributors. Please use it! See below for details on how changes should be noted.
2.14 Am I required to update the FONTLOG?
No, but users, designers and other developers might get very frustrated at you if you don't! People need to know how derivative fonts differ from the original, and how to take advantage of the changes, or build on them.
3 ABOUT THE FONTLOG
The FONTLOG can take a variety of formats, but should include these four sections:
3.1 FONTLOG for <FontFamilyName>
This file provides detailed information on the <FontFamilyName> font software. This information should be distributed along with the <FontFamilyName> fonts and any derivative works.
3.2 Basic Font Information
(Here is where you would describe the purpose and brief specifications for the font project, and where users can find more detailed documentation. It can also include references to how changes can be contributed back to the Original Version. You may also wish to include a short guide to the design, or a reference to such a document.)
3.3 ChangeLog
(This should list both major and minor changes, most recent first. Here are some examples:)
7 February 2007 (Pat Johnson) <NewFontFamilyName> Version 1.3
- Added Greek and Cyrillic glyphs
- Released as "<NewFontFamilyName>"
7 March 2006 (Fred Foobar) <NewFontFamilyName> Version 1.2
- Tweaked contextual behaviours
- Released as "<NewFontFamilyName>"
1 Feb 2005 (Jane Doe) <NewFontFamilyName> Version 1.1
- Improved build script performance and verbosity
- Extended the smart code documentation
- Corrected minor typos in the documentation
- Fixed position of combining inverted breve below (U+032F)
- Added OpenType/Graphite smart code for Armenian
- Added Armenian glyphs (U+0531 -> U+0587)
- Released as "<NewFontFamilyName>"
1 Jan 2005 (Joe Smith) <FontFamilyName> Version 1.0
- Initial release of font "<FontFamilyName>"
3.4 Acknowledgements
(Here is where contributors can be acknowledged.
If you make modifications be sure to add your name (N), email (E), web-address (W) and description (D). This list is sorted by last name in alphabetical order.)
N: Jane Doe
E: jane@university.edu
W: http://art.university.edu/projects/fonts
D: Contributor - Armenian glyphs and code
N: Fred Foobar
E: fred@foobar.org
W: http://foobar.org
D: Contributor - misc Graphite fixes
N: Pat Johnson
E: pat@fontstudio.org
W: http://pat.fontstudio.org
D: Designer - Greek & Cyrillic glyphs based on Roman design
N: Tom Parker
E: tom@company.com
W: http://www.company.com/tom/projects/fonts
D: Engineer - original smart font code
N: Joe Smith
E: joe@fontstudio.org
W: http://joe.fontstudio.org
D: Designer - original Roman glyphs
(Original authors can also include information here about their organization.)
4 ABOUT MAKING CONTRIBUTIONS
4.1 Why should I contribute my changes back to the original authors?
It would benefit many people if you contributed back to what you've received. Providing your contributions and improvements to the fonts and other components (data files, source code, build scripts, documentation, etc.) could be a tremendous help and would encourage others to contribute as well and 'give back', which means you will have an opportunity to benefit from other people's contributions as well. Sometimes maintaining your own separate version takes more effort than merging back with the original. Be aware that any contributions, however, must be either your own original creation or work that you own, and you may be asked to affirm that clearly when you contribute.
4.2 I've made some very nice improvements to the font, will you consider adopting them and putting them into future Original Versions?
Most authors would be very happy to receive such contributions. Keep in mind that it is unlikely that they would want to incorporate major changes that would require additional work on their end. Any contributions would likely need to be made for all the fonts in a family and match the overall design and style. Authors are encouraged to include a guide to the design with the fonts. It would also help to have contributions submitted as patches or clearly marked changes (the use of smart source revision control systems like subversion, svk or bzr is a good idea). Examples of useful contributions are bug fixes, additional glyphs, stylistic alternates (and the smart font code to access them) or improved hinting.
4.3 How can I financially support the development of OFL fonts?
It is likely that most authors of OFL fonts would accept financial contributions - contact them for instructions on how to do this. Such contributions would support future development. You can also pay for others to enhance the fonts and contribute the results back to the original authors for inclusion in the Original Version.
5 ABOUT THE LICENSE
5.1 I see that this is version 1.1 of the license. Will there be later changes?
Version 1.1 is the first minor revision of the OFL. We are confident that version 1.1 will meet most needs, but are open to future improvements. Any revisions would be for future font releases, and previously existing licenses would remain in effect. No retroactive changes are possible, although the Copyright Holder(s) can re-release the font under a revised OFL. All versions will be available on our web site: http://scripts.sil.org/OFL.
5.2 Can I use the SIL Open Font License for my own fonts?
Yes! We heartily encourage anyone to use the OFL to distribute their own original fonts. It is a carefully constructed license that allows great freedom along with enough artistic integrity protection for the work of the authors as well as clear rules for other contributors and those who redistribute the fonts. Some additional information about using the OFL is included at the end of this FAQ.
5.3 Does this license restrict the rights of the Copyright Holder(s)?
No. The Copyright Holder(s) still retain(s) all the rights to their creation; they are only releasing a portion of it for use in a specific way. For example, the Copyright Holder(s) may choose to release a 'basic' version of their font under the OFL, but sell a restricted 'enhanced' version. Only the Copyright Holder(s) can do this.
5.4 Is the OFL a contract or a license?
The OFL is a license and not a contract and so does not require you to sign it to have legal validity. By using, modifying and redistributing components under the OFL you indicate that you accept the license.
5.5 How about translating the license and the FAQ into other languages?
SIL certainly recognises the need for people who are not familiar with English to be able to understand the OFL and this FAQ better in their own language. Making the license very clear and readable is a key goal of the OFL.
If you are an experienced translator, you are very welcome to help by translating the OFL and its FAQ so that designers and users in your language community can understand the license better. But only the original English version of the license has legal value and has been approved by the community. Translations do not count as legal substitutes and should only serve as a way to explain the original license. SIL - as the author and steward of the license for the community at large - does not approve any translation of the OFL as legally valid because even small translation ambiguities could be abused and create problems.
We give permission to publish unofficial translations into other languages provided that they comply with the following guidelines:
- put the following disclaimer in both English and the target language stating clearly that the translation is unofficial:
"This is an unofficial translation of the SIL Open Font License into $language. It was not published by SIL International, and does not legally state the distribution terms for fonts that use the OFL. A release under the OFL is only valid when using the original English text.
However, we recognize that this unofficial translation will help users and designers not familiar with English to understand the SIL OFL better and make it easier to use and release font families under this collaborative font design model. We encourage designers who consider releasing their creation under the OFL to read the FAQ in their own language if it is available.
Please go to http://scripts.sil.org/OFL for the official version of the license and the accompanying FAQ."
- keep your unofficial translation current and update it at our request if needed, for example if there is any ambiguity which could lead to confusion.
If you start such a unofficial translation effort of the OFL and its accompanying FAQ please let us know, thank you.
6 ABOUT SIL INTERNATIONAL
6.1 Who is SIL International and what does it do?
SIL International is a worldwide faith-based education and development organization (NGO) that studies, documents, and assists in developing the world's lesser-known languages through literacy, linguistics, translation, and other academic disciplines. SIL makes its services available to all without regard to religious belief, political ideology, gender, race, or ethnic background. SIL's members and volunteers share a Christian commitment.
6.2 What does this have to do with font licensing?
The ability to read, write, type and publish in one's own language is one of the most critical needs for millions of people around the world. This requires fonts that are widely available and support lesser-known languages. SIL develops - and encourages others to develop - a complete stack of writing systems implementation components available under open licenses. This open stack includes input methods, smart fonts, smart rendering libraries and smart applications. There has been a need for a common open license that is specifically applicable to fonts and related software (a crucial component of this stack) so SIL developed the SIL Open Font License with the help of the FLOSS community.
6.3 How can I contact SIL?
Our main web site is: http://www.sil.org/
Our site about complex scripts is: http://scripts.sil.org/
Information about this license (including contact email information) is at: http://scripts.sil.org/OFL
7 ABOUT USING THE OFL FOR YOUR ORIGINAL FONTS
If you want to release your fonts under the OFL, you only need to do the following:
7.1 Put your copyright and reserved font names information in the beginning of the main OFL file.
7.2 Put your copyright and the OFL references in your various font files (such as in the copyright, license and description fields) and in your other components (build scripts, glyph databases, documentation, rendering samples, etc).
7.3 Write an initial FONTLOG for your font and include it in the release package.
7.4 Include the OFL in your release package.
7.5 We also highly recommend you include the relevant practical documentation on the license by putting the OFL-FAQ in your package.
7.6 If you wish, you can use the OFL Graphics on your web page.
That's all. If you have any more questions please get in touch with us.

95
gfs_artemisia/OFL.txt Executable file
View File

@ -0,0 +1,95 @@
Copyright (c) 2007, Greek Font Society (www.greekfontsociety.org | gfs@greekfontsociety.org),
with Reserved Font Name 'GFS Artemisia'.
This Font Software is licensed under the SIL Open Font License, Version 1.1.
This license is copied below, and is also available with a FAQ at:
http://scripts.sil.org/OFL
-----------------------------------------------------------
SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
-----------------------------------------------------------
PREAMBLE
The goals of the Open Font License (OFL) are to stimulate worldwide
development of collaborative font projects, to support the font creation
efforts of academic and linguistic communities, and to provide a free and
open framework in which fonts may be shared and improved in partnership
with others.
The OFL allows the licensed fonts to be used, studied, modified and
redistributed freely as long as they are not sold by themselves. The
fonts, including any derivative works, can be bundled, embedded,
redistributed and/or sold with any software provided that any reserved
names are not used by derivative works. The fonts and derivatives,
however, cannot be released under any other type of license. The
requirement for fonts to remain under this license does not apply
to any document created using the fonts or their derivatives.
DEFINITIONS
"Font Software" refers to the set of files released by the Copyright
Holder(s) under this license and clearly marked as such. This may
include source files, build scripts and documentation.
"Reserved Font Name" refers to any names specified as such after the
copyright statement(s).
"Original Version" refers to the collection of Font Software components as
distributed by the Copyright Holder(s).
"Modified Version" refers to any derivative made by adding to, deleting,
or substituting -- in part or in whole -- any of the components of the
Original Version, by changing formats or by porting the Font Software to a
new environment.
"Author" refers to any designer, engineer, programmer, technical
writer or other person who contributed to the Font Software.
PERMISSION & CONDITIONS
Permission is hereby granted, free of charge, to any person obtaining
a copy of the Font Software, to use, study, copy, merge, embed, modify,
redistribute, and sell modified and unmodified copies of the Font
Software, subject to the following conditions:
1) Neither the Font Software nor any of its individual components,
in Original or Modified Versions, may be sold by itself.
2) Original or Modified Versions of the Font Software may be bundled,
redistributed and/or sold with any software, provided that each copy
contains the above copyright notice and this license. These can be
included either as stand-alone text files, human-readable headers or
in the appropriate machine-readable metadata fields within text or
binary files as long as those fields can be easily viewed by the user.
3) No Modified Version of the Font Software may use the Reserved Font
Name(s) unless explicit written permission is granted by the corresponding
Copyright Holder. This restriction only applies to the primary font name as
presented to the users.
4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
Software shall not be used to promote, endorse or advertise any
Modified Version, except to acknowledge the contribution(s) of the
Copyright Holder(s) and the Author(s) or with their explicit written
permission.
5) The Font Software, modified or unmodified, in part or in whole,
must be distributed entirely under this license, and must not be
distributed under any other license. The requirement for fonts to
remain under this license does not apply to any document created
using the Font Software.
TERMINATION
This license becomes null and void if any of the above conditions are
not met.
DISCLAIMER
THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
OTHER DEALINGS IN THE FONT SOFTWARE.

34
gfs_artemisia/readme.rtf Executable file
View File

@ -0,0 +1,34 @@
{\rtf1\mac\ansicpg10000\cocoartf824\cocoasubrtf380
{\fonttbl\f0\fnil\fcharset77 MyriadPro-Regular;\f1\fnil\fcharset77 MyriadPro-Bold;\f2\fnil\fcharset77 Georgia;
}
{\colortbl;\red255\green255\blue255;}
\paperw11899\paperh16839\margl1440\margr1440\vieww11900\viewh15820\viewkind1\viewscale100
\pard\tx566\tx1133\tx1700\tx2267\tx2834\tx3401\tx3968\tx4535\tx5102\tx5669\tx6236\tx6803\ql\qnatural\pardirnatural
\f0\fs24 \cf0 Thank you for downloading GFS Artemisia\
________________________________________\
\
You may use these fonts for personal and commercial use. These fonts may be freely redistributed, provided that you do not alter them in any way and that you credit GFS for this.\
\
These fonts are distributed free and may not be sold or resold for any purposes.\
\
GFS does not take any responsibility for any damage caused through use of these fonts, be it indirect, special, incidental or consequential damages (including damages for loss of business, loss of profits, interruption or the like).\
\
visit www.greekfontsociety.org\
\
\
________________________________________\
\
\pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx5600\tx6160\tx6720\sl300\ql\qnatural
\f1\b\fs22 \cf0 Greek Font Society
\f0\b0 \
\
33 S Merkouri Street\
116 34 Athens\
Greece\
T: +30 210 725 1979\
F: +30 210 725 1979\
E: gfs@greekfontsociety.org
\f2 \
}

File diff suppressed because it is too large Load Diff

BIN
img/CapaAnim.webp Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 878 KiB

BIN
img/CapaAnimP.webp Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 244 KiB

BIN
img/SFcor.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 71 KiB

BIN
img/anghipdes.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 22 KiB

BIN
img/anghippos.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 20 KiB

BIN
img/anghipuv.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

BIN
img/anghipuv2.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 22 KiB

BIN
img/anghipuv3.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 20 KiB

BIN
img/anghipuv4.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 18 KiB

BIN
img/anghipuv5.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 19 KiB

BIN
img/anghipuv6.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 22 KiB

BIN
img/angparidade.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 30 KiB

BIN
img/angperps.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 15 KiB

BIN
img/angposneg.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 22 KiB

BIN
img/angseccsc.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 19 KiB

BIN
img/angtgctg.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 19 KiB

BIN
img/anguv.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

BIN
img/anguv2.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

BIN
img/anguv3.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 20 KiB

BIN
img/areaint.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 40 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 111 KiB

BIN
img/capa.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 344 KiB

BIN
img/capa.webp Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 30 KiB

BIN
img/catenaria.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 24 KiB

BIN
img/cictrig.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 19 KiB

BIN
img/farccos.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 26 KiB

BIN
img/farccosh.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 59 KiB

BIN
img/farccsc.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 47 KiB

BIN
img/farccsch.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 50 KiB

BIN
img/farcctg.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 47 KiB

BIN
img/farcctgh.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 41 KiB

BIN
img/farcsec.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 63 KiB

BIN
img/farcsech.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 34 KiB

BIN
img/farcsin.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

BIN
img/farcsinh.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 64 KiB

BIN
img/farctan.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 48 KiB

BIN
img/farctgh.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 37 KiB

Some files were not shown because too many files have changed in this diff Show More