You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rupert Westenthaler (JIRA)" <ji...@apache.org> on 2014/05/21 12:07:38 UTC
[jira] [Resolved] (STANBOL-660) Stanbol Enhancer should allow to
manually parse the langage of the Content
[ https://issues.apache.org/jira/browse/STANBOL-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler resolved STANBOL-660.
-----------------------------------------
Resolution: Fixed
implemented with http://svn.apache.org/r1596518 in 0.12.1 and merged with http://svn.apache.org/r1596525 to trunk.
> Stanbol Enhancer should allow to manually parse the langage of the Content
> --------------------------------------------------------------------------
>
> Key: STANBOL-660
> URL: https://issues.apache.org/jira/browse/STANBOL-660
> Project: Stanbol
> Issue Type: New Feature
> Components: Enhancer
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
> Fix For: 1.0.0, 0.12.1
>
>
> This is important for very short texts where the detection of the language can fail.
> This will support using the Content-Language HTTP header to explicitly parse the language of the content.
> The parsed language will be set as
> {code}
> content-item-uri dc:language "content-language-value"
> {code}
> to the metadata of the ContentItem before parsing it to the Enhancement Chain
--
This message was sent by Atlassian JIRA
(v6.2#6252)