Translation
SeedCodeCalendar12.Translation History
Hide minor edits - Show changes to output
Changed line 57 from:
-> Two scripts in the calendar use the English word "Done" when working with the To-Do list and if you're using To-Dos you'll want to edit those to use your own version of that word. Edit the script "Mark Done", where it's usage is pretty obvious. Then edit the script "Capture Events by Date Range - Run SQL Query" where you'll see a comment early in the script where you can change the word "Done" in our SQL queries.
to:
-> Two scripts in the calendar use the English word "Done" when working with the To-Do list and if you're using To-Dos you'll want to edit those to use your own version of that word. Edit the script "Mark Done", where its usage is pretty obvious. Then edit the script "Capture Events by Date Range - Run SQL Query" where you'll see a comment early in the script where you can change the word "Done" in our SQL queries.
Changed lines 52-57 from:
-> The phrase "All Day" on the Week and Schedule screens can be found in the field CalendarRows::TimeDisplayMinutesCalc.
to:
-> The phrase "All Day" on the Week and Schedule screens can be found in the field CalendarRows::TimeDisplayMinutesCalc.
''''Done'''
-> Two scripts in the calendar use the English word "Done" when working with the To-Do list and if you're using To-Dos you'll want to edit those to use your own version of that word. Edit the script "Mark Done", where it's usage is pretty obvious. Then edit the script "Capture Events by Date Range - Run SQL Query" where you'll see a comment early in the script where you can change the word "Done" in our SQL queries.
''''Done'''
-> Two scripts in the calendar use the English word "Done" when working with the To-Do list and if you're using To-Dos you'll want to edit those to use your own version of that word. Edit the script "Mark Done", where it's usage is pretty obvious. Then edit the script "Capture Events by Date Range - Run SQL Query" where you'll see a comment early in the script where you can change the word "Done" in our SQL queries.
Added lines 47-49:
-> Some of the time formats (the ones on the month view for example) can be switched to 24 hour format using a simple setting in one of our scripts (it is in the script "Format Event Time --- Edit Time Formats for Events Here ---" but others (like the times shown in the left hand column on the schedule screen) will need to be changed in layout mode.
Changed line 49 from:
The phrase "All Day" on the Week and Schedule screens can be found in the field CalendarRows::TimeDisplayMinutesCalc.
to:
-> The phrase "All Day" on the Week and Schedule screens can be found in the field CalendarRows::TimeDisplayMinutesCalc.
Changed lines 34-35 from:
CalendarInterface::NinjaCal_year \\
to:
CalendarInterface::NinjaCal_year
Added lines 36-42:
--> Scripts... \\
Go to Calendar Tab ( Tab Name ) \\
Load Calendar Layout \\
Go to Day \\
Go to Week \\
Insert into Calendar { Column } \\
Go to Calendar Tab ( Tab Name ) \\
Load Calendar Layout \\
Go to Day \\
Go to Week \\
Insert into Calendar { Column } \\
Changed line 31 from:
CalendarInterface::DateDisplayCalc \\
to:
--> CalendarInterface::DateDisplayCalc \\
Changed lines 25-42 from:
-> Changing the Yes No value list from "Yes" and "No" to another language is actually the trickiest part of the translation, since so many calcs and scripts use these values. Once you change the value list you'll need to replace "Yes" and "No" in the following scripts and calculations:
to:
-> Changing the Yes No value list from "Yes" and "No" to another language is actually the trickiest part of the translation, since so many calcs and scripts use these values. Once you change the value list you'll need to replace "Yes" and "No" in the following scripts and calculations:
--> Calcs... \\
CalendarRows::DateRangeStartAutoGlob \\
CalendarRows::WeekNumbersDisplayCalc \\
CalendarInterface::DateDisplayCalc \\
CalendarInterface::NinjaCal_triple \\
CalendarInterface::NinjaCal_basic \\
CalendarInterface::NinjaCal_year \\
'''Time Increments'''
-> The value list "Calendar Time Scale" includes a few English phrases you might want to replace, fortunately if you also edit a couple of fields the software has already abstracted these values. Translate the Engish values in the field CalendarInterface::TimeIncrementAutoGlob and then edit CalendarInterface::TimeScaleGlob. In this second field, only translate the IF() part of the calcs, not the result, leaving "day" in lower case towards the end of the calc.
'''All Day'''
The phrase "All Day" on the Week and Schedule screens can be found in the field CalendarRows::TimeDisplayMinutesCalc.
--> Calcs... \\
CalendarRows::DateRangeStartAutoGlob \\
CalendarRows::WeekNumbersDisplayCalc \\
CalendarInterface::DateDisplayCalc \\
CalendarInterface::NinjaCal_triple \\
CalendarInterface::NinjaCal_basic \\
CalendarInterface::NinjaCal_year \\
'''Time Increments'''
-> The value list "Calendar Time Scale" includes a few English phrases you might want to replace, fortunately if you also edit a couple of fields the software has already abstracted these values. Translate the Engish values in the field CalendarInterface::TimeIncrementAutoGlob and then edit CalendarInterface::TimeScaleGlob. In this second field, only translate the IF() part of the calcs, not the result, leaving "day" in lower case towards the end of the calc.
'''All Day'''
The phrase "All Day" on the Week and Schedule screens can be found in the field CalendarRows::TimeDisplayMinutesCalc.
Changed lines 23-24 from:
''Yes and No value list'''
to:
'''Yes and No value list'''
Changed lines 21-25 from:
-> You'll do the same with the month names on the repeat Yearly tab.
to:
-> You'll do the same with the month names on the repeat Yearly tab.
''Yes and No value list'''
-> Changing the Yes No value list from "Yes" and "No" to another language is actually the trickiest part of the translation, since so many calcs and scripts use these values. Once you change the value list you'll need to replace "Yes" and "No" in the following scripts and calculations:
''Yes and No value list'''
-> Changing the Yes No value list from "Yes" and "No" to another language is actually the trickiest part of the translation, since so many calcs and scripts use these values. Once you change the value list you'll need to replace "Yes" and "No" in the following scripts and calculations:
Deleted lines 8-15:
->The Repeat Options layout shows 4 tabs where users select the frequency with which they'd like an event to repeat. In a few tabs we refer to day names in English; you'll want to change the day names on the layout, keeping the day names in the same order as they already are. Then change the conditional formatting for each day name, replacing "Self" with the now translated name of the day, like this:
--> not IsEmpty ( FilterValues ( $$sc_Repeat_DayOfWeek ; "Ludi" ) )
-> You'll do the same with the month names on the repeat Yearly tab.
Changed lines 15-21 from:
-> The Repeat Options layout contains tab names and text (like the names of days and months) you may wish to translate. Drag the orange tab at the top of the screen out of the way to reveal the "real" FileMaker tabs below, and you can then navigate to the weekly, monthly, and yearly tabs to translate their contents. The day and month names are just text on the layout so you can edit these with the text tool: do NOT change the script parameters being sent from these buttons. These script parameters should always use the English names of days and months: your users will never see these.
to:
-> The Repeat Options layout contains tab names and text (like the names of days and months) you may wish to translate. Drag the orange tab at the top of the screen out of the way to reveal the "real" FileMaker tabs below, and you can then navigate to the weekly, monthly, and yearly tabs to translate their contents. The day and month names are just text on the layout so you can edit these with the text tool: do NOT change the script parameters being sent from these buttons. These script parameters should always use the English names of days and months: your users will never see these.
-> You'll want to change the conditional formatting for each day name, replacing "Self" with the now English name of the day, like this:
--> not IsEmpty ( FilterValues ( $$sc_Repeat_DayOfWeek ; "Monday" ) )
-> You'll do the same with the month names on the repeat Yearly tab.
-> You'll want to change the conditional formatting for each day name, replacing "Self" with the now English name of the day, like this:
--> not IsEmpty ( FilterValues ( $$sc_Repeat_DayOfWeek ; "Monday" ) )
-> You'll do the same with the month names on the repeat Yearly tab.
Changed lines 19-23 from:
-> You can rename most layouts once you've integrated the solution into your file. The exceptions are the "Source No X" layouts. Don't rename those, just take them out of the layout menu. And if you rename the "calendar" layouts, edit the script "Go to Calendar Layout" to reflect your changes.
to:
-> You can rename most layouts once you've integrated the solution into your file. The exceptions are the "Source No X" layouts. Don't rename those, just take them out of the layout menu. And if you rename the "calendar" layouts, edit the script "Go to Calendar Layout" to reflect your changes.
'''Repeat Options'''
-> The Repeat Options layout contains tab names and text (like the names of days and months) you may wish to translate. Drag the orange tab at the top of the screen out of the way to reveal the "real" FileMaker tabs below, and you can then navigate to the weekly, monthly, and yearly tabs to translate their contents. The day and month names are just text on the layout so you can edit these with the text tool: do NOT change the script parameters being sent from these buttons. These script parameters should always use the English names of days and months: your users will never see these.
'''Repeat Options'''
-> The Repeat Options layout contains tab names and text (like the names of days and months) you may wish to translate. Drag the orange tab at the top of the screen out of the way to reveal the "real" FileMaker tabs below, and you can then navigate to the weekly, monthly, and yearly tabs to translate their contents. The day and month names are just text on the layout so you can edit these with the text tool: do NOT change the script parameters being sent from these buttons. These script parameters should always use the English names of days and months: your users will never see these.
Changed lines 15-19 from:
-> You'll do the same with the month names on the repeat Yearly tab.
to:
-> You'll do the same with the month names on the repeat Yearly tab.
'''Layouts''''
-> You can rename most layouts once you've integrated the solution into your file. The exceptions are the "Source No X" layouts. Don't rename those, just take them out of the layout menu. And if you rename the "calendar" layouts, edit the script "Go to Calendar Layout" to reflect your changes.
'''Layouts''''
-> You can rename most layouts once you've integrated the solution into your file. The exceptions are the "Source No X" layouts. Don't rename those, just take them out of the layout menu. And if you rename the "calendar" layouts, edit the script "Go to Calendar Layout" to reflect your changes.
Added line 15:
-> You'll do the same with the month names on the repeat Yearly tab.
