.message-sources {
    margin-top: 0.75rem;
    padding-top: 0.75rem;
    border-top: 1px solid #ebecf0;
}

.message-sources h6 {
    font-size: 0.75rem;
    color: #6b778c;
    margin-bottom: 0.5rem;
    text-transform: uppercase;
    letter-spacing: 0.05em;
    font-weight: 600;
}

.source-list {
    list-style: none;
    padding: 0;
    margin: 0;
    display: flex;

-2,.px-2{padding-right:.5rem!important}.pb-2,.py-2{padding-bottom:.5rem!important}.pl-2,.px-2{padding-left:.5rem!important}.p-3{padding:1rem!important}.pt-3,.py-3{padding-top:1rem!important}.pr-3,.px-3{padding-right:1rem!important}.pb-3,.py-3{padding-bottom:1rem!important}.pl-3,.px-3{padding-left:1rem!important}.p-4{padding:1.5rem!important}.pt-4,.py-4{padding-top:1.5rem!important}.pr-4,.px-4{padding-right:1.5rem!important}.pb-4,.py-4{padding-bottom:1.5rem!important}.pl-4,.px-4{padding-left:1.5r...

labels.advance_search_filetype_excel=MS Excel
labels.advance_search_filetype_powerpoint=MS PowerPoint
labels.advance_search_occt=Cerca in
labels.advance_search_occt_default=Intera pagina
labels.advance_search_occt_allintitle=Titolo della pagina
labels.advance_search_occt_allinurl=URL della pagina
labels.advance_search_sitesearch=Sito o dominio
labels.advance_search_timestamp=Data di aggiornamento
labels.advance_search_timestamp_default=Qualsiasi data

/* Override some defaults */

html {
	min-height: 100%;
	position: relative;
}

body {
	padding: 1em 0;
	margin: 56px 0 4em;
}

footer {
	width: 100%;
	bottom: 0;
	height: 4em;
	position: absolute;
	border-top: 1px solid;
	padding-top: 1em;
}

h1,
h2,
h3 {
	line-height: 32px;
}

h1 {
	font-size: 30px;
}

h2 {
	font-size: 24px;
}

h3 {
	font-size: 18px;
}

This can save everyone a lot of time and frustration.

For any non-trivial change, we need to be able to answer these questions:

* Why is this change done? What's the use case?
* For user-facing features, what will the API look like?
* What test cases should it have? What could go wrong?
* How will it roughly be implemented? We'll happily provide code pointers to save you time.

labels.advance_search_filetype_excel=MS Excel
labels.advance_search_filetype_powerpoint=MS PowerPoint
labels.advance_search_occt=Buscar en
labels.advance_search_occt_default=Página completa
labels.advance_search_occt_allintitle=Título de la página
labels.advance_search_occt_allinurl=URL de la página
labels.advance_search_sitesearch=Sitio o dominio
labels.advance_search_timestamp=Fecha de actualización
labels.advance_search_timestamp_default=Cualquier fecha

Properties for documents:
o documentMap.dfprop

Properties for non-functional adjustments:
o sourceCopyright.dfprop
o infraMap.dfprop (manual making)

Properties for plug-ins:
o freeGenMap.dfprop (manual making)
o lastafluteMap.dfprop (manual making)

labels.advance_search_filetype_excel=MS Excel
labels.advance_search_filetype_powerpoint=MS PowerPoint
labels.advance_search_occt=Pesquisar em
labels.advance_search_occt_default=Página inteira
labels.advance_search_occt_allintitle=Título da página
labels.advance_search_occt_allinurl=URL da página
labels.advance_search_sitesearch=Site ou domínio
labels.advance_search_timestamp=Data de atualização
labels.advance_search_timestamp_default=Qualquer data

        // Test the specific field naming configuration
        JsonMappingOption option = provider.provideMappingOption();

        // The option should be configured with CAMEL_TO_LOWER_SNAKE
        // Field naming is now provided as OptionalThing
        OptionalThing<JsonFieldNaming> fieldNamingOpt = option.getFieldNaming();
        assertTrue("Field naming should be present", fieldNamingOpt.isPresent());

## Decision

The Gradle project adopts **American English** as the standard language variant for all code, comments, documentation, user-facing messages, and written communication.

### Examples

Use American English spelling, for example:

* `color` (not `colour`)
* `initialize` (not `initialise`)
* `behavior` (not `behaviour`)