Work-Related/events
Work-Related/events
1
0
mirror of https://github.com/werkraum-media/events.git synced 2024-11-13 02:36:10 +01:00
Code Issues Activity
events/Resources/Private/Language/locallang_csh_event.xlf

111 lines
4.8 KiB
Text
Raw Normal View History

Add CI * Add first basic CI with defaults. * Add ecs for coding guideline. * Fix invalid xliff files.
2021-09-07 09:03:02 +02:00
<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2">
<file source-language="en" datatype="plaintext" original="messages" date="2021-09-07T09:15:42Z" product-name="Events">
Add pages to events Allow editor to reference TYPO3 page records from events. E.g. used to provide further internal information links. Also those pages are resolved via DataProcessing. That allows integrators to be 100% flexible to resolve those page info. By default a menu is generated and media is resolved. Also validation is ignored, as this improves performance and allows to use the new class as injected property without validation fails. Models are not managed via frontend and therefore don't need validation. Relates: #8092
2021-01-11 09:20:51 +01:00
<header/>
<body>
<trans-unit id="tx_events.name">
<source>Events</source>
</trans-unit>
<trans-unit id="tx_events.description">
<source>Event Modul</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event">
<source>Event</source>
</trans-unit>
Restructure event TCA
2021-02-11 13:13:05 +01:00
<trans-unit id="tx_events_domain_model_event.tabs.text">
<source>Text</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event.tabs.dates">
<source>Dates</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event.tabs.location">
<source>Location</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event.tabs.relations">
<source>Relations</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event.tabs.media">
<source>Media</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event.tabs.social">
<source>Social Media</source>
</trans-unit>
Add source while importing from Destination Data One (#37) Destination Data One provides an source info explaining where the data originally came from. This is now added to event records and exposed in TYPO3 backend. That allows editors to check the source and contact corresponding sources in order to fix broken data. Relates: #10630
2023-08-10 15:02:05 +02:00
<trans-unit id="tx_events_domain_model_event.palette.source">
<source>Source</source>
</trans-unit>
Add pages to events Allow editor to reference TYPO3 page records from events. E.g. used to provide further internal information links. Also those pages are resolved via DataProcessing. That allows integrators to be 100% flexible to resolve those page info. By default a menu is generated and media is resolved. Also validation is ignored, as this improves performance and allows to use the new class as injected property without validation fails. Models are not managed via frontend and therefore don't need validation. Relates: #8092
2021-01-11 09:20:51 +01:00
<trans-unit id="tx_events_domain_model_event.title">
<source>Title</source>
</trans-unit>
Add subtitle filed to event
2021-02-15 09:58:51 +01:00
<trans-unit id="tx_events_domain_model_event.subtitle">
<source>Subtitle</source>
</trans-unit>
Add pages to events Allow editor to reference TYPO3 page records from events. E.g. used to provide further internal information links. Also those pages are resolved via DataProcessing. That allows integrators to be 100% flexible to resolve those page info. By default a menu is generated and media is resolved. Also validation is ignored, as this improves performance and allows to use the new class as injected property without validation fails. Models are not managed via frontend and therefore don't need validation. Relates: #8092
2021-01-11 09:20:51 +01:00
<trans-unit id="tx_events_domain_model_event.global_id">
<source>Global UID</source>
</trans-unit>
Add source while importing from Destination Data One (#37) Destination Data One provides an source info explaining where the data originally came from. This is now added to event records and exposed in TYPO3 backend. That allows editors to check the source and contact corresponding sources in order to fix broken data. Relates: #10630
2023-08-10 15:02:05 +02:00
<trans-unit id="tx_events_domain_model_event.source_name">
<source>Source Name</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event.source_url">
<source>Source URL</source>
</trans-unit>
Add pages to events Allow editor to reference TYPO3 page records from events. E.g. used to provide further internal information links. Also those pages are resolved via DataProcessing. That allows integrators to be 100% flexible to resolve those page info. By default a menu is generated and media is resolved. Also validation is ignored, as this improves performance and allows to use the new class as injected property without validation fails. Models are not managed via frontend and therefore don't need validation. Relates: #8092
2021-01-11 09:20:51 +01:00
<trans-unit id="tx_events_domain_model_event.slug">
<source>Slug</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event.highlight">
<source>Highlight</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event.teaser">
<source>Teaser</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event.details">
<source>Details</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event.price_info">
<source>Price Info</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event.web">
<source>Web</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event.ticket">
<source>Ticket</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event.facebook">
<source>Facebook</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event.youtube">
<source>Youtube</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event.instagram">
<source>Instagram</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event.images">
<source>Images</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event.pages">
<source>Pages</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event.categories">
<source>Categories</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event.dates">
<source>Dates</source>
</trans-unit>
Add location as separate record
2022-08-02 15:56:18 +02:00
<trans-unit id="tx_events_domain_model_event.location">
<source>Location</source>
</trans-unit>
Add pages to events Allow editor to reference TYPO3 page records from events. E.g. used to provide further internal information links. Also those pages are resolved via DataProcessing. That allows integrators to be 100% flexible to resolve those page info. By default a menu is generated and media is resolved. Also validation is ignored, as this improves performance and allows to use the new class as injected property without validation fails. Models are not managed via frontend and therefore don't need validation. Relates: #8092
2021-01-11 09:20:51 +01:00
<trans-unit id="tx_events_domain_model_event.organizer">
<source>Organizer</source>
</trans-unit>
<trans-unit id="tx_events_domain_model_event.region">
<source>Region</source>
</trans-unit>
Add partner Add new record type partner. This can be something like a media partner or something else. Allow an event to have zero or more partner. Add necessary files and models with relations. Relates: #8092
2021-01-11 10:15:21 +01:00
<trans-unit id="tx_events_domain_model_event.partner">
<source>Partner</source>
</trans-unit>
Allow to reference events from event This might be useful to allow editors and integrators to create something like "you might also be interested in" or "related events".
2021-07-13 09:31:01 +02:00
<trans-unit id="tx_events_domain_model_event.references_events">
<source>Related Events</source>
</trans-unit>
Add pages to events Allow editor to reference TYPO3 page records from events. E.g. used to provide further internal information links. Also those pages are resolved via DataProcessing. That allows integrators to be 100% flexible to resolve those page info. By default a menu is generated and media is resolved. Also validation is ignored, as this improves performance and allows to use the new class as injected property without validation fails. Models are not managed via frontend and therefore don't need validation. Relates: #8092
2021-01-11 09:20:51 +01:00
</body>
</file>
Cleanup localization
2020-10-01 16:35:34 +02:00
</xliff>
Copy permalink