Translation of Event Tickets: Portuguese (Brazil)

1 2 3 4 5 … 244
Prio Original string Translation —
The sale price dates cannot be read. Enter a valid date for each specific date. You have to log in to add a translation. Details

The sale price dates cannot be read. Enter a valid date for each specific date.

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • src/Tickets/Relative_Sale_Dates/Window_Kind.php:371
Priority:
normal
More links:
The relative sale price dates cannot be read. Enter a whole number from %1$d to %2$d for each relative date. You have to log in to add a translation. Details

The relative sale price dates cannot be read. Enter a whole number from %1$d to %2$d for each relative date.

You have to log in to edit this translation.

Meta

Status:
untranslated
Comment:
translators: 1) the lowest number a relative sale price date takes, 2) the highest.
References:
  • src/Tickets/Relative_Sale_Dates/Window_Kind.php:364
Priority:
normal
More links:
Ticket sales cannot end before they start. Please adjust the sales window. You have to log in to add a translation. Details

Ticket sales cannot end before they start. Please adjust the sales window.

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • src/Tickets/Relative_Sale_Dates/Window_Kind.php:292
Priority:
normal
More links:
The sales dates cannot be read. Enter a valid date for each specific date. You have to log in to add a translation. Details

The sales dates cannot be read. Enter a valid date for each specific date.

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • src/Tickets/Relative_Sale_Dates/Window_Kind.php:288
Priority:
normal
More links:
The relative sales dates cannot be read. Enter a whole number from %1$d to %2$d for each relative date. You have to log in to add a translation. Details

The relative sales dates cannot be read. Enter a whole number from %1$d to %2$d for each relative date.

You have to log in to edit this translation.

Meta

Status:
untranslated
Comment:
translators: 1) the lowest number a relative sale date takes, 2) the highest.
References:
  • src/Tickets/Relative_Sale_Dates/Window_Kind.php:281
Priority:
normal
More links:
For a relative boundary, the unit in seconds: %1$d (minutes), %2$d (hours), %3$d (days) or %4$d (weeks). You have to log in to add a translation. Details

For a relative boundary, the unit in seconds: %1$d (minutes), %2$d (hours), %3$d (days) or %4$d (weeks).

You have to log in to edit this translation.

Meta

Status:
untranslated
Comment:
translators: 1) a minute, 2) an hour, 3) a day and 4) a week, each in seconds.
References:
  • src/Tickets/Relative_Sale_Dates/Rule_Parameter.php:227
Priority:
normal
More links:
For a relative boundary, the number of units before the anchor, from %1$d to %2$d. You have to log in to add a translation. Details

For a relative boundary, the number of units before the anchor, from %1$d to %2$d.

You have to log in to edit this translation.

Meta

Status:
untranslated
Comment:
translators: 1) the lowest number of units, 2) the highest number of units.
References:
  • src/Tickets/Relative_Sale_Dates/Rule_Parameter.php:221
Priority:
normal
More links:
When sales end. You have to log in to add a translation. Details

When sales end.

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • src/Tickets/Relative_Sale_Dates/Rule_Parameter.php:216
Priority:
normal
More links:
When sales start. You have to log in to add a translation. Details

When sales start.

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • src/Tickets/Relative_Sale_Dates/Rule_Parameter.php:215
Priority:
normal
More links:
The sales window relative to the event, or null when the ticket has fixed sale dates. Sending null removes the rule. While the rule keeps a relative or default boundary, a date sent for that boundary is replaced by the one the rule resolves to. You have to log in to add a translation. Details

The sales window relative to the event, or null when the ticket has fixed sale dates. Sending null removes the rule. While the rule keeps a relative or default boundary, a date sent for that boundary is replaced by the one the rule resolves to.

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • src/Tickets/Relative_Sale_Dates/Rule_Parameter.php:214
Priority:
normal
More links:
How this end of the window is set: `default` (sales open at once, or close when the event starts), `relative` (before the event) or `specific` (the date sent with the ticket). You have to log in to add a translation. Details

How this end of the window is set: `default` (sales open at once, or close when the event starts), `relative` (before the event) or `specific` (the date sent with the ticket).

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • src/Tickets/Relative_Sale_Dates/Rule_Parameter.php:211
Priority:
normal
More links:
For a relative boundary, the unit in seconds: %1$d (days) or %2$d (weeks). You have to log in to add a translation. Details

For a relative boundary, the unit in seconds: %1$d (days) or %2$d (weeks).

You have to log in to edit this translation.

Meta

Status:
untranslated
Comment:
translators: 1) a day and 2) a week, each in seconds.
References:
  • src/Tickets/Relative_Sale_Dates/Rule_Parameter.php:201
Priority:
normal
More links:
For a relative boundary, the number of units before the event start, from %1$d to %2$d. You have to log in to add a translation. Details

For a relative boundary, the number of units before the event start, from %1$d to %2$d.

You have to log in to edit this translation.

Meta

Status:
untranslated
Comment:
translators: 1) the lowest number of units, 2) the highest number of units.
References:
  • src/Tickets/Relative_Sale_Dates/Rule_Parameter.php:195
Priority:
normal
More links:
How the end is set: `relative` (before the event start) or `specific` (the date sent in `sale_price_end_date`). You have to log in to add a translation. Details

How the end is set: `relative` (before the event start) or `specific` (the date sent in `sale_price_end_date`).

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • src/Tickets/Relative_Sale_Dates/Rule_Parameter.php:192
Priority:
normal
More links:
How the start is set: `now` (as soon as ticket sales open), `relative` (before the event start) or `specific` (the date sent in `sale_price_start_date`). You have to log in to add a translation. Details

How the start is set: `now` (as soon as ticket sales open), `relative` (before the event start) or `specific` (the date sent in `sale_price_start_date`).

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • src/Tickets/Relative_Sale_Dates/Rule_Parameter.php:191
Priority:
normal
More links:
Legend:
Current
Waiting
Rejected
Fuzzy
Old
With warnings
1 2 3 4 5 … 244

Export as