Search results
Jump to navigation
Jump to search
Page title matches
- ...se uses have different requirements for corpora, and a number of different formats for storing such corpora have sprung up. Some examples include:5 KB (813 words) - 00:08, 28 December 2011
- [[Category:Ideas for Google Summer of Code|Plain-text formats for Apertium data]]2 KB (324 words) - 11:37, 16 February 2016
- I’m planning to do the proposed idea: “Plain-text formats for Apertium data”.6 KB (1,035 words) - 17:12, 3 May 2013
- [[Category:Ideas for Google Summer of Code|Unify the metadix formats]]1 KB (243 words) - 11:47, 14 February 2014
- Unify the Metadix Formats This variation is getting more complex and the different metadix formats are kind of depend on the developer of the language pair.13 KB (2,203 words) - 19:23, 28 March 2014
- Plain-text formats for Apertium data ..., It is good to see the Coding Challenge for the Project Unify the Metadix Formats, I have already attempted that coding challenge. Available on the Github. [12 KB (1,985 words) - 14:22, 21 March 2014
- 26 members (1 subcategory, 0 files) - 10:37, 3 September 2011
- =2011/04/05 #3: Supporting open formats on the mailing list= ...rt free/open-source software, we should take a stand by only allowing open formats on the mailing list.2 KB (237 words) - 22:19, 3 August 2013
- #REDIRECT [[PMC proposals/Supporting open formats on the mailing list]]71 bytes (10 words) - 08:20, 19 July 2011
Page text matches
- == Official formats carried out by Apertium == ...ng gettext]] and [[Translating subtitles]] for very simple solutions. More formats at [[Tips for translators]].13 KB (1,781 words) - 09:49, 6 October 2014
- Unify the Metadix Formats This variation is getting more complex and the different metadix formats are kind of depend on the developer of the language pair.13 KB (2,203 words) - 19:23, 28 March 2014
- ...) || Apertium structural transfer rules are currently encoded in XML-based formats. These are very overt and clear, but clumsy and may be hard to write. The i !colspan=4 style="background-color: #cdcdcd"|'''Unify the metadix formats'''71 KB (10,374 words) - 21:14, 18 January 2021
- == Formats officiellement supportés par Apertium == ...construction supportant les fichiers '''gettext''' <code>.po</code> ou les formats de sous-titres, mais voir [[Traduction des fichiers gettext]] et [[Traducti12 KB (1,757 words) - 09:51, 6 October 2014
- Plain-text formats for Apertium data ..., It is good to see the Coding Challenge for the Project Unify the Metadix Formats, I have already attempted that coding challenge. Available on the Github. [12 KB (1,985 words) - 14:22, 21 March 2014
- =2011/04/05 #3: Supporting open formats on the mailing list= ...rt free/open-source software, we should take a stand by only allowing open formats on the mailing list.2 KB (237 words) - 22:19, 3 August 2013
- To start with two formats, along with plain text, are supported, that is RTF and HTML. This also keeps the same objects and formats. The stages as as follows:58 KB (8,964 words) - 11:11, 14 May 2016
- ...mirroring that of Apertium's "lt-proc", but which loads transducers in the formats supported by HFST. The lookup tool tokenises the input text on the fly, loo ...development on HFST tools allowing for conversion between the HFST backend formats, and initial development on a tool for dumping a list of the strings recogn16 KB (2,571 words) - 12:21, 20 June 2019
- ...ormats. You will probably need to learn more about the specifics of these formats. The GitHub issue is [https://github.com/jonorthwash/ud-annotatrix/issues/ |title=apertium-apy: add i/o formats)397 KB (52,731 words) - 11:22, 10 December 2019
- == Basic understanding of the Metadix and other formats == The formats en-ca, en-es, fr-es, oc-ca, oc-es contains the metadix format files.4 KB (684 words) - 12:20, 20 March 2014
- ::Problems in incompatibility between text formats can be either taken care of in the code (e.g. add a mode to SFST to output ===Example formats===3 KB (406 words) - 14:29, 13 April 2008
- * There is an import button that allows to import large corpus in multiple formats. * Each pair of formats has a validation procedure, which determines whether the current format can4 KB (667 words) - 16:37, 1 April 2017
- === Code/Plain-text formats for Apertium data ===9 KB (1,494 words) - 00:52, 20 April 2019
- ...he lttoolbox/apertium directories, while some editors require other schema formats. The java program "trang" can convert the dix and transfer DTD's to other formats like XSD, RNC or RNG, if your favourite editor doesn't support DTD's.5 KB (783 words) - 14:25, 29 December 2020
- ==Editing Xerox formats in vim==2 KB (359 words) - 16:00, 2 January 2021
- == Formats ==13 KB (1,601 words) - 23:31, 23 July 2021
- ==Rule formats==12 KB (1,761 words) - 14:10, 19 August 2014
- If you know anything about digital film formats, you will know this is an area of many configuration options, and that, at Several formats have been used for subtitling films. However, the format you will meet ofte9 KB (1,428 words) - 18:45, 8 January 2017
- ...written in Java-Script and HTML. The interface works with three annotation formats, namely CoNLL-U, CG-3 and SD. The current system allows a user to either en ** allow to view trees in three annotation formats9 KB (1,483 words) - 22:04, 2 April 2017
- ...istiques non supportées par le format .dix . Les objectifs de ces nouveaux formats ''dix-like'' sont : Il y a actuellement un débat sur l'unification de ces formats dans un format metadix unique qui à son tour pourrait être aussi utilisé12 KB (1,883 words) - 08:42, 8 October 2014
