LRM JSON Support - Revision history

Llawson: /* Sample LRM Project Definition File for .json */

2017-09-18T20:26:27Z

Sample LRM Project Definition File for .json

@@ Line 119: / Line 119: @@
    "key1": true
-== Sample LRM Project Definition File for .json ==
+== Example of Project Definition for Resources ==
- <?xml version="1.0" encoding="UTF-8" standalone="no"?>
+The following is an example of json resource file definitions. See [[Supported_Resource_Bundles#Resource_Extensions| resource extensions]] for more information.
- <lrmconf>
    <resource-extensions>
      <resource-extension>
@@ Line 164: / Line 147: @@
      </resource-extension>
    </resource-extensions>

Llawson: /* .json uses the json parser type */

2017-09-01T15:48:37Z

.json uses the json parser type

← Older revision		Revision as of 15:48, 1 September 2017
Line 84:		Line 84:

	=== .json uses the ''json'' parser type===		=== .json uses the ''json'' parser type===
	When defining a project ~~with~~ .json ~~extension~~, there is no need to define a ''<parser-type>'' as the ''json'' parser will always be used.		When defining a project containing LRM Standard .json resource files, there is no need to define a ''<parser-type>'' as the ''json'' parser will always be used.

	=== unique file extension needs to define ''json'' parser type ===		=== unique file extension needs to define ''json'' parser type ===
	If a unique file extension is a valid json file, then the ''<parser-type>'' should be ''json'' in the project definition file.		If a unique file extension is a valid json file, then the ''<parser-type>'' should be ''json'' in the project definition file.

Llawson: /* valid json syntax */

2017-08-31T23:19:37Z

valid json syntax

← Older revision		Revision as of 23:19, 31 August 2017
Line 81:		Line 81:
	== ''json'' parser type ==		== ''json'' parser type ==
	=== valid json syntax ===		=== valid json syntax ===
	Files that use the ''json'' are expected to have valid json syntax		Files that use the ''json'' parser are expected to have valid json syntax

	=== .json uses the ''json'' parser type===		=== .json uses the ''json'' parser type===
	When defining a project with .json extension, there is no need to define a ''<parser-type>'' as the ''json'' parser will always be used.		When defining a project with .json extension, there is no need to define a ''<parser-type>'' as the ''json'' parser will always be used.

Llawson: /* unique file extension needs to define json parser type */

2017-08-31T23:15:59Z

unique file extension needs to define json parser type

← Older revision		Revision as of 23:15, 31 August 2017
Line 85:		Line 85:
	When defining a project with .json extension, there is no need to define a ''<parser-type>'' as the ''json'' parser will always be used.		When defining a project with .json extension, there is no need to define a ''<parser-type>'' as the ''json'' parser will always be used.
	=== unique file extension needs to define ''json'' parser type ===		=== unique file extension needs to define ''json'' parser type ===
	If a unique file extension is a valid json file, then the ''<parser-type>'' should be ''json''		If a unique file extension is a valid json file, then the ''<parser-type>'' should be ''json'' in the project definition file.

	== In what format should JSON Files or files extensions using the ''json'' parser type be for LRM Handling ?==		== In what format should JSON Files or files extensions using the ''json'' parser type be for LRM Handling ?==

Llawson: /* In what format should JSON Files or files extensions using the json parser type be for LRM Handling ? */

2017-08-31T23:09:23Z

In what format should JSON Files or files extensions using the json parser type be for LRM Handling ?

← Older revision		Revision as of 23:09, 31 August 2017
Line 78:		Line 78:
	<b>Caveat</b>		<b>Caveat</b>
	JSON structure changes can lead to problems with project on-boarded for file deltas (v. Full Files).		JSON structure changes can lead to problems with project on-boarded for file deltas (v. Full Files).

			== ''json'' parser type ==
			=== valid json syntax ===
			Files that use the ''json'' are expected to have valid json syntax
			=== .json uses the ''json'' parser type===
			When defining a project with .json extension, there is no need to define a ''<parser-type>'' as the ''json'' parser will always be used.
			=== unique file extension needs to define ''json'' parser type ===
			If a unique file extension is a valid json file, then the ''<parser-type>'' should be ''json''

	== In what format should JSON Files or files extensions using the ''json'' parser type be for LRM Handling ?==		== In what format should JSON Files or files extensions using the ''json'' parser type be for LRM Handling ?==

Llawson: /* Sample LRM Project Definition File for .json */

2017-08-31T21:00:24Z

Sample LRM Project Definition File for .json

← Older revision		Revision as of 21:00, 31 August 2017
Line 142:		Line 142:
	</resource-extension>		</resource-extension>
	<resource-extension>		<resource-extension>
	'''''<!-- parser-type is required ~~since~~ .myext is not a standard LRM extension -->'''''		'''''<!-- parser-type is required because .myext is not a standard LRM extension -->'''''
	'''<extension>''myext''</extension>'''		'''<extension>''myext''</extension>'''
	'''''<parser-type>json</parser-type>'''''		'''''<parser-type>json</parser-type>'''''

Llawson: /* Sample LRM Project Definition File for .json */

2017-08-31T20:57:07Z

Sample LRM Project Definition File for .json

← Older revision		Revision as of 20:57, 31 August 2017
Line 131:		Line 131:
	<resource-extensions>		<resource-extensions>
	<resource-extension>		<resource-extension>
			'''<!-- parser-type not needed since .json is a standard LRM extension that maps to the json parser type -->'''
	'''<extension>json</extension>'''		'''<extension>json</extension>'''
	'''<file-name-pattern>*_l-c-v</file-name-pattern>'''		'''<file-name-pattern>*_l-c-v</file-name-pattern>'''
Line 141:		Line 142:
	</resource-extension>		</resource-extension>
	<resource-extension>		<resource-extension>
			'''''<!-- parser-type is required since .myext is not a standard LRM extension -->'''''
	'''<extension>''myext''</extension>'''		'''<extension>''myext''</extension>'''
	'''''<parser-type>json</parser-type>'''''		'''''<parser-type>json</parser-type>'''''

Llawson: /* Sample LRM Project Definition File for .json */

2017-08-31T20:43:15Z

Sample LRM Project Definition File for .json

← Older revision		Revision as of 20:43, 31 August 2017
Line 154:		Line 154:
	<dirset>		<dirset>
	<includes>		<includes>
	<include-dir>/src/</include-dir>		<include-dir-file>/src/</include-dir-file>
	</includes>		</includes>
	<excludes>		<excludes>

Llawson: /* In what format should JSON Files be for LRM Handling ? */

2017-08-31T20:23:11Z

In what format should JSON Files be for LRM Handling ?

← Older revision		Revision as of 20:23, 31 August 2017
Line 79:		Line 79:
	JSON structure changes can lead to problems with project on-boarded for file deltas (v. Full Files).		JSON structure changes can lead to problems with project on-boarded for file deltas (v. Full Files).

	== In what format should JSON Files be for LRM Handling ?==		== In what format should JSON Files or files extensions using the ''json'' parser type be for LRM Handling ?==

	===Arrays are not allowed in the context of JSON files as resource bundles===		===Arrays are not allowed in the context of JSON files as resource bundles===

Llawson: /* Example of JSON files or file extensions using the json parser type */

2017-08-31T20:22:16Z

Example of JSON files or file extensions using the json parser type

← Older revision		Revision as of 20:22, 31 August 2017
Line 1:		Line 1:
	LRM supports those .json files which makes sense for translation. Not all .json files do. The JSON extension as well as file extensions using the json parser type are supported in Lingoport Resource Manager (LRM). Well-formed JSON is required and specified by http://www.ietf.org/rfc/rfc4627.txt. In order to detect and import changes,		LRM supports those .json files which makes sense for translation. Not all .json files do. The JSON extension as well as file extensions using the json parser type are supported in Lingoport Resource Manager (LRM). Well-formed JSON is required and specified by http://www.ietf.org/rfc/rfc4627.txt. In order to detect and import changes,

	== Example of JSON files or file extensions using the json parser type ==		== Example of JSON files or file extensions using the ''json'' parser type ==
	'''Simple JSON object'''		'''Simple JSON object'''
	{		{