Click or drag to resize
ILocationMarker Interface
A location marker represents a persistent location in the bilingual content. It is often generated from LocationMark(LocationMarkerId) calls with associated native message reporter calls from native parsers, and content processors used during extraction. Location markers can also be used as general bookmarks.

Namespace: Sdl.FileTypeSupport.Framework.BilingualApi
Assembly: Sdl.FileTypeSupport.Framework.Core (in Sdl.FileTypeSupport.Framework.Core.dll) Version: 1.0.0.0 (1.0.2551.0)
Syntax
public interface ILocationMarker : IAbstractMarker, 
	IAbstractMarkupData, ICloneable

The ILocationMarker type exposes the following members.

Properties
  NameDescription
Public propertyIndexInParent
The index of this item in its parent container (if any).
(Inherited from IAbstractMarkupData.)
Public propertyMarkerId
The unique identifier for this location marker. Note that it may happen that content gets duplicated, e.g. from source to target in a paragraph unit, and that location markers in that case also get duplicated. Therefore, it is not possible to guarantee that location marker ids are unique throughout the document, but at least, in such cases, the two locations should be closely related.
Public propertyParent
When this item is inside a markup data container, this property provides access to the parent container.
(Inherited from IAbstractMarkupData.)
Public propertyParentParagraph
Convenient accessor to the source or target paragraph container that the item appears in.
(Inherited from IAbstractMarkupData.)
Top
Methods
  NameDescription
Public methodCode exampleAcceptVisitor
Part of the visitor pattern implementation for markup data. This method is overridden in each leaf implementation. The implementation should call the Visit... method on the visitor corresponding to their object type, passing themselves (i.e. this) as the parameter. Objects that contain other objects (e.g. implementations of ISegment or IOtherMarker) should NOT apply the visitor to their content items. It must be left to the visitor implementation to 'decide' whether the visitor 'wants' to visit the sub-items of a node.
(Inherited from IAbstractMarkupData.)
Public methodRemoveFromParent
Removes this node from its parent container (if any).
(Inherited from IAbstractMarkupData.)
Top
See Also
Community
Edit

Be the first to Edit the community content of this topic.
Comments