<?xml version="1.0" encoding="utf-8"?>
<root>
  <!-- 
    Microsoft ResX Schema 
    
    Version 2.0
    
    The primary goals of this format is to allow a simple XML format 
    that is mostly human readable. The generation and parsing of the 
    various data types are done through the TypeConverter classes 
    associated with the data types.
    
    Example:
    
    ... ado.net/XML headers & schema ...
    <resheader name="resmimetype">text/microsoft-resx</resheader>
    <resheader name="version">2.0</resheader>
    <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
    <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
    <data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
    <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
    <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
        <value>[base64 mime encoded serialized .NET Framework object]</value>
    </data>
    <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
        <value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
        <comment>This is a comment</comment>
    </data>
                
    There are any number of "resheader" rows that contain simple 
    name/value pairs.
    
    Each data row contains a name, and value. The row also contains a 
    type or mimetype. Type corresponds to a .NET class that support 
    text/value conversion through the TypeConverter architecture. 
    Classes that don't support this are serialized and stored with the 
    mimetype set.
    
    The mimetype is used for serialized objects, and tells the 
    ResXResourceReader how to depersist the object. This is currently not 
    extensible. For a given mimetype the value must be set accordingly:
    
    Note - application/x-microsoft.net.object.binary.base64 is the format 
    that the ResXResourceWriter will generate, however the reader can 
    read any of the formats listed below.
    
    mimetype: application/x-microsoft.net.object.binary.base64
    value   : The object must be serialized with 
            : System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
            : and then encoded with base64 encoding.
    
    mimetype: application/x-microsoft.net.object.soap.base64
    value   : The object must be serialized with 
            : System.Runtime.Serialization.Formatters.Soap.SoapFormatter
            : and then encoded with base64 encoding.

    mimetype: application/x-microsoft.net.object.bytearray.base64
    value   : The object must be serialized into a byte array 
            : using a System.ComponentModel.TypeConverter
            : and then encoded with base64 encoding.
    -->
  <xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
    <xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
    <xsd:element name="root" msdata:IsDataSet="true">
      <xsd:complexType>
        <xsd:choice maxOccurs="unbounded">
          <xsd:element name="metadata">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" />
              </xsd:sequence>
              <xsd:attribute name="name" use="required" type="xsd:string" />
              <xsd:attribute name="type" type="xsd:string" />
              <xsd:attribute name="mimetype" type="xsd:string" />
              <xsd:attribute ref="xml:space" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="assembly">
            <xsd:complexType>
              <xsd:attribute name="alias" type="xsd:string" />
              <xsd:attribute name="name" type="xsd:string" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="data">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
                <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
              <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
              <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
              <xsd:attribute ref="xml:space" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="resheader">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" use="required" />
            </xsd:complexType>
          </xsd:element>
        </xsd:choice>
      </xsd:complexType>
    </xsd:element>
  </xsd:schema>
  <resheader name="resmimetype">
    <value>text/microsoft-resx</value>
  </resheader>
  <resheader name="version">
    <value>2.0</value>
  </resheader>
  <resheader name="reader">
    <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <resheader name="writer">
    <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <data name="ActiveMyPacenoteCreationTime_Tooltip" xml:space="preserve">
    <value>Creation timestamp of the active custom pacenote</value>
  </data>
  <data name="ActiveMyPacenoteExtension_Tooltip" xml:space="preserve">
    <value>Name of the pacenote extension.

The pacenote extension and range options are set in PaceNote plugin while editing pacenotes</value>
  </data>
  <data name="ActiveMyPacenoteFilename_Tooltip" xml:space="preserve">
    <value>The active MyPacenote for this stage.

default = The default pacenotes for the map
latest = The latest available MyPacenote (RBR uses automatically the version with the latest timestamp)
other name = The specific selected MyPacenote version from the list of available pacenotes</value>
    <comment>Tooltip of the active selected pacenote filename item</comment>
  </data>
  <data name="ActiveMyPacenoteRange_Tooltip" xml:space="preserve">
    <value>Name of the pacenote range option (an option in PaceNote plugin)</value>
  </data>
  <data name="Available_pacenotes" xml:space="preserve">
    <value>Available pacenotes</value>
  </data>
  <data name="Differentiate" xml:space="preserve">
    <value>Differentiate</value>
    <comment>Name of the "Differentiate pacenotes per M/N/E/O" option</comment>
  </data>
  <data name="Differentiate_Tooltip" xml:space="preserve">
    <value>Differentiate MyPacenotes by the type of stage (M-Morning, N-Noon, E-Evening, O-Overcast)

If you are unsure if you need these options then you probably don't need to enable these options.

Very few stages have a different track layout or objects in morning/noon/evening/overcast settings. 
A stage called "Gestel I" is one rare case with different road side objects in O stage settings</value>
    <comment>Tooltip of differentiate options</comment>
  </data>
  <data name="MyPacenotes_Info_Tooltip" xml:space="preserve">
    <value>When MyPacenote is enabled then all pacenotes are stored and loaded from MyPacenote storage folder.
Select a stage from the list and then choose the active note from the list of available pacenotes (default, the latest custom note).
If a stage is not listed here then start it at least once in RSF plugin.

RBR co-driver uses the selected MyPacenote automatically each time a stage is started. Pacenote changes are also autosaved.

Pro tip: You can set the MyPacenote root path option to a folder synchronized by a cloud storage service
and this way your custom pacenotes are automatically preserved in your personal cloud drive</value>
    <comment>Tooltip in "?" icon in MyPacenotes page</comment>
  </data>
  <data name="MyPacenotes_Path_Tooltip" xml:space="preserve">
    <value>Root path where MyPacenotes files are stored. The default path is Plugins\NGPCarMenu\MyPacenotes.

If a stage is not shown here then start the stage in RBR at least once in RSF plugin</value>
  </data>
  <data name="MyPacenotes_Path_Watermark" xml:space="preserve">
    <value>Path to MyPacenotes root folder</value>
    <comment>Watermark text shown when MyPacenotes path value is empty</comment>
  </data>
  <data name="OpenFolder_Tooltip" xml:space="preserve">
    <value>Open MyPacenotes folder of the selected stage in FileExplorer</value>
    <comment>Tooltip of Open MyPacenotes folder button</comment>
  </data>
  <data name="RBRRoadbook_Recommendation" xml:space="preserve">
    <value>Recommended by RSF. RBR Roadbook app (by Mister Arek)
is an easy and powerful tool to create and modify own pacenotes</value>
    <comment>RBR Roadbook app recommendation text shown in MyPacenotes page</comment>
  </data>
  <data name="RefreshFolder_Tooltip" xml:space="preserve">
    <value>Refresh the stage list to show new MyPacenote stages and notes</value>
    <comment>Tooltip of Refresh MyPacenotes button</comment>
  </data>
  <data name="Use_MyPacenotes" xml:space="preserve">
    <value>Use MyPacenotes</value>
    <comment>An option in MyPacenotes page</comment>
  </data>
  <data name="Use_MyPacenotes_Tooltip" xml:space="preserve">
    <value>The MyPacenote feature of NGPCarMenu plugin stores pacenotes in your personal MyPacenote folder.

This makes it easier to edit pacenotes and own custom notes are not lost when a stage is updated or re-installed.
Pacenote changes are also autosaved and the MyPacenote selection here is automatically used when a stage is restarted in RBR</value>
    <comment>Tooltip of the "Use MyPacenotes" option</comment>
  </data>
</root>